Skip to content

demo.md

Latest commit

 

History

History
156 lines (113 loc) · 4.92 KB

demo.md

File metadata and controls

156 lines (113 loc) · 4.92 KB
Raw

console demo — End-to-End Architecture Verification

console demo proves the full path from operator to execution result.

What it does

Runs six sequential steps across the full stack:

1. Preflight       repos present, config bootstrapped
2. Stack           PlatformDeployment Docker stack healthy
3. Health          SwitchBoard reachable at /health
4. Route           SwitchBoard returns a real LaneDecision
5. Planning        OperationsCenter builds TaskProposal, routes through SwitchBoard
6. Execution       OperationsCenter runs the selected backend adapter

Canonical run artifacts are written to ~/.console/operations_center/runs/<run_id>/ by the execute entrypoint's RunArtifactWriter. Use console last to inspect them.

Prerequisites

# From PlatformDeployment:
./scripts/up.sh          # start the full stack (SwitchBoard must be healthy)

OperationsCenter and SwitchBoard repos must be at:

~/Documents/GitHub/OperationsCenter/
~/Documents/GitHub/SwitchBoard/
~/Documents/GitHub/PlatformDeployment/

Run the demo

console demo

Skip the stack start (if already running):

console demo --no-start

Machine-readable output:

console demo --json

What success looks like

  console demo — end-to-end architecture validation

── 1 · Preflight ─────────────────────────────────────
  ✓ PlatformDeployment: ~/Documents/GitHub/PlatformDeployment
  ✓ SwitchBoard: ~/Documents/GitHub/SwitchBoard
  ✓ OperationsCenter: ~/Documents/GitHub/OperationsCenter
  ✓ .env present
  ✓ PlatformDeployment endpoints config present

── 2 · Stack ─────────────────────────────────────────
  ✓ PlatformDeployment stack ready

── 3 · Health ────────────────────────────────────────
  ✓ SwitchBoard health: ok

── 4 · Route Selection ───────────────────────────────
  ✓ lane=claude_cli backend=team_executor

── 5 · Planning ──────────────────────────────────────
  ✓ proposal=<id> task=console-demo-worker lane=claude_cli backend=team_executor rule=...

── 6 · Execution ─────────────────────────────────────
  · lane=claude_cli  backend=team_executor
  ✓ Backend executed successfully — status=success
  · artifacts: ~/.console/operations_center/runs/<run_id>/

── Summary ───────────────────────────────────────────
  PASS preflight
  PASS stack
  PASS health
  PASS route
  PASS planning
  PASS execution      status=success executed=True

  ✓ Full end-to-end path verified
  · artifacts: ~/.console/operations_center/runs/<run_id>/
  · run `console last` to inspect

Artifact location

Artifacts are the canonical Phase 7 run artifacts written by RunArtifactWriter:

~/.console/operations_center/runs/<run_id>/
  proposal.json
  decision.json
  execution_request.json
  result.json
  run_metadata.json

console last                              # inspect most recent run
console last --json                       # machine-readable
ls ~/.console/operations_center/runs/         # list all runs

Failure modes

Symptom Cause Fix
Step 1 fails (PlatformDeployment not found) Repo not at expected path Clone PlatformDeployment to ~/Documents/GitHub/PlatformDeployment
Step 3 fails (HTTP 0) SwitchBoard not running Run ./scripts/up.sh from PlatformDeployment
Step 5 fails (exit 1) OperationsCenter venv missing cd OperationsCenter && pip install -e .
Step 6 — backend failure Backend binary not installed Install team_executor or aider; result is still canonical
Step 6 — policy skipped Policy gate blocked the task Check SwitchBoard policy config

Step 6 returning success=False with failure_category=backend_error is expected when the backend binary is not installed on the current machine. The execution boundary is still real — the adapter ran and returned a canonical ExecutionResult.

Contract chain

The demo exercises the full contract chain:

PlanningContext
    → build_proposal()     → TaskProposal        (proposal.json)
    → SwitchBoard /route   → LaneDecision         (decision.json)
    → ExecutionRequestBuilder → ExecutionRequest  (execution_request.json)
    → backend adapter      → ExecutionResult      (result.json)

All four canonical contracts (TaskProposal, LaneDecision, ExecutionRequest, ExecutionResult) are exercised. No mocks in the live path.