ONE RECORD · EVERY QUESTION

Every record you keep, one question away.

Machine state, job history, program revisions, and the predictions already graded against them: one journaled record, queried in plain language on your hardware. When the record cannot back an answer, Pilot says so.

Ask about Machine state Job history Program revisions Quality trends Predictions Precedents An answer the record can't back doesn't ship
PULSE PILOTTHE GROUNDED CO-PILOT

Ask your floor anything. Get answers it can prove.

Pilot answers questions in plain language: machine state, program history, quality trends, precedents. Every answer is built from your floor's own journaled data and cites its receipts, and every citation is verified mechanically before the answer reaches a screen. An answer whose citations don't resolve doesn't ship; and LLM output can never become plant truth — the record's gate blocks it in every configuration.

P PULSE PILOT · SESSION #1042 · HASH-CHAINED TRANSCRIPT
Why did YTTL-6 stop at 14:32?
Spindle-load changepoint at 14:31:52, sustained +2.8σ vs its part-family baseline receipt:8f2c…a1, followed by alarm 2110 (spindle overload) at 14:32:04 receipt:8f2c…b7. Same signature preceded the July 14 insert failure receipt:5d01…e9.
Should we push the feed rate on that job?
REFUSED: no journaled evidence supports a feed-rate recommendation. Pilot answers from the record; it doesn't invent recipes.
01

Grounded by construction

Answers are built from journaled evidence with receipt hashes, not from the model's memory of the internet. An answer whose citations don't resolve against the record is refused before it reaches an operator.

02

Runs on your hardware

One OpenAI-compatible seam: point it at a local model on your own appliance and Pilot works fully air-gapped. No data leaves the floor. Ever.

03

Knows who's asking

Every session carries an authenticated identity with a server-derived role — never self-declared — so who asked, and who judged a finding, is part of the record. And every tool Pilot holds is read-only.

04

Every turn on the record

Transcripts are hash-chained sessions. What Pilot said, what backed it, and what it refused to say: all replayable, all auditable.

SYSTEM ARCHITECTUREWHERE PILOT SITS · WHY IT CAN'T DRIFT

Grounded because of where it sits.

Pilot doesn't sit beside your data; it sits at the far end of a governed pipeline. Telemetry is pulled from the controls, journaled on the way in, run through detectors and forecasters, graded against outcomes, and committed to a second hash-chained record. Only then can it answer a question. Twenty-eight ordered stages stand between a sensor and a sentence. Explore the deployment, or walk a single tick.

CLICK ANY NODE
CORE
Driver + kernel

The governed core. Twenty-eight ordered stages run every tick, from producer liveness through detectors, forecasts, grading, and the kernel's own four phases.

28 STAGES PER TICK · 0 OUTBOUND
TELEMETRY IN, RECEIPTS OUT · SIMULATED FLOW · ILLUSTRATIVE
Next action

See it on your parts, on the record

A demo takes an hour. Your parts, your machines, your priorities, and a straight assessment either way.

Book a demo