EXAMPLE / CompanyOS
Trace a signal to a reviewable outcome
Walk a support-to-product scenario through permissions, correction replay, and an evidence receipt.
Follow the pattern. Inspect its limits.
Explore the source walkthrough, its evidence and the choices you would make in your own application.
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.
An exploration of the inspected source; no example is executed here.
The situation.
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.
Follow the operation.
- 01
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.
- 02
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.
- 03
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.
- 04
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 the source demonstrates.
- 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.
What it does not establish.
- A real customer outcome, external provider execution, or production integration.
- Legal compliance certification.
- That every comparison scenario has the same complete path.
Bring it into your environment.
Use the exact source context and prerequisites below. A source walkthrough is not a verified public-package installation recipe.
- 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.
Working directory: examples/companyos-ai-os-proofs
bun test src/provider-free-guardrails.test.ts src/example.smoke.test.tsThe source guardrails inspect deterministic local dependencies and dry-run proof boundaries.
Source and tests inspected; not executed here.
Read the related guide →Make the pattern your own.
- 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.
Inspect the evidence.
Reviewed 2026-10-27 · b67c376f
Pinned source links require repository access; publication and anonymous package availability were not checked for this example.
- Declared maturity
- experimental
- Catalogue registration
- Registered
- Inline preview
- Registered
- Execution in this review
- Not rerun
- Production qualification
- Provider-free dry run