Systems / Operating book
Public operating book
A publish path from private runtime ledgers to a public, closed-operation record.
Problem
Autonomous systems that act in public markets or public channels create a trust problem: observers cannot distinguish competence from opacity. Full transparency of private keys and open positions is unsafe. Silence is worse.
Architecture
Internal ledgers and position stores remain private. A publish pipeline selects closed operations only, normalises them into a public book, and deploys to a static surface. Open state, keys and unfinalised work never cross the boundary.
Operating model
- Source of truth: internal journal / closed position store
- Filter: closed-only; no live inventory leakage
- Publish: deterministic export to a public site
- Cadence: operator-triggered or scheduled after close
What it produces
A stable public record of completed operations suitable for external scrutiny, track-record review and operator accountability.
Status
Lab system · Live. Pattern generalises to any domain where closed outcomes should be public while open work stays private (ops runbooks, experiment results, agent task completions).