Skip to content
ContractSpec
Start here

CompanyOS · Advanced · source walkthrough

Turn a request into bounded technical proof

Inspect a fixed request, a reviewed plan, and a recorded or explicitly enabled loopback proof.

@lssm-tech/example.companyos-ai-solutions-engineer-poc · Recording and host modes inspected · evidence as of 2026-10-27

Source context

Recording and host modes inspected · b67c376f

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

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.

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

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.

1 / 4

0 points in your packet

Walk through the source

  1. 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.
  2. 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.
  3. 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.
  4. 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 this review establishes

  • 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.

Not established

  • 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.

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.
  • 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.

Adapt the pattern

  • 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.
declaredStability
experimental
registry
Registered
inlinePreview
Registered with host override support
execution
Not rerun
production
Experimental bounded proof