PULSE IQ · EARNED AUTONOMY · GROUNDED ANSWERS

Intelligence that puts its accuracy on the record.

Every prediction committed before the outcome and graded against what the floor actually did. Every answer built from that record and cited. Pulse IQ watches, earns its authority, and answers in plain language through Pulse Pilot.

PULSE IQEARNED AUTONOMY

Pulse IQ doesn't ask for trust. It shows its work.

Every other vendor asks you to believe their alerts. Pulse IQ commits every warning to a hash-chained record before the outcome exists, then grades itself against what the floor actually did: hits, misses, and the running track record, in the open. When it speaks up, you know exactly how often it has been right. And it only ever acts as far as it has earned: staged authority, expiring leases, one-tap revocation.

01

Warnings you can act on

When Pulse IQ flags a tool, a part, or a drift, it shows its track record with it. You stop guessing which alerts matter and start fixing the ones that do.

02

Earned autonomy

It watches first, proposes second, and only acts inside the envelope you gave it. Promotion is a human decision; demotion on incident is automatic; every elevation expires on its own.

03

Answers, not archaeology

Who approved what, what ran when, why it flagged. Any day replayed on demand, so the auditor's question takes minutes, not a week.

04

Savings you can reconcile

Every caught failure is priced in dollars with the math attached: what was avoided, what it cost. A number your controller can check, not marketing ROI.

Prediction receiptResolved: HIT
committed 06:14:22 · YTTL-6
claim    reject_rate 90% band [0.021, 0.047]
resolved 06:41:09 · actual 0.033 · HIT
detector lift over chance (90d): +0.31
calibration: sha256:9be4…c71a
Authority ladderLeased
OBSERVE → reads only current: all detectors
PROPOSE → human approves each maintenance proposals
BOUNDED → acts inside constraints ceremony + lease required
AUTONOMOUS → narrow envelope never reached automatically
Value ledger · avoided downtimeReceipted
intervention tool change · HM-3 · RUL proposal #118
credited    scrap avoided $1,240 · downtime avoided $640
cost       tool consumed early −$310
net        $1,570 · cost-model fp:3d90…e2
CAPABILITY × TRUST · HOW PULSE IQ COMPARES
TYPICAL FLOOR-AI VENDOR
PULSE IQ
Alert accuracy
"AI-powered." Accuracy never published.
A published hit rate you can check yourself, per detector, inside your own deployment.
Machine actions
Auto-stops and auto-work-orders with no authority model.
Earned autonomy: staged authority, TTL leases, one-tap revocation.
Audit trail
Logs you can't verify and they can't replay.
Hash-chained journal: any day replayed bit-for-bit, by you, on demand.
Value claims
Marketing ROI on a slide.
Proven-value ledger: dollars with receipts, reconciled against your costs.

Illustrative receipts shown. Your deployment grades its own; the scoreboard lives inside your walls, not in our pitch deck.

SYSTEM ARCHITECTUREWHERE PULSE IQ SITS · WHY IT CAN'T DRIFT

Grounded because of where it sits.

Pulse IQ doesn't sit beside your data; it sits inside 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. Pulse Pilot, the way you talk to it, sits at the far end and can only answer from that record. 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
PULSE PILOTHOW YOU TALK TO PULSE IQ

Ask your floor anything. Get answers it can prove.

Pulse Pilot is the conversational side of Pulse IQ. It 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.

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 →