File: File_52a Title: Inverse-Number Architecture of the Rounded Chronology Status: Final; post-final pressure tested June 26 2026; author §14 non-load-bearing Mirror-row removal integrated; marked Final June 26 2026; sampled post-equalization pressure test complete Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive. Pressure-test status: Current; sampled post-equalization pressure test complete; publication-clean verification complete; post-final pressure test of June 26 2026 retained. Register Agreement status: Checked against State_Vocabulary_Register v1.17 and active companion controls; convergence / pointer update only; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries changed. Primary domain: Rounded; Inverse; Regular; Cumulative; Mirror; Comparative; Theological Traditions: MT; LXX by dependency; BJ / Jubilees by dependency; SKL by dependency where File_52b opens the supplement Canonical source: Markdown Primary anchors: 14006 BC; 13016 BC; 12026 BC; 41006 BC; 14726 BC; 14556 BC; 14526 BC; 1406 BC; 4106 BC; 3656 BC by File_52b dependency; 2706 BC; 2496 BC; 2414 BC by File_52b dependency; 2166 BC; 2006 BC; 1876 BC; 1446 BC; 6 BC; AD 48095; AD 48995; AD 53495 Related files: File_00; File_13; File_15; File_16; File_17; File_18; File_43; File_51a; File_51b; File_51c; File_52b; File_52c; File_52d; File_52e; File_54; Restart Capsule v11.15; State Vocabulary Register v1.17; 490d Repository Style Guide v2.5; Project Procedures v3.2 Major operators: base-10 digit reversal; Rounded inverse axiom; mod-5 normalization; placeholder force; no-placeholder compression by File_52b dependency only; same-side BC span; civil cross-axis span BC + AD − 1 where opened; A-space display where explicitly opened; Key of 23 25/23; Prophetic expansion 70/69; regular trunk 2700 → 7200; cumulative trunk 12600 → 62100; cumulative / regular transfer bridge 9900; triadic anchor-field; midpoint; centroid; apparent-age +30 overlay; File_52c second-order closure by dependency Major modal states: File identity state; Rounded Scaffold dependency state; inverse-number architecture state; regular trunk inverse state; cumulative trunk inverse state; placeholder-preserving inverse state; no-placeholder technical supplement state; regular inverse begetting-chain dependency state; cumulative inverse lifespan-chain dependency state; 2nd Cainan overlay state; Mirror compatibility state; A-space / civil-span distinction state; triadic anchor-field state; Christ super-anchor state; apparent-age propagation state; File_52b technical dependency state; File_52c second-order boundary state Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State Vocabulary Register v1.17; Project Procedures v3.2; File_00 foundation / archive-routing precedent; File_51a; File_52b; File_54; prior File_52a Final and post-final pressure-tested source; author §14 non-load-bearing Mirror-row removal decision; Repository_Change_Archive (non-controlling history). Current refresh note: Public-clean trust-status equalization aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.15, State_Vocabulary_Register v1.17, and Project Procedures v3.2. Register Agreement status is recorded in the header; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive.

Rounded-coordinate clarification: Author-directed September 25 2026; signed mod-5 calculations and symmetric BC/AD display labels are distinguished from literal civil counts; amendment examples and bounded diffs verified; no new full-file pressure test or central-register update claimed. Rounded whole-span anchor clarification: Author-directed September 25 2026; 6/1406 BC for Rounded birth/event sources ending in 6 and 1/1401 BC for those ending in 1; segmented chains retain their stated rules; bounded amendment verification only, with no new full-file pressure test or central-register update claimed.

File_52a — Inverse-Number Architecture of the Rounded Chronology

Author clarification — Rounded coordinates and civil spans (20260925)

Author clarification: Dean, September 25 2026. Scope: the pure Rounded coordinate and display convention in Files 51a, 51b, 52a, and 52b. The choice to use a civil count as an input to a particular mixed inverse/expansion construction remains explicit and provisional.

The Rounded calculation takes place on signed multiples of five. Write its coordinate as $q$:

$q(B\text{ BC})=-(B-1),\qquad q(\text{AD }A)=A-1.$

Reflection sends $q$ to $-q$. Display a nonzero coordinate with the numeral $|q|+1$ and the era indicated by its sign. Thus $-1405$ displays as 1406 BC, and $+1405$ displays as AD 1406. Pure Rounded date labels end in 1 or 6 on both sides; their coordinates end in 0 or 5. Zero denotes the algebraic Mirror origin and does not introduce a civil year zero. These labels do not acquire Tishri/Nisan phases merely from their final digits.

For opposite-side displayed labels, distinguish two quantities:

$W_R=q(\text{AD }A)-q(B\text{ BC})=B+A-2,$ $C=B+A-1=W_R+1.$

$W_R$ is the Rounded coordinate width. $C$ is the ordinary civil elapsed-year count between those same printed BC/AD numerals. The label mapping is therefore a Rounded display convention, not a single ordinary astronomical-year coordinate map. Use the appropriate count explicitly; do not transfer the extra year into a coordinate calculation silently.

The last row begins at 41006 BC, not 14006 BC. Accordingly, Dean's example is:

$14010-(-41005)=55015,\qquad41006+14011-1=55016.$

The selected civil-count conversion chains are:

$10051=19\times529\xrightarrow{25/23}10925\xrightarrow{25/23}11875,$ $55016=104\times529\xrightarrow{25/23}59800\xrightarrow{25/23}65000,$ $59800=200\times299\xrightarrow{300/299}60000.$

These are exact conversions of $C$, not of the neighboring coordinate widths 10050 and 55015. Their arithmetic alone does not establish the proposed inverse system as a third geometric axis.

When a converted duration is subsequently applied on the Rounded grid, calculate with $q$ and restore the date label afterward. In Dean's separately stated launch from 14006 BC:

$-14005+59800=+45795\quad\longrightarrow\quad\boxed{\text{AD }45796}.$

Here the coordinate width is 59800; the literal civil count between the displayed labels 14006 BC and AD 45796 is 59801. The starting anchor is declared separately from the original 41006 BC → AD 14011 span that generated the converted duration.

