Spine Console
A spine is a table family plus a function family plus one cockpit that governs it. Deals is the exemplar — 12 tables, 59 functions, one place it is driven from. Everything below is measured against that.
Counting…
The rule: a spine without a cockpit is governed by whoever last edited a page. A cockpit without a spine is a page pretending to be a system. Every family over ~30 pieces earns exactly one admin surface — no more, no less.
Every spine, counted live
Placements waiting on a person
On 8/22 a model read every page and filed it into a family. Those are drafts, not decisions — and a draft nobody has looked at has been sitting in production looking like one. Confirm it or move it; either answer takes it off this list for good. Worst-confidence first.
How to read this
Pieces = tables + functions, counted from the live catalogue at read time — not a stored number, so it cannot drift. Surfaces = how many nav rows point into that family. High pieces with low surfaces means ungoverned; low pieces with high surfaces means shattered. Both are failures, in opposite directions. Cockpit is the single admin surface that should govern the spine — if it reads not alive, the named cockpit is parked or missing, which is worth fixing before anything else.