35.8. What the machine can hold here
Of the 17 rubrics, 7 have no census and can have none — their population is what the document says. Of the other 10, 5 are walked today (2 by an audit that fails the build, the rest by a generated view or a pinned reading), and 5 have a population a sweep could enumerate and no sweep walking it: for those, the template is reporting exemplars, and is only as complete as the author's memory.
The framing is the model template's — a census needs a population that is a type, a decidable predicate on its members, and a way to declare the honest exceptions — but this template's profile differs in kind, for the reason the chapter opened with. Almost everything a deployment adds is unproved by construction: an image is built, a queue is chosen, an ABI floor is what it is. More of this template is therefore prose, and a document that states those facts plainly has done what can be done about them.
What is worth seeing in the table below is that the rows reading census possible are nearly all one move from being held, and it is the same move each time. The sizing records, the sweep behind each operating point, the settable knobs, the paired run behind a performance claim — every one of them is data the deployment already has and currently writes into a sentence. Declared instead of narrated, each becomes a population something can walk, which is the step M9 took for crossings in the model template and the reason that rubric gates where its neighbours only report.
| Closure | What holds the population, or what a sweep would walk |
|---|---|---|
What is deployed |
|
|
| no census | — |
| no census | — |
The contracts |
|
|
| census possible | declared payload faces with no validation ahead of the first decode |
| gated |
|
| pinned | the deployment card, generated per declared unit |
Sizing and knobs |
|
|
| census possible | sizing constants, once the measured records behind each are declared |
| census possible | reported operating points, once the sweep behind each is declared |
| census possible | settable environment knobs, once declared as data rather than listed in prose |
The platform |
|
|
| no census | — |
| pinned | the deployed version and registration payload, derived from the artifact |
| no census | — |
Acceptance |
|
|
| gated | the acceptance run itself, executed against the model document's specification |
| census possible | performance claims, once each names the paired run in the deployed executable behind it |
| no census | — |
Reproducibility and limits |
|
|
| no census | — |
| pinned | the manifest, generated from the artifacts that ran |
| no census | — |