Existing-file reading rule. Earlier Protocol 1 passages often render a positive coordinate $q$ as civil AD $q$; the symmetric Rounded display renders it AD $(q+1)$. Thus the legacy expression “1406 BC → AD 1405” and the symmetric display “1406 BC ↔ AD 1406” can refer to the same abstract coordinate pair $-1405,+1405$ under different renderings. An explicitly civil equation retains its stated civil labels and count. When redrawing a pure Rounded diagram, render its coordinates using the symmetric rule. Do not globally shift actual dates, phase-resolved dates, or no-placeholder inverse results.

This author-directed clarification controls the pure Rounded display convention in this file. Inherited references to AD (n-1) or AD (n − 1) as a strict Protocol 1 target describe the legacy astronomical/civil rendering; the symmetric Rounded display of that positive coordinate is AD n. Prior expressly civil calculations remain readable in their stated rendering. The clarification and its examples are verified separately from the earlier full-file proof status.

Author clarification — Whole-span inverse anchors (20260925)

For a whole-span inversion of an explicitly Rounded BC birth or event date, select the Nativity or Conquest anchor family required by the construction, then select its member from the source date's final digit:

Keep the source date unchanged. Subtract the selected anchor, invert that complete span while preserving its trailing-zero placeholders, and rebuild from the same anchor. Matching the final digit makes the span a multiple of ten, so this whole-span operation needs no post-inverse rounding.

The selector applies in both regular and cumulative Rounded states. It does not re-anchor individual rows of a begetting or lifespan chain: those segment-by-segment operations retain their stated anchors and mod-5 normalization rules. Explicit Exodus constructions retain 1446 BC; this clarification introduces no 1441 BC anchor. Actual and phase-resolved dates are outside this rule. The Mirror coordinate and civil-count distinction above remains unchanged.

File_52a §2.1 defines the operation; File_52b §1.1 supplies the six regular dates ending in 1 and both sets of results. This author-directed rule controls whole-span birth/event inversion; it does not settle the separate experimental inverse death-date procedure or increase the evidential status of proposed patterns.

Related Repository Files

0. File-function

File_52a states the first-order inverse-number architecture of the Rounded Chronology.

The file defines base-10 digit reversal as an inverse-number operator and applies that operator to the Rounded Scaffold under the Rounded inverse axiom. Its central structural claim is that the 9900-year span between Rounded cumulative Creation and Rounded regular Creation functions as the transfer constant joining the regular trunk 2700 and cumulative trunk 12600.

This file is architectural. It states the trunk, branch, and first-order centered logic. It does not reproduce the full technical tables. File_52b carries the dense tables and technical supplement. File_52c carries the second-order closure.

Publication-cleanup note: This public-clean source preserves the Final and post-final pressure-tested status, including the author decision that removed the non-load-bearing §14 Mirror-row use from the local argument. Detailed pass notes, arithmetic-verification ledgers, machine-diff records, finalization records, pressure-test repetition, and cross-file recommendation history are archived rather than repeated in the public body.

Argument-control rule: Arithmetic facts and explicitly stated operators carry the base layer of the argument. Structural inferences identify how repeated inverse, Rounded, Mirror-compatible, and Key-of-23 relations interlock. Theological or providential readings, where present by dependency, explain why a structure matters, but they do not replace arithmetic, modal-state, node-class, or operator control.

Modal-state rule: A shared date-label, span, operator, Mirror term, or apparent-age label does not create identity unless state, node-class, tradition, and operator agree.

0.1 Working state register

0.2 File map

0.3 Machine Guards

Machine Guard [INVERSE / MIRROR FIREWALL]: Inverse-number reversal is a base-10 transformation of a span or structured value. It is not Protocol 1 Mirror target generation, not Protocol 2 phase Mirror, and not civil cross-axis span-counting.

Machine Guard [CIVIL SPAN EXECUTION]: When an executable BC-to-AD civil span is opened, use BC + AD − 1 = total. Do not use ordinary signed subtraction across the epoch boundary unless an explicitly labeled A-space calculation is being performed.

Machine Guard [A-SPACE DISPLAY]: Pure Rounded calculations use signed mod-5 coordinate q, with symmetric display numeral |q|+1 and era from its sign. Distinguish that Rounded display from legacy astronomical/civil A-space rendering and from literal civil statements. A Rounded width between displayed BC B and AD A is B+A-2; the literal civil count between those printed numerals is B+A-1. See the September 25 2026 author clarification above.

Machine Guard [ROUNDED INVERSE AXIOM]: When a rounded span is inverted and the raw inverse falls off the mod-5 lattice, normalize to the nearest mod-5 value before reapplying the span chronologically. Whole-span birth/event inversion uses the source-ending anchor selector first; its multiples-of-ten spans remain exact and require no normalization. Do not use this axiom to bypass that selector.

Machine Guard [PLACEHOLDER FORCE]: Placeholder-preserving inversion is the primary register of File_52a. Do not strip trailing zeros unless a local section explicitly opens File_52b no-placeholder compression.

Machine Guard [NO-PLACEHOLDER COMPRESSION]: No-placeholder compression belongs to File_52b as a secondary technical confirmation. It does not replace placeholder force and does not become the default operator in File_52a.

Machine Guard [ANCHOR RULE]: Regular inverse chains are reckoned from 1406 BC, 1446 BC, or 6 BC only where the section states the active anchor. The cumulative inverse lifespan chain summary is reckoned from 1406 BC by File_52b dependency. For independent whole-span birth/event inversions, select the anchor family first and use 6/1406 BC for a Rounded source ending in 6 or 1/1401 BC for one ending in 1. This source-ending rule does not re-anchor the segmented chains; see the dated author clarification and the whole-span section.

Machine Guard [TRUNK-FIRST HIERARCHY]: The inverse architecture is trunk-first. Do not promote branch coincidences above the regular trunk 2700 → 7200, the cumulative trunk 12600 → 62100, or the 9900 transfer bridge.

Machine Guard [APPARENT-AGE PROPAGATION]: The Adamic +30 overlay is meaningful only where it rides on an already load-bearing node. Intrinsic Creation-pole use and inherited inverse-pole use must remain distinct.

