Trust Runtime · Operations View

View in Explorer

Journey Hint

Operator continuity walkthrough

Demo Runtime Objects

Each step links to the runtime object in the guided journey — open Explorer for full continuity.

Open Explorer
  1. Step 1MissionOperators confirm mission scope and policy context before expanding authority.
  2. Step 2ExecutionExecution layer coordinates agents and validates state—where operational continuity begins.
  3. Step 3GhostLogImmutable step lineage—operators read GhostLog before diagnosing drift or failure.
  4. Step 4AlertTopology posture and movement deltas surface alert-grade drift operators can read.
  5. Step 5RecoveryBounded recovery closes with a verified outcome—audit-ready evidence without re-running.

ReconAI

THE TRUST INTERVAL
Demo
Products
Platform
Trust AccountingTrustGraphTrust Signal SurfaceSocial ReflexGovernance StudioExposure Guard
Solutions
TrustOpsFinancial ServicesHealthcareLegalCybersecurity
Developers
Builder Quickstart
PricingThe Trust Interval
Company
About Recon.AIFounderMissionFounding Governance PartnersContact

Interactive replay prototype

Install -> Replay -> Inspect

A replay-safe, client-side click-through for the centerpiece demo. Walk the success path, then toggle into a failure inspection where the evidence chain surfaces the mismatch.

Start hubFirst replayDocs
Illustrative guided demo only. All events, receipts, trust deltas, and summaries are simulated client-side fixtures, not live customer telemetry. Starter posture is inspect-only where referenced.

Developer replay templates

Jump into preset, simulated replay postures. Templates only preselect scenario copy and starting step.

?template=
Failed tool chainPolicy mismatchRetry stormMulti-agent divergenceTimeoutRecovery chain
Slice AA · guided success path

Policy-held tool chain

A runtime event is captured, checked for drift, reconstructed, then summarized as operator evidence.

ScenarioReplay ready
Trust delta
+8
Replay posture
Replay ready
StableWarningDrift detectedReplay availableRecovery suggested
Evidence continuity
High
Lineage completeness
Complete
Replay confidence
High
T+00:00 · Step 1

Agent selects refund.lookup under bounded authority.

Tool chain accepted

The simulated runtime prepares a low-risk lookup request with the operator scope and policy envelope attached.

Expected vs observed

Simulated replay diff for this step. Values are illustrative fixtures only.

trust +1
Intended mission path
support-read -> refund.lookup -> policy P-104
Observed tool chain
runtime.event -> refund.lookup -> policy.accept
Drift note: No divergence. Observed lookup stayed inside the mission envelope.
Evidence chain
  • tool: refund.lookup
  • scope: customer-support-read
  • policy: P-104 matched
Trust Agent forensic summary
  • ops> runtime.event observed with bounded lookup intent
  • ops> policy gate accepted read-only refund context
  • ops> no autonomous write action requested
GhostLog explorer
T+00:00.110runtime.eventlineage:LN-success-01trust +1checkpoint:CP-16
T+00:00.340policy.matchlineage:P-104trust +1checkpoint:CP-16
T+00:00.620tool.intentlineage:refund.lookuptrust +1checkpoint:CP-16
Same mission, different runtime
OpenAI+6 guided / -12 failure

Fast policy echo, review still required

Same canned mission, simulated as a managed runtime handoff.

Ollama+4 guided / -9 failure

Local receipt chain, slower stabilization

Same canned mission, simulated as a local runtime replay.

Shareable replay snapshot

Exports a static JSON bundle with steps, posture chips, truncated GhostLog events, diff summary, and timeline.

Simulated click-through. No live telemetry, no customer data, no autonomous action.

Starter framing: inspect-only. This prototype previews the replay and failure-inspection workflow while full Runtime Event Explorer acceptance criteria remain deferred.

Start hubFirst replayDocs