Skip to content
ContractSpec
Start here

CompanyOS · Advanced · source walkthrough

Trace a signal to a reviewable outcome

Walk a support-to-product scenario through permissions, correction replay, and an evidence receipt.

@lssm-tech/example.companyos-ai-os-proofs · Replay and guardrail source inspected · evidence as of 2026-10-27

Source context

Replay and guardrail source inspected · b67c376f

Pinned source links require repository access; publication and anonymous package availability were not checked for this example.

A customer support signal reveals a product gap. The canonical fixture builds a permissioned graph, redacts data before agent access, compiles a dry-run runbook, blocks stale or conflicting paths, and keeps PM approval visible.

What you will learn

  • Connect a support signal to an explicit product workflow.
  • Inspect allowed, blocked, and approval-pending actions in the same replay.
  • Derive an evidence receipt from the events used by the viewer.

AN INTERACTIVE READING MAP

Walk through this example.

Step through the maintained source review, inspect its evidence boundaries, or assemble an adaptation packet.

SOURCE WALKTHROUGH

Read the operation in its authored order

01 / IN FOCUS

Read the messy signal

Begin with the support-to-product scenario in the workbench. Treat other scenario previews as comparison material: this is the documented canonical end-to-end path.

1 / 4

0 points in your packet

Walk through the source

  1. Read the messy signal. Begin with the support-to-product scenario in the workbench. Treat other scenario previews as comparison material: this is the documented canonical end-to-end path.
  2. Inspect the operating graph. Follow signals, actors, capabilities, policies, approvals, and evidence. The permission view makes visible what an actor can query and what is redacted.
  3. Replay blocked and corrected paths. The timeline includes policy denials, pending approval, stale/conflict checks, state differences, and a correction replay. The authorized execution lane stays dry_run.
  4. Inspect the receipt. The exported structured receipt is derived from the same deterministic replay events. Use it to inspect the demonstrated technical sequence and its remaining approval boundaries.

What this review establishes

  • The provider-free source fixture links graph, replay, and receipt data for one canonical scenario.
  • Guardrail tests assert no network, secrets, or production writes and a dry-run execution lane.
  • The receipt's evidence scope is documented explicitly.

Not established

  • A real customer outcome, external provider execution, or production integration.
  • Legal compliance certification.
  • That every comparison scenario has the same complete path.

Before adapting

  • Access to the inspected source repository and a checkout at the cited revision.
  • The repository's Bun workspace dependencies and required generated package exports. These instructions were inspected; the examples were not executed in this review.

Adapt the pattern

  • Keep the receipt derived from the events presented to the operator.
  • Show blocked and pending states alongside successful steps.
  • Introduce live ports only after deciding how their evidence and authority will be represented.
declaredStability
experimental
registry
Registered
inlinePreview
Registered
execution
Not rerun
production
Provider-free dry run