Machine Guard [FILE_52B BOUNDARY]: Dense tables, constrained chains, no-placeholder readings, reverse-jubilee corroborations, SKL / Pillar interoperability, and appendices remain File_52b-controlled. File_52a states the architecture and cites File_52b rather than reproducing its full proof burden.

Machine Guard [FILE_52C BOUNDARY]: Second-order closure, inverse-of-the-inverse chains, and full square / gate-field interpretation remain File_52c-controlled unless a local section explicitly opens a bounded preview.

Machine Guard [AUDIT NOTE REQUIRED]: Do not silently correct arithmetic, Mirror arithmetic, operator mismatch, or state logic. Preserve the source statement and add an audit note where needed.

0.4 Claim-status control

Claim-status labels are used only where needed. The default classifications are:

1. Thesis and scope

This file documents a second structural layer latent within the Rounded Scaffold. The chronology is not only organized by forward spans; it is also organized by the inverse behavior of those spans under base-10 digit reversal. The central claim is that the 9900-year gap between Rounded cumulative Creation and Rounded regular Creation is an ideal transfer constant for inverse-number operations. The inverse system appears load-bearing, not ornamental. It behaves like a trunk-and-branches architecture whose deepest members are the trunk spans 2700 in the regular line and 12600 in the cumulative line, inverting to 7200 and 62100.

This file states the architecture. The full technical tables, the constrained regular inverse begetting chain, the constrained cumulative inverse lifespan chain, the 2nd Cainan overlay, no-placeholder and reverse-jubilee confirmations, and fuller Mirror corroborations are deferred to File_52b.

2. Decimal mechanism and the Rounded inverse axiom

For any base-10 integer, the difference between the number and its digit-reversal is divisible by 9. This is intrinsic to decimal notation: a number and its reversal have the same digit sum, hence are congruent mod 9. Therefore reversal differences naturally generate values such as 90, 990, 1980, 2700, and 9900.

In the Rounded system a second rule is active. Because the chronology is built from links rounded to the nearest multiple of 5, reversed spans derived from rounded spans should remain on, or be restored to, the mod-5 lattice.

Rounded inverse axiom: When a rounded span is inverted by digit reversal and the result falls off the mod-5 lattice, normalize it to the nearest mod-5 value before reapplying it chronologically.

Examples:

The raw mod-9 law remains visible even before normalization:

5540 − 4550 = 990
2640 − 4620 = −1980
5042 − 2405 = 2637 = 9×293
5201 − 1025 = 4176 = 9×464

Thus decimal reversal supplies a native mod-9 grammar; the Rounded chronology supplies a native mod-5 grammar; their interaction explains the versatility of values such as 990, 1980, and 9900 without reducing the patterns to noise.

A further operational rule applies in the regular inverse chains: placeholder force is retained. Thus 30 → 30, 60 → 60, 100 → 100, and 500 → 500. The inverse is not read merely as a stripped digit-sequence; it is read as a decimal placeholder form.

Dependency note: File_52b extends the placeholder rule to additional examples such as 130 → 310, 240 → 420, and 230 → 320, and distinguishes this primary register from no-placeholder compression.

2.1 Whole-span birth/event inversion: 6/1406 BC and 1/1401 BC

Active state: an explicitly Rounded regular or cumulative BC birth/event date. Active operation: invert the complete span to a selected Nativity or Conquest anchor, rather than invert and sum individual begetting or lifespan segments.

Choose the anchor family first. A source date ending in 6 uses 6 BC or 1406 BC; a source ending in 1 uses 1 BC or 1401 BC. Do not move the source date by five years to change its ending, and do not switch anchor families to obtain a preferred result.

For the BC-side routes used here, write the source numeral as $B$ and the selected anchor as $a$, with $B\ge a$. Define the placeholder-preserving inverse $I$ by $I(0)=0$ and, for a positive span $s=10^k m$ with all trailing zeros removed from $m$,

$I(s)=10^k\operatorname{rev}(m),\qquad F_a(B)=a+I(B-a).$

Here $\operatorname{rev}$ reverses the decimal digits of the remaining core, and $k$ is the number of trailing zeros retained in their original place-value positions. Thus $2700\rightarrow7200$, $14000\rightarrow41000$, $1050\rightarrow5010$, $660\rightarrow660$, and $2000\rightarrow2000$. The rebuilt numeral $F_a(B)$ is a BC label on this branch; a construction in another direction must state that direction separately.

Matching source and anchor endings makes $B-a$ divisible by ten. Its inverse is also divisible by ten, and the rebuilt date has the same final digit as the source. No nearest-five adjustment is needed. Because this reversal preserves the trailing-zero count, applying it twice at the same anchor returns the source exactly:

$I(I(s))=s,\qquad F_a(F_a(B))=B.$

Shelah illustrates why anchor selection precedes inversion: $2421-1=2420\rightarrow2420$ returns 2421 BC, and $2421-1401=1020\rightarrow2010$ gives 3411 BC. The alternative $2421-6=2415\rightarrow5142\rightarrow5140$ uses an unmatched anchor followed by mod-5 normalization; it is not the primary whole-span procedure defined here. File_52b §1.1 lists all six regular birth dates ending in 1.

This clarification leaves the existing 6-ending whole-span examples intact: $4106-1406=2700\rightarrow7200$ rebuilds 8606 BC; $4106-6=4100\rightarrow1400$ rebuilds 1406 BC; and $14006-6=14000\rightarrow41000$ rebuilds 41006 BC. The same source-ending selector applies to an explicitly selected Rounded cumulative date ending in 1, including the 14011 BC member where that state is active.

Scope of the earlier Rounded inverse axiom: the mod-5 normalization examples in §2 remain valid for the segment or separately declared operation being inverted. The new rule does not re-anchor each row of the regular inverse begetting chain or cumulative inverse lifespan chain. Those chains, their summed macro routes, no-placeholder supplements, and explicit 1446 BC constructions retain their stated operators and anchors. Birth/event inversions carry the present rule; the separate inverse death-date proposal is not resolved by it. Choosing 1 BC or 1401 BC as an inverse anchor also leaves the Mirror origin at $q=0$ and does not alter civil counts.

