Governing the Smallest Piece: A Blueprint for the Console That Plugs an Ecosystem Together

This is the confrontable blueprint of governed_core 1.0.0, the entry point of an ecosystem of eleven contracts governed by a deterministic architecture engine on a single Android device. The console is one module of roughly 700 lines: it reads the state of four governed systems from two independent sources — the Builder, which reports declared architecture, and the observer, which reports behaviour under execution — displays them on one screen, and launches fifteen destinations as separate processes. It never merges the two sources into a single number, because merging them would hide which of the two moved. Until August 2026 the console was the only piece of the ecosystem without governance: no contract, no validation, no frozen decision constants. Submitting it produced seven corrections, none of them a visible bug. Four were silent degradations that made "no data" indistinguishable from "could not read" — in an instrument used for diagnosis, the worst possible place for that defect. The document reports the exact accounting of its own governance score. For a one-module system, 0.27 of the metric is fixed, 0.49 discriminates and 0.24 is unreachable without declaring something the code does not have: architecture is 100 % of what cannot move and 0 % of what can. The resulting 76.0 is a ceiling of the metric composed with validation, not of the metric alone — which delivers 100.0 for a single false declaration — and only while the system remains one module. That defence has an exact frontier, source_root, which three of the eleven contracts do not have. Written after declaring the system, not before. Every claim in Zone 1 is verified against live code; where the document and the code disagree, the code is right.