OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

Meetup-ready example

CompanyOS AI OS Proofs

Provider-free CompanyOS AI OS deterministic sandbox sharing one graph core and replayable evidence receipt across four scenarios.

Open sandbox Generated reference

Sandbox preview

Load the same public browser surface used for the prepared live demo.

Open preview

Reference docs

Inspect the generated contract-facing material instead of relying on marketing summaries.

Open reference

Package context

Use the agent-facing package page for fast repo orientation, then jump to the source directory.

@lssm-tech/example.companyos-ai-os-proofs

LLMS page GitHub source

Talk commands

Exact local commands for the meetup lane

Build the example package, then launch the web shell and open the prepared docs or sandbox route.

bun run --cwd packages/examples/companyos-ai-os-proofs build
bun run --cwd packages/apps/web-landing dev

# Open in the browser
# http://localhost:3000/docs/examples/companyos-ai-os-proofs
# http://localhost:3000/sandbox?template=companyos-ai-os-proofs

For the full fallback order and safe live-edit workflow, use the meetup runbook.

Live example

CompanyOS AI OS Proofs preview

This page uses the same shared preview surface as the template modal and sandbox. UI-backed examples render inline; the rest keep docs, sandbox, LLMS, and source links in one place.

CompanyOS AI OS Proofs

A deterministic sandbox for knowledge brain, operating graph, identity, permissions, realtime replay, runbook, and receipt evidence loops.

Sandbox

Support → Product

Deterministic sandbox

No provider calls

No production writes

Replayable

Evidence included

AI-native company work with permissions, redaction, replay, and evidence.

CompanyOS Operating Graph Proof

CompanyOS turns messy workflows into explicit operating graphs, lets agents act only within scoped permissions, blocks unsafe actions, replays every step, and exports evidence receipts.

Start with Support → Product: a customer support signal becomes a product gap while sensitive data is redacted, unsafe actions are blocked, PM approval is required, and the run exports a receipt.

Scenarios

Graph nodes

Replay events

Production writes

Guided 90-second executive tour

Move from story to receipt, governance, replay, architecture, and links without changing systems.

Before / after

What changes when CompanyOS becomes the operating layer.

Before CompanyOS

• Work hidden in tools

• Agents act against vague context

• Permissions unclear

• Data exposure risk

• No replay

• No proof

After CompanyOS

• Explicit operating graph

• Scoped agent capabilities

• Redaction and approval gates

• Replayable execution

• Exportable evidence receipt

Three-part proof path

The demo follows one inspectable path from graph to replay to receipt.

Graph defines constraints

Signals, actors, policies, approvals, and evidence are explicit before action.

Replay executes against constraints

Allowed, redacted, blocked, and approval-required decisions are inspectable.

Receipt proves execution

The final JSON receipt links actions, policies, redactions, approvals, and run ID.

Scenario preview

Default scenario: support-to-product

A customer support signal becomes a product gap. The agent proposes work, CompanyOS redacts sensitive data, blocks unsafe actions, requires PM approval, replays the run, and exports a receipt.

Shared graph primitives across scenarios

Every journey maps to the same reusable CompanyOS graph model.

Source records

Graph nodes

Graph edges

Permission policy

Identity review

Replay events

Evidence receipt

What this is / what this is not

This is

• Deterministic sandbox proof for CompanyOS-owned AI OS flows.

• Replayable evidence that graph, permissions, approvals, and actions align.

• A production-shaped architecture with providers intentionally disabled.

This is not

• Not a provider integration demo.

• Not a credentialed workflow.

• Not allowed to write to production systems.

Architecture diagram

Production path: replace sandbox fixtures with certified provider adapters after the same policy gates pass.

Sandbox fixtures

→

Shared graph primitives

→

Permission + identity gates

→

Replay timeline

→

Evidence receipt JSON

→

Production adapter seam

Choose a proof journey

Fixture data is labeled as deterministic sandbox data; all journeys use the same shared core.

Loading preview...

Deterministic sandbox

No provider calls

No production writes

Replayable

Evidence included

AI-native company work with permissions, redaction, replay, and evidence.

CompanyOS Operating Graph Proof

CompanyOS turns messy workflows into explicit operating graphs, lets agents act only within scoped permissions, blocks unsafe actions, replays every step, and exports evidence receipts.

Start with Support → Product: a customer support signal becomes a product gap while sensitive data is redacted, unsafe actions are blocked, PM approval is required, and the run exports a receipt.

Scenarios

Graph nodes

Replay events

Production writes

Guided 90-second executive tour

Move from story to receipt, governance, replay, architecture, and links without changing systems.

Before / after

What changes when CompanyOS becomes the operating layer.

Before CompanyOS

• Work hidden in tools

• Agents act against vague context

• Permissions unclear

• Data exposure risk

• No replay

• No proof

After CompanyOS

• Explicit operating graph

• Scoped agent capabilities

• Redaction and approval gates

• Replayable execution

• Exportable evidence receipt

Three-part proof path

The demo follows one inspectable path from graph to replay to receipt.

Graph defines constraints

Signals, actors, policies, approvals, and evidence are explicit before action.

Replay executes against constraints

Allowed, redacted, blocked, and approval-required decisions are inspectable.

Receipt proves execution

The final JSON receipt links actions, policies, redactions, approvals, and run ID.

Scenario preview

Default scenario: support-to-product

A customer support signal becomes a product gap. The agent proposes work, CompanyOS redacts sensitive data, blocks unsafe actions, requires PM approval, replays the run, and exports a receipt.

Shared graph primitives across scenarios

Every journey maps to the same reusable CompanyOS graph model.

Source records

Graph nodes

Graph edges

Permission policy

Identity review

Replay events

Evidence receipt

What this is / what this is not

This is

• Deterministic sandbox proof for CompanyOS-owned AI OS flows.

• Replayable evidence that graph, permissions, approvals, and actions align.

• A production-shaped architecture with providers intentionally disabled.

This is not

• Not a provider integration demo.

• Not a credentialed workflow.

• Not allowed to write to production systems.

Architecture diagram

Production path: replace sandbox fixtures with certified provider adapters after the same policy gates pass.

Sandbox fixtures

→

Shared graph primitives

→

Permission + identity gates

→

Replay timeline

→

Evidence receipt JSON

→

Production adapter seam

Choose a proof journey

Fixture data is labeled as deterministic sandbox data; all journeys use the same shared core.

Open system docs

CompanyOS AI OS Proofs

Sandbox preview

Reference docs

Package context

Exact local commands for the meetup lane

CompanyOS AI OS Proofs preview

CompanyOS Operating Graph Proof

Guided 90-second executive tour

Frame the proof

Open receipt JSON

Deny and redact

Shared primitives

Replay state diff

Scope boundaries

Architecture path

Before / after

Three-part proof path

Scenario preview

Shared graph primitives across scenarios

What this is / what this is not

Architecture diagram

Choose a proof journey

Support-to-product customer issue graph proof

Generic CompanyOS AI OS platform proof

EngineeringOS product/engineering drift proof

Incident Brain realtime runbook proof

CompanyOS Operating Graph Proof

Guided 90-second executive tour

Frame the proof

Open receipt JSON

Deny and redact

Shared primitives

Replay state diff

Scope boundaries

Architecture path

Before / after

Three-part proof path

Scenario preview

Shared graph primitives across scenarios

What this is / what this is not

Architecture diagram

Choose a proof journey

Support-to-product customer issue graph proof

Generic CompanyOS AI OS platform proof

EngineeringOS product/engineering drift proof

Incident Brain realtime runbook proof