THE ENGINE

An engine designed to keep up

NEPHES is a reasoning engine, in development, for signals that matter. Machines and markets speak in continuous streams of numbers — NEPHES is designed to listen, understand what's normal, notice what isn't, and say why, with the evidence attached. And because it is being built to adapt to the latest and greatest in AI infrastructure on its own, the goal is that you never have to chase it. It's the core every Deep Sky Robotics product is being built on.

HOW IT'S DESIGNED TO THINK

Observe → Reason → Judge → Explain

01 · OBSERVE

Many streams, one language

Sensor telemetry, market ticks, token flows — each source is designed to be normalized into one canonical stream the engine can reason over, in real time.

02 · REASON

A fabric of specialists

Instead of one monolithic model, NEPHES is designed to route each signal through specialized reasoning engines — limits, patterns, anomalies, cross-signal relationships — that each look for something different. In NFO these engines are built — threshold, spike and drift, ML anomaly scoring (shadow-only) and cross-tag correlation; demo on simulated data.

03 · JUDGE

Confidence before action

Every conclusion is designed to carry a calibrated confidence. Below the bar, NEPHES is meant to keep watching instead of acting — knowing when not to fire is the point.

04 · EXPLAIN

Evidence, not verdicts

Outputs are designed to arrive as findings with their reasoning trail — what was observed, what it was compared against, why it matters — and persist as an auditable history. Findings and episodes persisted locally with their evidence are built (demo on simulated data).

DESIGN PRINCIPLES

What it is designed around

A

It is designed to track stories, not alarms

A developing condition becomes one continuously updated episode — opened, tracked, and closed, with cooldown and auto-close — instead of a thousand duplicate alerts (built; demo on simulated data). The aim: humans see a narrative, not noise.

B

It is designed to ground itself in documents

Give it the paperwork — a manufacturer's datasheet, a spec, a policy — and its conclusions are designed to cite the documented limits they're judged against. Datasheet upload with limit extraction is built (demo on simulated data). No black-box verdicts, by design.

C

It is designed to run where the data lives

The design goal is an engine that deploys on-premises — a factory PC, a trading workstation — with nothing leaving the building. No cloud dependency, no data-governance objection: that is the target.

D

It is designed not to care what the signal is

The same core is meant to read vibration on a conveyor and momentum in a market. New vertical, new gateway — same engine.

IT'S BUILT TO KEEP UP SO YOU DON'T HAVE TO

AI reinvents itself every few months. NEPHES is built to keep up — so you can focus on what really matters.

New models, new runtimes, new tricks — NEPHES is being built to absorb them behind one stable interface. The engine is designed to adapt to the latest and greatest underneath while nothing you build on top has to change. The plan: adopt it once, and it stays current for you while your team stays on the plant, the portfolio, the product.

IN DEVELOPMENT

Where NEPHES is being built to run

MANUFACTURINGIN DEVELOPMENT
Factory Observer Reads Rockwell L5X ladder logic (built; tested on sample and generated programs). Live PLC telemetry connectors are built and tested on simulators only. The aim: evidence-backed maintenance calls — today a live demo on simulated data. Explore NFO →
FINTECHINTERNAL PROTOTYPE
Trading Intelligence An internal prototype that reads market streams and is designed to fire only inside calibrated confidence bands, with a shadow book alongside the live one. internal operation

Have a signal stream worth watching?

See the engine at work in the live demo on simulated data — or talk to us about your vertical.

Book a demo See it in NFO