Vol. I · No. 05
The Editor's Desk
The pioneer's review room
Solar Voice
Governance Console · judge · run · imprimatur
Reading the proof — validation lens2 🟦 Graph · real node/edge 🟪 Hybrid · grounded + rendered 🟨 LLM · voice, no fabrication 🟩 Data · own, not inflated Fixed · static 🟥 Care · two-tier holds the Desk inherits the Bench's ink key — same house
A

The Control Space

— two levers, one judge
THE MENTAL MODEL
Govern one point in a 2-D space.
Every nominated proof occupies a (prompt-setting × corpus-stock) point. Telemetry — readership response — is the 1-D value function that judges the pair. The Desk searches this grid; the compositors set the type below it.
X · Prompt — how it reasons & speaks
The static + voice layer and the templates. Tuned at the Bench (/optimize); versioned as promptVersionId.
Y · Corpus — what it knows
The graph: content · tags · edges · embeddings · variations. Built in the pipeline; versioned as corpusVersionId.
JUDGE · Telemetry — how it performs
Activation · retention · graduation · listen-depth. Measured, never shipped. Pick on outcome first, then sim.3
Reading the live edition…
Plot all candidates →
Coupled · not orthogonal
Prompt × corpus ship as a pinned pair — the prompt's Block-3 template reads the corpus's shape. Every candidate stamps both IDs; a lock is compatibility-guarded.4
B

The Live Edition

config/live
Reading config/live…
C

At the Desk Today

— what's waiting for judgment
D

The Rooms

— judge · run · imprimatur
Marginal Apparatus · Operational Anchors
1
Imprimatur. Literally "let it be printed" — the editor-in-chief's authority to send an edition to press. Here: the pioneer's lock — a write to config/live (a runtime-config flip, app-cached, no deploy). One live pair at a time; supersede-prior; full audit trail.
2
Validation lens. Each surfaced component is coloured by what proves it true: 🟦 graph (a real node/edge), 🟪 hybrid (grounded + on-voice), 🟨 LLM (rendered language, no fabrication), 🟩 data (the user's own, never inflated), ⬜ fixed (static), 🟥 care (two-tier). The same ink key the Compositor's Bench uses.
3
Telemetry as the value function. Two signals on the same beat-event axes: mechanism-fidelity (the sim-score — the leading signal, uncalibrated until validated) vs outcome (real production / A-B telemetry, lagging). Shown side by side = the calibration loop. Pick on outcome first, then sim.
4
The coupling. Prompt × corpus are not independent — the prompt's Block-3 template formats whatever the corpus retrieval exposes. So what goes live is a pinned (prompt × corpus) pair, every iteration stamps both promptVersionId and corpusVersionId, and a lock is compatibility-guarded: lock only if the prompt's required fields ⊆ the corpus's retrievalInterface.
5
Zero-variation. The optimizer must be behaviour-identical to the shipped engine — one code path, reused, never re-implemented. Both read config/live as the locked baseline, so anything tuned on the Bench is what ships.