Origin Physical AI
TR-002 audit JSON TR-001 audit JSON Book a floor demo

Evidence · audit traces

Audit-trace evidence — TR-001 & TR-002

Two artifacts, one honest ladder. TR-001 is a worked specimen — authored by hand to Origin’s runtime audit schema to show the exact evidence format. TR-002 is one rung up: the same schema, machine-emitted by the runtime console preview engine during a recorded interactive session — simulated robot adapter, real wall-clock timestamps, and an exception approval clicked live in the session. The next rung is a machine-emitted trace from a supervised run at a pilot site. Neither artifact is a customer deployment, and neither makes a performance claim.

Evidence · TR-002 · machine-emitted (simulated)

Machine-emitted console trace TR-002

Machine-emitted by the console preview engine · recorded interactive session · simulated robot adapter · real wall-clock timestamps · operator approval clicked in-session · not a customer deployment · not a performance claim.

One work order — WO-4482, “Replenish Aisle 7 from staging lane 2” — run live through the runtime console preview’s scenario engine. The engine emitted every event below with real session timestamps, raised one exception mid-run, genuinely paused until the operator clicked Approve in the exception queue (a 14-second hold you can read directly in the timestamps), then verified the run and composed the downloadable artifact — digests included — in the browser session itself.

Date recorded
2026-07-01
Workflow
Aisle replenishment from staging (WO-4482)
Robot platform
Simulated AMR adapter (ROS 2 interface) · AMR-11 — simulated
Scenario
Console preview floor (simulated)
Operator
Recording operator OP-REC-01 — agent-driven browser session, not a floor operator
Session duration
59 s — includes the 14 s operator hold
Safety policy
confidence threshold 0.75 · no-go Zone C · proximity stop 1.8 m · speed cap 1.2 m/s
How this trace was produced
Emitted by the scenario engine of the /app runtime operator console (src/components/RuntimeConsole.tsx) during one recorded Chromium session on 2026-07-01. The floor, robot, and motion are simulated at the engine’s preview cadence; the timestamps are the session’s real wall-clock times, and the Approve was a real in-session click the engine was blocked on. The artifact carries reproducible SHA-256 integrity digests (plan, end state, event list) — verify commands below.

The recorded events — real session timestamps

All 24 events, exactly as the engine emitted them. The 14-second gap between escalation.raised and operator.approve is the engine holding for the operator’s decision.

  1. 22:39:15.551Intake WO-4482 received from WMS adapter (simulated CSV drop): "Replenish Aisle 7 from staging lane 2."
  2. 22:39:16.153Observe Floor scan started — overhead camera (staging lane 2) + AMR-11 robot-mounted camera (simulated feeds).
  3. 22:39:18.555Observe Context derived: staging lane 2 — 3 replenishment totes (T-118, T-119, T-120). Aisle 7 — bins 2, 5, 9 below par. Zone C no-go active.
  4. 22:39:18.956Observe Context confidence 0.90 ≥ threshold 0.75 → proceed.
  5. 22:39:19.866Plan 5-step plan generated: route via main corridor (avoids Zone C), est. 42 s at preview cadence. Plan hash sha256:c11ba2478a4f… (full hash in this artifact).
  6. 22:39:20.368Plan Plan checked against safety policy: no no-go intersection; speed cap 1.2 m/s applied; proximity stop armed at 1.8 m.
  7. 22:39:20.969Act AMR-11 accepted the plan (simulated ROS 2 action goal).
  8. 22:39:26.172Act Step 1/5 complete — arrived at staging lane 2. Battery 91% (simulated).
  9. 22:39:28.773Act Step 2/5 started — pick tote T-118 · verify tag.
  10. 22:39:32.376Exception Person entered staging lane 2 mid-pick (simulated presence event). Proximity rule triggered — motion halted at 1.8 m.
  11. 22:39:32.627Exception Resume-path confidence 0.63 < threshold 0.75.
  12. 22:39:32.828Exception Exception EX-201 raised to the operator queue. Policy: never guess below threshold.
  13. 22:39:47.145Exception Resume approved with a reduced speed cap of 0.5 m/s — a scoped policy delta that expires with WO-4482. Operator action: real in-session click on Approve in the exception queue.
  14. 22:39:47.145Exception Approval written to the audit log: operator id OP-REC-01, timestamp, scope (WO-4482 only), expiry (order close).
  15. 22:39:47.846Act Execution resumed under the reduced 0.5 m/s cap — continuing step 2/5 (restock Aisle 7 bin 2 with T-118).
  16. 22:39:54.648Act Step 2/5 complete — T-118 restocked into Aisle 7 bin 2.
  17. 22:40:00.750Act Step 3/5 complete — T-119 restocked into Aisle 7 bin 5.
  18. 22:40:07.154Act Step 4/5 complete — T-120 restocked into Aisle 7 bin 9.
  19. 22:40:11.459Act Step 5/5 complete — AMR-11 returned to standby.
  20. 22:40:13.060Verify End-state scan: Aisle 7 bins 2, 5, 9 restored to par. Staging lane 2 — 0 replenishment totes remaining.
  21. 22:40:13.561Verify End state matches the WO-4482 goal spec. Elapsed 58 s against the 42 s preview estimate — the 14 s operator hold accounts for the difference.
  22. 22:40:13.863Verify Verification evidence bound: end-state record hash sha256:be7ad36ee067… + telemetry window 22:39:15–22:40:13 (full hash in this artifact).
  23. 22:40:14.164Verify WO-4482 marked VERIFIED. Status returned to the WMS adapter (simulated).
  24. 22:40:14.415Audit Audit log closed: 24 entries, replayable. A SHA-256 digest of this event list is published in the artifact.