3. Why 9900 is the ideal transfer constant

The formal bridge between Rounded cumulative and Rounded regular Creation is:

14006 BC → 4106 BC = 9900

This value is especially suited to inverse arithmetic for four reasons.

First, 9900 is decimal-reversal friendly: 9900 reverses to 0099, that is, to the stable kernel 99 once leading placeholders are ignored.

Second, 9900 is the formal span joining the cumulative and regular Creation rails.

Third, 9900 lies naturally on the 360 lattice:

9900 = 27.5×360

Fourth, 9900 integrates with the trunk:

2700 + 9900 = 12600

Thus the regular trunk plus the cum/reg transfer constant equals the cumulative trunk:

The inverse system therefore does not stand beside the Rounded chronology. It is built into the same scaffold through the 9900 bridge.

4. Trunk demonstration

The deepest inverse rails are the two trunk spans.

4.1 Regular trunk

4106 BC → 1406 BC = 2700
2700 inverted = 7200 = 20×360

4.2 Cumulative trunk

14006 BC → 1406 BC = 12600
12600 inverted = 62100 = 23×2700 = 27×2300

These are the two primary inverse rails. Everything else branches from them.

5. Primary regular inverse: Creation, Flood, Conquest

Regular Rounded triad:

Forward spans:

4106 → 2456 = 1650
2456 → 1406 = 1050

Inversion:

1650 → 5610
1050 → 5010

Rebuilt from the 1406 BC anchor:

1406 + 5010 = 6416 BC
6416 + 5610 = 12026 BC

Thus the primary regular inverse line is:

12026 BC → 6416 BC → 1406 BC

5.1 Utility of 12026 BC

12026 BC is immediately productive:

So the 9900 bridge is partitioned as:

14006 → 12026 = 1980
12026 → 4106 = 7920
1980 + 7920 = 9900
7920 = 4×1980

5.2 Flood bridge and doubled 360 relation

6416 → 2456 = 3960 = 11×360
12026 → 4106 = 7920 = 22×360

Hence the Creation bridge is exactly double the Flood bridge:

3960 : 7920 = 1 : 2

5.3 Compatibility with the original line

The inverse line also forms exact structured relations with the original Rounded line:

6176 → 4106 = 2070 = 23×90
2070×70/69 = 2100
4106 → 2496 = 1610 = 23×70

Thus inverse and real are not sealed systems. They interlock.

6. Route-independence: the 1050 + 600 + 1050 backbone

The regular Rounded backbone is:

4106 BC → 3056 BC = 1050
3056 BC → 2456 BC = 600
2456 BC → 1406 BC = 1050

Inversion gives:

1050 → 5010
600 → 600
1050 → 5010

Therefore:

5010 + 600 + 5010 = 10620
1406 + 10620 = 12026 BC

So 12026 BC is reached not only by the macro outline 1650 + 1050, but also by the finer internal backbone 1050 + 600 + 1050. This route-independence is one of the strongest signs of robustness.

The same backbone is reinforced by the two framing patriarchs:

Adam 930 + Moses 120 = 1050
930 inverted = 390 = 130×3
120 inverted = 210 = 70×3
390 + 210 = 600

Thus the Adam / Moses framing pair collapse under inversion into the same central 600 that already governs Noah, Shem, and Jacob.

7. Christ anchor and the optional 2700 shift

The Christic relation is:

1406 BC → 6 BC = 1400
1400 inverted = 4100
6 BC + 4100 = 4106 BC

Thus Christ feeds directly back into regular Rounded Creation.

If one shifts the inverse line by 2700 from the 6 BC anchor rather than from 1406 BC, the following values appear:

The optional 2700 shift is therefore not arbitrary. It remains fully integrated with the 360, 430, and 23 rails.

8. Main regular branches

8.1 Jared and Abraham branch

Regular Rounded sequence:

Forward spans:

460
1190
290
760

Inversion:

460 → 640
1190 → 9110
290 → 920
760 → 670

Rebuilt from 1406 BC:

Thus:

12746 BC → 12106 BC → 2996 BC → 2076 BC → 1406 BC

Key returns:

The Jared branch is especially dense:

3646 → 6 = 3640 = 10×364
12746 → 3646 = 9100 = 25×364
12106 → 1526 = 10580 = 23×460
12106 → 4106 = 8000
12106 → 2106 = 10000

The local Flood → Abraham span is also productive:

2456 → 2166 = 290
290 inverted = 920 = 460 + 460
920×25/23 = 1000

8.2 Secondary Entry branch

If Entry into Egypt is inserted as a secondary node and Exodus rather than Conquest becomes the immediate anchor, the inverse effect remains coherent.

The alternate inverse chain becomes:

13376 BC → 12736 BC → 3626 BC → 2706 BC → 1786 BC → 1446 BC

Key returns:

2706 → 1446 = 1260
2706 → 6 = 2700
13376 → 1876 = 11500

Thus the inverse effect is not restricted to the primary trunk nodes.

9. Constrained regular inverse begetting chain

When the inverse rules are applied not merely to macro-spans but to the rounded begetting ages themselves, the resulting line remains highly structured. This is important methodologically because it shows that the inverse architecture survives tighter constraints and is not merely an artifact of selective node choice.

Dependency note: The full regular inverse begetting table is controlled by File_52b. File_52a states the key resulting nodes and selected returns only.

Key resulting nodes:

The strongest returns are these:

Thus the earlier trunk-and-branch structure is corroborated by the fine-grained genealogical chain itself. See File_52b for the full regular inverse begetting table.

10. Primary cumulative inverse: Creation, Flood, Conquest

Rounded cumulative triad:

Forward spans:

14006 → 4836 = 9170
4836 → 1406 = 3430

Inversion:

9170 → 7190
3430 → 3430

Rebuilt from 1406 BC:

1406 + 3430 = 4836 BC
4836 + 7190 = 12026 BC

Thus the cumulative line independently converges on the same inverse Creation as the regular line:

12026 BC

This double witness is one of the main reasons the inverse system cannot be reduced to random noise.

11. Secondary cumulative inverse: emergence of 13016 BC

