Artifacts

Artifact overview

Every Boardroom deliberation produces a complete set of artifacts. These are deterministic, versioned, and stored locally.

Run directory

Each deliberation creates a run directory:

.pi/ceo-agents/deliberations/{brief-id}-{session-id}/
├── conversation.jsonl    # Event transcript
├── state.json            # Persistent run state
└── board/                # Per-member final outputs
    ├── revenue.md
    ├── product-strategist.md
    ├── technical-architect.md
    ├── contrarian.md
    ├── compounder.md
    └── moonshot.md

Transcript

conversation.jsonl is an append-only event log. Each line is a JSON object recording a converse call, response, state change, or lifecycle event. This provides a complete audit trail of the deliberation.

State

state.json captures the persistent run state:

  • run_id - unique session identifier
  • brief_id - the brief being deliberated
  • status - lifecycle status (initialized, running, closing, closed, aborted, failed, superseded)
  • started_at / closed_at - ISO timestamps
  • elapsed_ms - canonical duration
  • cost_usd_micros - total cost in microUSD (1 micros = $0.000001)
  • members - per-member state (cost, status, summary, vote)
  • vote_summary - aggregate vote counts (accept, reject, defer, other)
  • paths - relative paths to all artifacts

State files use versioned schemas and are written atomically to prevent corruption.

Board outputs

Each board member produces a final output in board/{member-name}.md containing:

  • Their specialist analysis
  • Final position statement (1–2 sentences)
  • Vote (accept, reject, defer, or other)
  • Conditions or caveats

Memo

The final memo is written to:

.pi/ceo-agents/memos/{brief-id}-{session-id}/memo.md

The memo contains YAML frontmatter with run metadata and a Markdown body with the CEO’s decision, board vote table, rationale, conditions, risks, and next moves.

Path policy

All artifact paths are stored as repo-relative paths. Absolute paths are never persisted. This ensures artifacts are portable across machines and environments.

Paths are validated at load time and normalized to forward slashes.

Cost tracking

Costs are tracked in cost_usd_micros (microUSD). This provides six-decimal precision without floating-point drift.

Per-member costs are recorded in state.json. The aggregate cost appears in the memo frontmatter.

Typical deliberation cost: $0.15–$0.30 for a full board with two rounds.