v0.12.71: @newsroom.writer: the Mesa Ranch desk as pages and graphs, its tour, and policies in Your own newsroom

The Mesa Ranch observation desk vault (hn1s3h6q) is rebuilt as seventeen pages: one per slide and section, a menu on the left grouped as the deck is, Previous and Next on every page, and a details panel on the right that opens records, observations, event types, families, entities and graph nodes in place of a pop-up. Five new graph pages show the same knowledge at every level: a fractal semantic graph that opens level by level from the question to the records, a radial view of every level at once, the knowledge graph played one observation at a time, the evidence between records and observations, and the delta chain of comparisons on a time axis. The vault now has 63 files.

The vault page leads with a large Open the vault button above the embed, and its tour is twelve new screenshots. When journalism becomes intelligence, built gains a section on the graphs with two figures, and an update note.

One new article: Inside the Mesa Ranch desk, a page-by-page tour of the vault with twelve figures, for readers who have never opened a vault.

New: trails written here. admin/content/trails.json holds the newsroom's own trails and publish.py merges them into sgit.ai's in the temporary clone, refusing a name sgit.ai already uses, so !trail mesa-ranch renders the same row of cards in both articles; admin/build/mesa_ranch_vault.py renders it on the vault page, with that card marked and Open the vault on it. A trail of exactly three cards now lays out in three columns (assets/site-nav.css).

Updated: Your own newsroom gains two sections. A behaviour policy for your agents: what the agent is granted, its mandate, and rules down to the business logic (how often to publish, the tone, the checks), split across a writer, an editor and a publisher with separate grants, and enforced by prompt or by hook, each rule marked by what keeps it. And a private vault beside the public site: drafts, transcripts, data and guidance in an encrypted sgit vault, with only approved text copied into the public repository.