A second cumulative inverse Creation is generated if the 12600 cumulative trunk is decomposed through either Shem or Noah while retaining the Rounded Flood and Conquest rails.

11.1 Shem-centered route

14006 → 5436 = 8570
5436 → 4836 = 600
4836 → 1406 = 3430

Inversion:

8570 → 7580
600 → 600
3430 → 3430

Rebuilt from 1406 BC:

1406 + 3430 + 600 + 7580 = 13016 BC

11.2 Noah-centered route

14006 → 6386 = 7620
6386 → 4836 = 1550
4836 → 1406 = 3430

Inversion:

7620 → 2670
1550 → 5510
3430 → 3430

Rebuilt from 1406 BC:

1406 + 3430 + 5510 + 2670 = 13016 BC

Thus different cumulative decompositions converge on the same inverse cumulative Creation:

13016 BC

11.3 Utility of 13016 BC

So the full cum/reg bridge is partitioned as:

14006 / 13016 / 12026 / 4106
990 + 990 + 7920 = 9900

This strongly suggests that the decimal family 99 / 990 / 9900 is not incidental but specially adapted to the inverse architecture.

12. Constrained cumulative inverse lifespan chain

When the same inverse rules are applied to the full rounded cumulative lifespan chain of the 26 patriarchs, the resulting chronology remains highly structured. This is the cumulative counterpart to the regular inverse begetting chain and is necessary if the inverse architecture is to be treated as systemic rather than rail-specific.

Dependency note: The full cumulative inverse lifespan table is controlled by File_52b. File_52a states the key resulting nodes and selected returns only.

Principal resulting nodes:

The strongest returns are these:

The cumulative inverse lifespans therefore do not merely mimic the regular inverse. They produce an independent and equally structured witness.

13. 2nd Cainan overlay

When 2nd Cainan is reinserted, his begetting age 130 inverts to 310 on the regular inverse line and his lifespan 460 inverts to 640 on the cumulative inverse line. Both overlays are surprisingly robust.

The most important cumulative placement is:

Shelah inverse 8396 BC
Cainan 460 → 640
therefore Cainan = 9036 BC

Then:

This is especially apt because Cainan's own structure is 130 + 330 = 460. The overlay does not disturb the inverse system; it locates Cainan naturally within its existing 23×230 / 23×330 stream.

Full regular and cumulative Cainan overlays are deferred to File_52b.

14. Mirror compatibility boundary

The inverse line is compatible with Mirror testing by dependency, but File_52a does not rely on local Mirror rows to carry its first-order inverse argument. By final author decision, the non-load-bearing source-stated Mirror rows formerly retained in this section are removed from the local File_52a argument rather than preserved as active audit rows.

This preserves the file's trunk-first hierarchy: the regular trunk, cumulative trunk, 9900 bridge, branch inversions, Cainan overlay, and triadic center-field remain the load-bearing evidence inside File_52a. Fuller Mirror examples and Mirror stress-tests remain deferred to File_52b and to the controlling Mirror files.

15. Load-bearing hierarchy: trunk and branches

The inverse chronology does not behave as a flat field of equally important dates. It behaves like a natural tree.

15.1 Trunk

2700 regular → 7200
12600 cumulative → 62100

15.2 Main branches

• Creation / Flood / Conquest
• Creation / Jared / Flood / Abraham / Conquest
• Creation / Flood / Conquest / Christ

15.3 Secondary branches

• Entry into Egypt
• Exodus
• Joshua
• Moses
• Noah
• Shem
• Cainan
• Mirror correspondences

15.4 Fine print

• regular inverse begetting chain
• cumulative inverse lifespan chain

Thus, the inverse system exhibits degrees of load-bearing importance. The trunk governs the branches. The branches retain the same numerical DNA.

16. Triadic anchor-field and Mirror productivity

The rounded poles 14006 BC, 4106 BC, and 1406 BC — and, in Mirror notation, their A-space magnitudes 14005, 4105, and 1405 — should not be treated as an arbitrary decimal arrangement. Within the Rounded Scaffold they occupy the three load-bearing positions of the inverse architecture: the cumulative trunk 12600, the cumulative / regular transfer bridge 9900, and the regular trunk 2700. Under decimal reversal these become the primary rails 62100, the stable 99 / 990 / 9900 kernel, and 7200. Thus the triad is not an added flourish at the edge of the file, but a condensed restatement of the same trunk grammar already established in §§3–4.

This productivity is not merely impressionistic. When the triad is tested across the Mirror, the same poles remain structurally fertile rather than dissolving into numerical noise. In the inner Mirror pair 4105 / 1405, 244 of 271 mirrored decadal comparisons fall into the dominant 990 classes. In the upper Mirror pair 14005 / 4105, 805 of 991 mirrored decadal comparisons are nonzero multiples of 990. Even the broader outer span 14005 / 1405 remains favorable to the same register, with 720 of 1261 positive-side decadal comparisons landing on nonzero multiples of 990, though less concentratively than the two Mirror pairings. Taken together, these results indicate that the triad occupies a distinctly favorable, though not uniquely maximal, decimal position for inverse-number behavior.

The point of these counts is methodological rather than triumphalist. They do not prove that inverse-number grammar is the only organizing principle of the Rounded chronology, nor that every node was selected solely for inverse purposes. They do show, however, that the triad lies in a region where decimal reversal, the Rounded lattice, and the Mirror interact with unusual stability. The hypothesis that inverse patterns were also in view is therefore not a speculative curiosity, but a structurally serious possibility within the broader architecture of the file.

This triadic field should accordingly be treated as a first-order disclosure of the inverse system. The trunk spans 2700 and 12600 do not merely generate isolated inverse rails; they also generate a stable anchor-set whose Mirror behavior confirms that the decimal family 99 / 990 / 9900 is adapted to the chronology at a deeper level than a local coincidence. The fuller implications of that triadic field appear in the centered disclosures treated next.

Dependency note: The decadal-count tables and technical classifications are controlled by File_52b Appendix A. File_52a preserves the architectural claim without importing the full count table.

16.1 The two first-order centers: 9056 BC and 6506 BC

The triadic anchor-field does not only yield strong terminal poles. It also yields two first-order internal centers, each produced by a different averaging operation and each structurally productive in its own right.

