The common chronological construction
The Strategy asked for four things: a primitive-data register, admitted operations, relations among those operations, and a ledger of what they reconstruct. The completed presentation supplies each.
| Component | What it contains | Why it matters |
|---|---|---|
| Primitive-data register | Eight modules of labelled source rows, paths, original words, Keys, Covenant inputs, counts and finite variants | Keeps supplied information distinct from calculated summaries |
| Operation inventory | Twelve operations with domains, moving supports and retained information | States exactly what can act on each source object |
| Relation ledger | Nine modules of identities, domain conditions and additional source relations | Explains which agreements are forced and which require further input |
| Reconstruction ledger | Six complete source-to-family routes | Connects the rules to whole fields, not only striking endpoints |
The basic row change is . Ordered measurement carries the selected birth or lifespan changes into complete fields. SP capacity clipping connects birth positions to selected life reductions. Row rounding retains an exact residual record when recovery is required. Original named components determine the single-reversal paths. Anchored Keys compare declared measures. Covenant translation and count grouping use the same attention to order, source roles and retained information.
The most useful relations are concrete. Accumulated row differences equal differences of accumulated fields. Cap and nearest-five rounding commute after count conventions are resolved. Residual-aware source translations compose exactly. Uniform Keys respect addition, while selected factors respect grouping only on compatible blocks. The first Covenant clutch join is definitional, the next follows from equal lives, and the third requires a source equality.
The six reconstruction routes are ordinary genealogies, SP cap/rectangle, the Rounded Moses path, inverse/Keys, Covenant, and counts/NT. Their interfaces fall into three types: actual source data transferred between constructions, the same operation used on different inputs, or separately generated fields connected by source calibration.
The full JSON bundle retains exact source bindings and the detailed models. This overview states the explanatory result. No source age is made independent merely because it is summarized by an amplitude; no discarded residual is generated by keeping it; no repeated dependent output is counted as an additional witness.