# Documentation Path Migration — 2026-08-23 Status: ACTIVE PATH REGISTER / CONTENT-PRESERVING / NON-RUNTIME / NO AUTHORITY EFFECT ## Purpose Record the normalization of documentation storage required by `CONTEXT_FOLDER_RULES.md`. This register changes addresses only. It does not rewrite source content, change provenance, grant authority, or promote any document. ## Mapping rules | Previous routing-layer path | Source-storage path | |---|---| | `01_CONTEXT_Development_Only/CODEX_ONLY/` | `00_Sources/01_CONTEXT_Development_Only/CODEX_DEV/` | | `01_CONTEXT_Development_Only/KABBALAH_STACK/` | `00_Sources/01_CONTEXT_Development_Only/KABBALAH_STACK/` | | `02_CONTEXT_Execution_Allowed/` | `00_Sources/02_CONTEXT_Execution_Allowed/` | `LOCAL_REFERENCE_INDEX.md` files remain in the routing layers and are not source migrations. Ignored `desktop.ini` files are synchronization metadata and are excluded. ## Preservation gates - Every tracked move must preserve the original Git blob at the destination, except a source already carrying a separately inventoried current workspace edit; for those files the pre-move current-worktree blob is authoritative for this migration. - Binary and ignored sources must preserve byte count and SHA-256. - Existing source content must not receive path corrections, formatting, encoding, line-ending normalization, or editorial changes as part of the move. - Routing metadata and downstream path references may be updated without changing the relocated source. ## Scope summary - 107 Git-visible source files follow the mapping rules. - 11 ignored literature PDFs move to `00_Sources/01_CONTEXT_Development_Only/CODEX_DEV/Literature_PDFs/`. - The PDF set contains 137,884,706 bytes; each file is verified by SHA-256 before and after relocation. - Six recent development-history records already placed in `00_Sources` remain in place and enter the scoped branch as the current workspace layer. ## Verified move result Against base commit `acace468aa75ab9c874c43264a2b24674ec54e08`: - 107 Git-visible old-to-new source mappings were resolved; - 104 destination blobs equal their source blobs at the base commit exactly; - three destinations preserve the newer current-workspace versions rather than reverting them to the base blob: - `CODEX_DEV/artebreve_PT_Comentários.md`; - `CODEX_DEV/LIBER_X_ARS_BREVIS_VERSIO_LATINA_SCHOLASTICA_COMMENTATA.md`; - `02_CONTEXT_Execution_Allowed/NEW TRANSLATIONS/PORTUGUESE/ARS_BREVIS_TRADUCAO_PORTUGUESA_COMENTADA.md`; - each of those three filtered destination blobs equals the corresponding pre-move current-workspace blob; - the separately modified `CODEX_DEV/SOURCE_INDEX.md` and six recent development-history files were copied from the current workspace and hash-verified at transfer; - all 11 ignored PDFs retained their byte count and SHA-256; exact values are recorded in `00_Sources/01_CONTEXT_Development_Only/CODEX_DEV/Literature_PDFs/LITERATURE_PDF_INVENTORY_2026-08-23.md`. ## Validation record - documentation layout validator: PASS; - Llulliana validator: PASS, with its pre-existing canon-readiness blocks still declared; - Arithmetica validator: PASS; - Stack B candidate validator: 39 PASS / 0 FAIL; - chat deployment mirror: regenerated successfully; - HTML mirror: full rebuild required and completed after the final routing metadata update; - Figurae A III vector-package validator: 2,410 PASS / 12 FAIL, exactly equal to the untouched `integration-branch` baseline. The inherited vector-package inconsistency is not repaired or widened by this documentation slice. ## Reconciliation overlay — 2026-08-29 The migration is reconciled onto the current persistent-branch tip under the low-coupling consolidation policy. Stack G is deliberately excluded from this commit so its stable-artifact mutation remains a separate rollback unit. Until that unit is applied, the prior Stack G source remains at: `01_CONTEXT_Development_Only/CODEX_ONLY/LIBER_X_ARS_BREVIS_VERSIO_LATINA_SCHOLASTICA_COMMENTATA.md` This is a bounded compatibility source, not the normalized documentation destination. Its normalized UTF-8/LF SHA-256 is `ab54083bf008b371c2de9fe690e5d3faee85667a94204bea17bb4e20a69e7494`. The layout validator admits only this exact compatibility path and hash. The separate Stack G commit must update the four G references, remove this legacy source, remove the validator exception, and record closure here. Two additional byte-controlled compatibility anchors remain in the execution routing layer because the already-numbered Stack W records their exact legacy addresses and hashes: - `02_CONTEXT_Execution_Allowed/Ars Brevis Latin.md`, normalized UTF-8/LF SHA-256 `5758658ae1412f4b012d3fb3dcff01d4ec6b63ae1d1fd5ba6c13288ed51c2291`; - `02_CONTEXT_Execution_Allowed/NEW TRANSLATIONS/PORTUGUESE/ARS_BREVIS_TRADUCAO_PORTUGUESA_COMENTADA.md`, normalized UTF-8/LF SHA-256 `6d8ba92b4750f838ea373e5b5836e5d146250c360a94006ad764a5f803180954`. These anchors do not compete with `00_Sources` as storage authority. They are read-only compatibility addresses for a stable numbered stack and may be removed only by a separately validated Stack W path-migration commit. Received and qualified W candidates remain frozen. This temporary duplication preserves the rule that integration authority follows artifact location and declared status, not the historical branch that introduced a path. ## Stack G compatibility closure — 2026-08-29 The four active Stack G artifacts now resolve the normalized source at `00_Sources/01_CONTEXT_Development_Only/CODEX_DEV/LIBER_X_ARS_BREVIS_VERSIO_LATINA_SCHOLASTICA_COMMENTATA.md`. The Stack G compatibility copy in the routing layer and its validator exception are therefore removed in the same bounded stable-artifact change. No G procedure, admissibility rule, output law, or source content is rewritten; only the source address changes. The two independently required Stack W execution witness anchors remain controlled by their exact hashes.