The first is the bipolar midpoint between the two Creation poles 14006 BC and 4106 BC. Since their distances from the common Conquest anchor 1406 BC are 12600 and 2700, their mean is:

(12600 + 2700) / 2 = 7650

Reckoned upward from 1406 BC, this gives the midpoint:

1406 + 7650 = 9056 BC

This node is exactly centered between the two Creation poles:

14006 − 9056 = 9056 − 4106 = 4950 = 99×50 = 5×990

Thus the two principal Creation rails admit a natural internal center on the 99 / 50 / 990 register.

The second is the true arithmetic centroid of the full triad 14006 / 4106 / 1406 BC. Averaging all three nodes gives:

(14006 + 4106 + 1406) / 3 = 6506 BC

Unlike 9056 BC, which averages only the two Creation poles, 6506 BC respects the entire triad, including the historical anchor at 1406 BC. Its spans are unusually productive: 6500 to 6 BC, 5100 to 1406 BC, 5060 = 11×460 to the Exodus, 2400 to 4106 BC, 7500 to 14006 BC, and 2550 = 1260 + 1290 to the midpoint center at 9056 BC. The triad therefore yields not one internal center but two complementary ones: 9056 BC as midpoint of the two Creation rails, and 6506 BC as centroid of the full three-node architecture.

The relation between these two centers is itself orderly but must be interpreted correctly:

9056 − 6506 = 2550
6506 − 1406 = 5100

This yields the clean ratio 1:2, that is, 2550 + 5100 = 7650. This proportion, however, should not be overstated. Once midpoint and centroid are defined on a fixed three-point set, such a ratio follows geometrically. What is significant here is not the bare existence of the ratio, but that the automatically generated centers land on active registers already native to the file: 99×50, 1260 + 1290, 11×460, 6500, and the two Creation-side spans 2400 and 7500 which together reproduce the formal bridge 9900 between cumulative and regular Creation.

The methodological point is therefore modest but important. The centered dates are not introduced to create pattern by free manipulation; they arise as the natural midpoint and centroid of the primary triadic poles themselves. Their significance lies not in the geometry alone, but in the fact that these unavoidable centers then re-enter the established numerical architecture of the Rounded chronology. In this way the triad discloses not only inverse rails, but an internal centered field already adapted to the same registers that govern the trunk and its branches. Cf. File_51a on the Rounded Scaffold and anchor architecture; cf. also §7 on the Christ anchor and its optional shift, where the same rail-family remains compatible with the Christward horizon.

16.2 The centroidal Exodus span: 5060 = 11×460, its Priestly expansion, and the 16000 Mirror frame

Among the spans generated by the triadic centroid 6506 BC, the most immediately consequential is its relation to the Exodus:

6506 − 1446 = 5060 = 11×460

This is not an isolated coincidence. File_51a already establishes the 460-year module as one of the governing registers of the Rounded Scaffold, structuring the line from Adam to Joseph and reappearing in major anchor-intervals to the Conquest. The centroid therefore does not reach the Exodus on an arbitrary value, but on a register already active in the underlying scaffold.

This centroidal span becomes more significant under the Priestly Key of 23:

5060 × 25/23 = 5500

Reapplied from the Exodus, this yields:

1446 BC + 5500 = 6946 BC

In A-space this is −6945, and its importance appears when it is cast against the civil mirror of the bipolar midpoint 9056 BC, namely AD 9055. The span is then:

−6945 → +9055 = 16000 = 400×40

Thus the centroidal 460 register does not terminate at the Exodus. Under Priestly expansion it opens directly into a larger Mirror frame of 16000, linking the first-order centroid 6506 BC, the Exodus anchor 1446 BC, the Priestly expansion of 5060, and the Mirror pole of 9056 BC within one continuous field.

This matters methodologically because the result is not produced by free choice of an endpoint. The date 6946 BC arises deterministically from the centroidal span to the Exodus and from the standard Priestly operator already active elsewhere in the file-system. Once that is done, the Mirror relation appears as a secondary disclosure:

6946 BC ↔ AD 9055 = 16000

In that sense the centroid functions not merely as a geometric center, but as a productive relay between the Rounded triad, the Exodus register, and the larger Mirror architecture. Cf. File_51a on the 460 module; cf. also §7, where the Christ anchor and its optional shift already show that the inverse rails remain compatible with larger Mirror and expansion frames.

The evidential force here lies in the centered date itself. The geometric ratio between midpoint and centroid is, as noted above, a formal consequence of the construction. What is not automatic is that the centroid's Exodus span should land exactly on 11×460, expand by the Priestly operator to 5500, and then reopen as 16000 = 400×40 to the civil mirror of the bipolar midpoint. The significance therefore lies not in the geometry alone, but in the fact that the generated center re-enters several pre-existing registers at once.

16.3 The free inverse rail 62100: multi-directional launch from the primary poles

Once the cumulative trunk is sanctioned as one of the two principal rails of the inverse architecture:

14006 BC → 1406 BC = 12600
12600 → 62100

its inverse 62100 need not be treated as though it were chained to the Conquest anchor alone. The trunk itself licenses 62100 as a load-bearing inverse span. Accordingly, the resulting rail may be launched from any of the primary poles generated by the same trunk, including 1406 BC, 4106 BC, and 14006 BC. This is methodologically important, because it means that the inverse span should be judged not merely by a single rebuilt date, but by the destinations it reaches when cast from the poles that originally generated it.

Read from the lower pole, the basic inverse launch is:

1406 BC + 62100 = 63506 BC

From this same rail the two standard Key-of-23 expansions yield:

62100 × 70/69 = 63000
62100 × 25/23 = 67500

and therefore the two secondary BC-side poles:

1406 BC + 63000 = 64406 BC
1406 BC + 67500 = 68906 BC

These are not needed to complete the primary inverse argument, but they are structurally relevant because they preserve the original lower rail while producing strong returns. The first yields:

64406 BC → 6 BC = 64400 = 2300×7×4

which under the Priestly key expands exactly to 70000. The second yields:

68906 BC → 4106 BC = 64800 = 180×360

