EXAMPLE / CompanyOS
Turn a request into bounded technical proof
Inspect a fixed request, a reviewed plan, and a recorded or explicitly enabled loopback proof.
Follow the pattern. Inspect its limits.
Explore the source walkthrough, its evidence and the choices you would make in your own application.
Inspect the prepared request
The source uses one allowlisted profile and a curated capability map. It shapes the request into a reviewed Outcome Pack and bounded proof plan.
An exploration of the inspected source; no example is executed here.
The situation.
A fixed enterprise request moves through Understand, Shape, Match, Bound, and Verify. The package default uses prepared analysis and a committed recording. A host can explicitly enable live analysis and a bounded loopback browser run after preflight.
What you will learn
- Separate prepared analysis, recorded evidence, and live execution.
- Bind a proof to an allowlisted profile, canonical plan, and approval.
- Read exact post-action state before treating a technical criterion as satisfied.
Follow the operation.
- 01
Inspect the prepared request
The source uses one allowlisted profile and a curated capability map. It shapes the request into a reviewed Outcome Pack and bounded proof plan.
- 02
Choose the execution mode explicitly
The package's prepared runtime exposes recorded evidence and reports live browser execution unavailable. The web host may inject its API-backed runtime with explicit enablement and browser preflight.
- 03
Check the bound proof
The proof plan permits a narrow loopback mutation and structured read-back. Approval denial and off-domain attempts are blocked; assertion failures remain visible.
- 04
Inspect recorded artifacts
The repository includes companyos-acme-proof.png and a validated-recording manifest. The recording schema binds profile, plan digest, captured run, proof, and artifact hashes. A stored recording is evidence of its captured run, not evidence of a new live run.
What the source demonstrates.
- The source differentiates prepared-profile, validated-recording, prepared-simulation, live-ai, and live-browser modes.
- A committed screenshot and recording manifest exist at the cited revision.
- The prepared runtime rejects a recording/profile mismatch and represents blocked and failed scenarios explicitly.
What it does not establish.
- A current live browser run or enabled deployment configuration.
- Customer acceptance, business impact, or broad arbitrary-request automation.
- Sending invitations or operating on external production domains.
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.
- Recording verification is distinct from live browser testing. Live testing needs the documented host flags and Chromium preflight; no live run was attempted for this catalog.
Répertoire de travail : examples/companyos-ai-solutions-engineer-poc
bun run recording:verifyThe repository verifier checks the committed recording. Use the package README for the separate browser-test and host enablement path.
Manifest structure, artifacts, and source inspected; hashes and runtime not reverified here.
Read the related guide →Make the pattern your own.
- Keep the execution mode visible beside the result.
- Define one bounded criterion and exact read-back before expanding scope.
- Carry profile, plan, approval, and artifact provenance through the receipt.
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 with host override support
- Execution in this review
- Not rerun
- Production qualification
- Experimental bounded proof
Related source artifacts.
Committed screenshot ↗
Captured source artifact; not a screenshot of this audit.
Validated recording manifest ↗
Manifest exists; not freshly reverified.