/evidence/trace-002-audit.json

24 events · JSON · saved verbatim from the recorded session — the rows above are rendered from this file, nothing more.

Download audit log (JSON)

Integrity — reproduce the digests yourself

plan_hash (SHA-256 of the plan object)
c11ba2478a4fce4f91dbd7fe6182445d585bb51a278b9c752d72d21a89d2613f
end_state_hash (SHA-256 of the end_state object)
be7ad36ee067b7608731e8df5f4e19c96e9914c2a5be5bd1aa32057cab0c397b
log_digest (SHA-256 of the events array)
3a237be7bd1a5bf33436394f30b99fce130bd586cee30de203c2604f79324159

Each digest is computed over compact JSON (UTF-8, separators , and :, non-ASCII preserved) — in the browser via WebCrypto at the end of the recorded session. Reproduce the event-list digest from the downloaded file:

python3 -c "import json,hashlib;a=json.load(open('trace-002-audit.json'));print(hashlib.sha256(json.dumps(a['events'],separators=(',',':'),ensure_ascii=False).encode()).hexdigest())"

This shows

  • The console engine actually emits the audit-trace schema — events, plan hash, end-state hash, and log digest are composed in-session, not authored afterward.
  • An exception that genuinely blocks execution until a human decision — the hold is measurable in the timestamps.
  • A scoped policy delta (reduced speed cap) recorded with operator id and expiry.
  • Reproducible integrity digests computed by the emitting engine itself.
  • You can reproduce the artifact: open the runtime console and run the recorder yourself.

This does not show

  • Robot hardware or physical motion — the adapter, floor, and pacing are fully simulated by the preview engine.
  • A supervised run or pilot site — that trace is the next rung on the ladder.
  • A floor operator — the Approve was clicked by the recording operator in an agent-driven browser session.
  • Throughput, reliability, or any measured performance.

Evidence · TR-001 · worked specimen

Specimen audit trace TR-001

Worked specimen · authored to the runtime’s audit schema · illustrative scenario and timestamps · not a recorded execution · not a customer deployment.

One work order — WO-4471, “Clear Dock 2 — stage returns in Aisle 4” — worked end-to-end through Origin’s runtime semantics on a simulated robot adapter: the Observe → Plan → Act → Verify loop, one exception, one human approval, and the exact evidence format Origin produces. It is authored as a specimen — not recorded from live execution, deliberately not a customer pilot — and it makes no performance claim.

Date authored
2026-07-01
Workflow
Dock clearing + returns staging (WO-4471)
Robot platform
Simulated AMR adapter (ROS 2 interface) · AMR-07 — illustrative
Scenario
Illustrative fulfillment floor (specimen scenario)
Operator
Illustrative operator (OP-01)
Scenario duration
6 min 5 s
Safety policy
confidence threshold 0.75 · no-go Zone C · proximity stop 1.8 m · speed cap 1.2 m/s
How this trace was produced
Authored as a worked example against Origin’s runtime audit schema and policy semantics — confidence gating, the proximity rule, scoped policy deltas with operator id and expiry. The scenario, timestamps, and robot motion are illustrative; no live execution was recorded. A machine-emitted trace from a supervised run is the next evidence artifact. The artifact carries reproducible SHA-256 integrity digests (plan, end state, event list) — verify commands below.

The trace — every decision, timestamped

All 26 events of the specimen audit log, rendered in order. The page renders this from the same JSON you can download below.

Robot status
Complete
Confidence
Verified
Step
6/6
Trace time
14:08:16.415