thus reconnecting the expanded pole directly to Rounded regular Creation on a pure prophetic register.

Read from the upper Creation pole, the same parent rail is equally valid as a forward-time cross-axis launch:

14006 BC + 62100 = AD 48095

Under Prophetic expansion this becomes:

14006 BC + 63000 = AD 48995

which stands exactly 49000 years from 6 BC. Under Priestly expansion it becomes:

14006 BC + 67500 = AD 53495

Operator note: These AD-side labels are verified as civil forward-time launches from a BC pole:

62100 − 14006 + 1 = 48095
63000 − 14006 + 1 = 48995
67500 − 14006 + 1 = 53495

This terminal point is productive in several directions at once: it stands 60000 years from the primary centroid 6506 BC, 78000 years from the inverse centroid 24506 BC, and, significantly, exactly 62100 years from 8606 BC, the lower inverse pole generated by 2700 → 7200. In this way the expanded terminal node does not drift away from the parent architecture; it preserves the original inverse trunk rail itself across the pairing.

The consequence is that the rail 62100 should be treated as multi-directional rather than single-anchored. Launched from 1406 BC, it yields the BC-side inverse and expanded poles 63506, 64406, and 68906 BC. Launched from 14006 BC, it yields the AD-side poles AD 48095, AD 48995, and AD 53495. The significance of the rail therefore lies not in one privileged direction only, but in the fact that both directions produce coherent and numerically strong returns. The cumulative trunk does not merely invert into a static span; it opens into a field of legitimate rails whose destinations remain interoperable with the Christ anchor, the regular Creation pole, the centered nodes, and the established 230, 360, 460, and 490 registers already active elsewhere in the file-system. Cf. File_51a on the 460 module and macro-anchor structure; cf. also §7, where the Christ anchor already functions as a superordinate relay for the inverse rails.

16.4 Christ as super-anchor: the decadal triad beneath 6 BC and the emergence of 41006 BC

The decadal triad 1406 / 4106 / 14006 BC should not be read only as an internal BC-side structure. It also functions as a subordinate anchor-set beneath the Christ super-anchor at 6 BC, or, in Mirror terms, 1 BC / AD 1. Measured from 6 BC, the three poles yield the decade spans:

1406 → 6 BC = 1400
4106 → 6 BC = 4100
14006 → 6 BC = 14000

Under decimal reversal these become:

1400 → 4100
4100 → 1400
14000 → 41000

Thus, relative to the Christ super-anchor, the lower two poles simply exchange places, while the upper pole generates a secondary date:

6 BC + 41000 = 41006 BC

This is the simplest form of the Christ-super-anchor disclosure. The lower members of the decadal triad remain stable under reversal by permutation, while the upper member opens the system outward to a secondary pole. That pole is not numerically idle. It re-enters the main architecture through several returns.

First, to the Exodus anchor:

41006 BC → 1446 BC = 39560 = 23×1720

Under Priestly expansion this becomes:

39560 × 25/23 = 43000

so that:

1446 BC + 43000 = 44446 BC

This yields a Christward return:

44446 BC → 6 BC = 44440 = 1111×40

Thus the Christ-generated pole 41006 BC binds directly to the Exodus by a span that expands to 43000, re-entering the historical 430 register on a higher decimal scale.

Second, to the Conquest anchor:

41006 BC → 1406 BC = 39600

This value is doubly productive:

39600 = 110×360 = 990×40

The same span therefore reads at once on the Joshua register (110 years to the Conquest) and on the wilderness register (40 years from Exodus to Conquest), while also remaining fully compatible with the 990 family already active throughout the Mirror and triadic tests.

Third, to the principal centered dates. The Christ-generated pole stands:

41006 BC → 6506 BC = 34500

which under the Prophetic key converts exactly to:

34500 × 70/69 = 35000

It also stands:

41006 BC → 8606 BC = 32400 = 180² = 90×360

Thus the same node reconnects not only to Exodus and Conquest, but also to the primary centroid 6506 BC and to the lower inverse pole 8606 BC, and does so through square, prophetic, and expansion registers.

The methodological consequence is that 6 BC should be treated as a genuine super-anchor for the decadal triad. It is not merely one more endpoint to which spans may be measured. Under reversal it preserves the lower two decadal poles by exchange, generates the secondary pole 41006 BC, and then binds that pole back into the main architecture through the 430, 110, 40, 360, 990, and centered-date registers. In this way the Christ anchor does not sit outside the inverse system. It governs one of its most compact disclosures. Cf. §7 on the Christ anchor and optional 2700 shift; cf. also File_51a on the Exodus / Conquest anchor-complex and the 460 module.

Verification note: The normalized notation 180² is confirmed: 180² = 32400 = 90×360.

16.5 The first second-order centered field

The disclosures above already show that the triadic anchor-field is not exhausted by its primary poles. Once the Christ super-anchor at 6 BC and the first inverse rails are admitted, the architecture begins to generate a second centered field of its own. At this stage the purpose is not to catalogue every derived node, but to register that the centered logic of the first-order triad reappears at a higher level.

Relative to 6 BC, the non-inverse triad becomes:

41006 BC; 4106 BC; 1406 BC

whose two internal centers are:

(41006 + 4106) / 2 = 22556 BC
(41006 + 4106 + 1406) / 3 = 15506 BC

Likewise, the inverse-of-the-inverse triad:

53606 BC; 6806 BC; 4106 BC

yields the two centers:

(53606 + 6806) / 2 = 30206 BC
(53606 + 6806 + 4106) / 3 = 21506 BC

Thus, the first-order architecture does not terminate in one isolated midpoint and one isolated centroid. It begins to generate a 2×2 center-grid:

22556 BC; 15506 BC; 30206 BC; 21506 BC

The significance of this grid lies not in the fact that midpoints and centroids can be computed in principle, but in the fact that the resulting center-to-center spans immediately re-enter the established numerical field. Four examples are sufficient to show the point:

30206 → 15506 = 14700 = 30×490
21506 → 15506 = 6000
30206 → 22556 = 7650 = 153×50
22556 → 21506 = 1050

