Working demo path

Test AI agent with custody, policy, and verification.

The public demo should show how MASTER ATC works without exposing raw API endpoints or bouncing visitors into broken sign-in. This walkthrough demonstrates the control-plane logic, then links to the local audit-envelope demo when running on the owner workstation.

STEP 01

Operator assigns task

Olivia-HQ creates a Tier 2 audit export task for Codex-JWGH2.

STEP 02

Test AI agent evaluates policy

MASTER ATC checks identity, risk tier, operation, and target resources.

STEP 03

Custody envelope is written

The task records created_by, assigned_to, machine_id, policy_version, and target resources.

STEP 04

Approval gate fires when needed

Tier 4-5 actions require a named human approver before allow.

STEP 05

Audit chain verifies

Each event links previous_hash to event_hash so tampering becomes visible.

Live local demo

On the owner workstation, the audit-envelope demo is running as a UI at localhost. Its API stays behind the interface; the visitor should see the cockpit, not a JSON endpoint.

Open local audit demo See ATC flow chart

Sample custody envelope

{
  "custody_id": "CUSTODY-DEMO-AGENT-001",
  "created_by": "Olivia-HQ",
  "assigned_to": "Codex-JWGH2",
  "machine_id": "JWGH2",
  "operation": "demo.audit_export",
  "risk_tier": 2,
  "target_resources": [
    "team.chat",
    "audit-chain.jsonl",
    "FINAL_OWNER_INVESTOR_PACKAGE"
  ],
  "decision": "allow",
  "verification": "valid"
}

Why this is safer than raw endpoint links

API endpoints are still available for authenticated systems and developer review, but public product pages should lead with outcomes: agent identity, bounded authority, human approval, evidence export, and chain verification.