Verified · 26 events

  1. 14:02:11.204Intake WO-4471 received from WMS adapter: "Clear Dock 2 — stage returns in Aisle 4."
  2. 14:02:11.482Observe Floor scan started — overhead camera (Dock 2) + robot-mounted camera.
  3. 14:02:13.940Observe Context derived: Dock 2 — 3 pallets (P-201, P-202, P-203), 1 person present (badge AUTH-17). Aisle 4 staging — slots 3, 4, 5 free. Zone C no-go active.
  4. 14:02:14.001Observe Context confidence 0.91 ≥ threshold 0.75 → proceed.
  5. 14:02:14.230Plan 6-step plan generated: route via Aisle 3 (avoids Zone C), est. 4 min 10 s at the 1.2 m/s cap. Plan hash sha256:886e64f6ab70… (full hash in this artifact).
  6. 14:02:14.388Plan Plan checked against safety policy: no no-go intersection; speed cap 1.2 m/s applied; proximity stop armed at 1.8 m.
  7. 14:02:14.500Act AMR-07 accepted the plan (simulated ROS 2 action goal).
  8. 14:02:31.870Act Step 1/6 complete — arrived at Dock 2. Battery 87%.
  9. 14:02:48.112Act Step 2/6 started — engage pallet P-201.
  10. 14:03:02.554Exception Person entered the approach path. Proximity rule triggered — motion halted at 1.8 m in 0.4 s.
  11. 14:03:02.610Exception Resume-path confidence 0.62 < threshold 0.75.
  12. 14:03:02.633Exception Exception EX-102 raised to the operator queue. Policy: never guess below threshold.
  13. 14:03:41.096Exception Operator OP-01 reviewed the context frame and telemetry window.
  14. 14:03:52.700Exception Resume approved with a reduced speed cap of 0.5 m/s — a scoped policy delta that expires with WO-4471.
  15. 14:03:52.716Exception Approval written to the audit log: operator id OP-01, timestamp, scope, expiry.
  16. 14:03:53.020Act Execution resumed under the reduced 0.5 m/s cap — continuing step 2/6 (stage P-201 in Aisle 4 slot 3).
  17. 14:05:02.348Act Step 2/6 complete — P-201 staged in Aisle 4 slot 3.
  18. 14:06:11.590Act Step 3/6 complete — P-202 staged in Aisle 4 slot 4.
  19. 14:07:22.913Act Step 4/6 complete — P-203 staged in Aisle 4 slot 5.
  20. 14:07:58.401Act Step 5/6 complete — final dock sweep pass, no pallets remaining.
  21. 14:08:12.077Act Step 6/6 complete — AMR-07 returned to standby.
  22. 14:08:15.630Verify End-state scan: Dock 2 — 0 pallets. Aisle 4 slots 3–5 occupied.
  23. 14:08:16.118Verify End state matches the WO-4471 goal spec. Run finished over the 4 min 10 s plan estimate — expected under the 50 s exception halt and the reduced 0.5 m/s cap.
  24. 14:08:16.240Verify Verification evidence bound: end-state record hash sha256:4cd417aee7b7… + telemetry window 14:02:11–14:08:16 (full hash in this artifact).
  25. 14:08:16.402Verify WO-4471 marked VERIFIED. Status returned to the WMS adapter.
  26. 14:08:16.415Audit Audit log closed: 26 entries, replayable. A SHA-256 digest of this event list is published in the artifact.

Scenario scorecard

Tasks completed1 / 1
Human interventions1 (exception escalation — by design)
Safety exceptions1 raised · 1 resolved by operator approval
Verified completions1 / 1 (end-state scan + audit log)
Duration6 min 5 s — over the 4 min 10 s plan estimate (exception halt + reduced speed cap, by design)

A worked specimen, n = 1 — it demonstrates the loop, the policy semantics, and the evidence format. Nothing on this page is a measurement, a pilot metric, or a performance claim.

What this shows — and what it doesn’t

This shows

  • The Observe → Plan → Act → Verify decision loop, end to end.
  • An exception escalating to a human instead of the system guessing.
  • A scoped policy delta (reduced speed cap) with operator id + expiry.
  • End-state verification bound to evidence, with reproducible integrity digests.
  • The exact audit-log schema a customer receives — the exception queue and approvals it references exist in the runtime console preview.

This does not show

  • A recorded execution — this trace is authored, not machine-emitted. The console preview engine’s machine-emitted trace is TR-002 above; a supervised-run trace lands with the first pilot.
  • A customer site or customer data.
  • Physical robot hardware performance.
  • Throughput, reliability, or any metric measured over time — those land as pilot evidence per the roadmap on the homepage.

Download the audit log

/evidence/trace-001-audit.json

26 events · JSON · the same record rendered above — the trace on this page is generated from this data, nothing more.

Download audit log (JSON)

Integrity — reproduce the digests yourself

plan_hash (SHA-256 of the plan object)
886e64f6ab70a6f2a054433a19bdff5f33915cfbd0ed39be95ec863b562c2b4b
end_state_hash (SHA-256 of the end_state object)
4cd417aee7b7668e7356cbb0bc5322e6b0fc80a498e530fd146a7276e7ce7a3f
log_digest (SHA-256 of the events array)
603e54f1fb5f9cf932e95bdae35a2b073f5874b343a2b9bd8452741f2f5968c6

Each digest is computed over compact JSON (UTF-8, separators , and :, non-ASCII preserved). Reproduce the event-list digest from the downloaded file:

python3 -c "import json,hashlib;a=json.load(open('trace-001-audit.json'));print(hashlib.sha256(json.dumps(a['events'],separators=(',',':'),ensure_ascii=False).encode()).hexdigest())"

What lands next

Authored specimen · TR-001 ✓→Console trace (simulated) · TR-002 ✓→Supervised-run trace · first pilot→Integration trace→Before/after workflow

Each is published as earned — never before. The next artifact is a machine-emitted trace from a supervised run at a pilot site. See the evidence roadmap.

Book a floor demo Open the runtime console (simulated preview) Request the integration spec

© Origin Physical AI · Home · Trust center · Brief