These are not random outputs. The first re-enters the 490 family on an enlarged scale; the second yields a clean millennial block; the third reproduces the earlier bipolar half-sum 7650 but now on the explicit jubilee register 153×50; and the fourth returns to the regular backbone value 1050. Thus the centered field is no longer confined to a single triad, but begins to generate a secondary network whose internal spans re-enter the same 490, 153, 7650, and 1050 registers already active elsewhere in the file-system.

Two further Christward relations show why this second-order field deserves at least initial notice in File_52a. The second-order centroid stands:

21506 BC → 6 BC = 21500 = 430×50

while the inverse centroid already discussed above stands:

24506 BC → 6 BC = 24500 = 490×50 = 49×500

Accordingly, the higher centered field begins to place the 430 and 490 families on the same jubilee base. This is not yet the place to unfold the entire second-order closure argument, but it is important to note that the inverse architecture, once mediated through the Christ super-anchor, starts to reproduce its own center-generating behavior at a higher level rather than dissipating into unstructured expansions.

The decadal Mirror counts and supporting classifications underlying the triadic anchor-field summarized in §16 are gathered separately in File_52b Appendix A, so that the architectural argument may remain in the present file while the denser numerical corroboration is preserved in its technical supplement.

The larger implications of this enfolding behavior — including the full inverse-of-the-inverse chains, the wider center-grid, and the more explicit closure of the trunk grammar upon itself — belong properly to File_52c. For present purposes it is enough to state the first-order result: the triadic field, once passed through Christ and the inverse rails, generates a second centered field whose principal dates and internal intervals remain compatible with the same numerical families that govern the trunk from the beginning. Cf. File_52c on second-order closure; cf. also File_52b for the denser technical tables underlying the inverse rails and their returns.

16.6 Adam's apparent-age overlay across the triadic field

A further bounded extension of the triadic field should now be stated. Adam's apparent age of 30 years is not to be propagated indiscriminately across every derived node. It is meaningful only when attached to an already load-bearing member. Accordingly, the +30 is intrinsic at the two Creation poles 4106 and 14006 BC, since these are themselves Rounded Creation states; but at 1406 BC the +30 is inherited rather than native, because 1406 BC enters the present field not as an Adamic event in its own historical right, but as the inverse-Creation pole generated from 4106 BC under the trunk grammar. The same distinction must be preserved across the Mirror: under the A-space and mod-5 conventions of File_51a, the rounded decadal pattern remains lawful, so that the AD-side companions 4135, 14035, and 1435 are to be read as the Mirror-side continuations of the same intrinsic / inherited distinction rather than as ad hoc numerical shadows.

The methodological importance of this overlay is negative as well as positive. It does not create a second architecture competing with the inverse system already established in the present file. It leaves the trunk unchanged. What it does is test whether the triadic and Mirror fields already disclosed can bear an Adamic +30 without degradation. The result is that they can. The strongest returns remain concentrated at already active registers and horizons: 360, 430, 460, 490, 1260, 1290, the Pillar field, and the SKL Flood tiers. Thus the +30 does not loosen the architecture into noise. It behaves like a lawful secondary mode superimposed upon the existing rails.

The resulting node-families are not all of equal rank. The intrinsic Creation poles remain primary. The inherited 1406/1436 pole remains secondary to them but still load-bearing within the triadic field. Beyond these stand the first-order and second-order branches disclosed through inverse and inverse-of-the-inverse propagation. The fuller technical survey of these apparent-age families, including the twelve Mirror-side anchor nodes, their major returns, their restricted ranking within the Christ / Exodus / Abraham / SKL Flood / Pillar test-field, and the distinction between first-order and second-order families, belongs properly to File_52b. Only the genuinely second-order branch effects need to be touched again in File_52c.

The fuller architectural and canonical implications of the twelve-gated square, including the side-means 6506 / 15506 / 21506 / 24506, the perimeter circuit, and the measured-city correspondences with Ezekiel 48 and Revelation 21–22, are developed in File_52c §12 and technically tabulated in File_52b Appendix B.

17. Conclusion

The 9900 gap between Rounded cumulative Creation and Rounded regular Creation remains the formal bridge of the inverse architecture. It joins the two chronological trunks, lies naturally on the decimal-reversal family 99 / 990 / 9900, and integrates with the regular trunk 2700 to produce the cumulative trunk 12600. In that sense the trunk argument stated at the beginning of this file remains unchanged: the inverse system is not ornamental, but structural.

The expanded sections above have clarified that this structure is not exhausted by a few isolated rails. The trunk spans 2700 → 7200 and 12600 → 62100 generate a triadic anchor-field, a centered internal field, and a Mirror-directed range of productive returns. The first-order disclosures are sufficient to establish the main methodological claim: the Rounded chronology is not organized only by forward spans, but also by the inverse behavior of those spans under decimal reversal. That inverse behavior remains intelligible under the Rounded lattice, the centered dates, and the Christ-super-anchor. Mirror compatibility remains active as a test-field, but the non-load-bearing §14 source-stated rows are not retained in the local argument; fuller Mirror testing remains File_52b-controlled and formally governed by the controlling Mirror files.

This does not prove that inverse-number grammar is the only organizing principle of the Rounded chronology, nor that every node was selected solely for inverse purposes. It does show that the hypothesis that inverse patterns were also in view is structurally serious and deserves to be considered alongside the forward-span architecture and the other numerical registers already active in the file-system. The evidence no longer suggests a random cloud of correspondences. It suggests a load-bearing transfer architecture governed by the trunk spans, the decimal reversal family, and a hierarchy of branches whose force can be ranked.

File_52b supplies the technical tables, full decadal counts, constrained chains, no-placeholder and reverse-jubilee corroborations, and denser technical support. File_52c carries the argument forward into the inverse of the inverse and the fuller second-order closure of the main trunk.

Revision and archive note

This public-clean Markdown source removes only archival amendment history, pass logs, pressure-test repetition, pointer-refresh records, and obsolete replacement-workflow notes.

Detailed revision history is preserved in the Repository_Change_Archive.

Final pressure-test status is preserved in the file header. Detailed pressure-test records are archived rather than repeated in the public file body.

No arithmetic, anchors, modal states, node-classes, sign conventions, operators, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed.