# Open Residuals Register Corridor: Stage-Two Constitutional Continuity Embodiment First entry: MI 5.10.4.10(a) Each residual carries an independent pass-condition and does not inherit closure from any other item. --- ## R-IDENTITY-DECL-01 Classification: CLOSED / RESOLVED BY SOURCE-CUSTODY CLARIFICATION Registered: MI 5.10.4.10(a) Closed: MI 6.4.8 `source_thread_id` functions as the cross-surface canonical identity thread (catalog join key, drawer band prefix origin, field membership carry, graph derivation input) while nowhere being explicitly declared as such. An identifier governing cross-surface identity resolution without explicit declaration is the implicit-authority condition INV-3 was written to surface. Pass-condition: `source_thread_id` explicitly declared as canonical cross-surface identifier, OR adjudicated disposition that the current implicit state is acceptable and does not constitute an INV-3 violation. Notes: - Archaeological/governance question, not an implementation target. - Adjudication reserved to David. - Does not inherit closure from any PAC, feeder remediation, or dual-key work. MI 6.4.8 reduction disposition: The residual is closed without creating a new constitutional object or standing identity declaration. Deeper repository evidence establishes that the operative role of `source_thread_id` is source/share provenance continuity when an upstream shared-conversation payload exposes such an identifier. It is not the canonical corpus artifact identity, does not replace repository artifact ids such as `openai-####`, and does not itself adjudicate thread custody, publication status, field membership, drawer membership, or corpus authority. Existing machinery already expresses the needed continuity: - shared-conversation normalization emits `source_thread_id` from the upstream payload where exposed; - thread-ingest validation checks `source_thread_id` consistency between ingest records and artifacts; - semantic-region validation checks `source_thread_id` across parent artifacts, message custody, and normalization validation evidence; - public/crawler surfaces expose it as provenance metadata; and - child-project provenance machinery treats it as ordinary source/share custody rather than a new corpus artifact identity. The prior registration's formulation of `source_thread_id` as a cross-surface canonical identity thread is withdrawn as overbroad for current repository practice. The required INV-3 clarification is now satisfied by ordinary source-custody/provenance machinery and its validator-enforced continuity. No new declaration surface, lifecycle state, artifact identity class, or constitutional category is required. Projection consequence: `R-IDENTITY-DECL-01` is terminal for current Open Dependencies projection purposes. Historical provenance remains preserved in this register. --- ## R-PHASE-II-C-LEXICON-01 Classification: OPEN / LEXICON CONTINUATION / PROJECT-STANDING CUSTODY Registered: MI 6.4.4.1 final pre-Phase-A custody settlement The positive Quasantum lexicon is formulation-complete at proposed/noncanonical state, with `79` admitted lexical objects and `79` validated proposed definitions under existing Phase II-C completion accounting. No further external formulation requirement remains, no Batch 3 exists, and the `493,082`-row observation universe is not reopened by this residual. The remaining unresolved obligation is narrow: future canonicalization, final lexical disposition, and public human manifestation of the proposed/noncanonical positive lexicon require explicit later authorization. This residual preserves project-standing custody of that future obligation after the MI 6.4.4 family closes; it does not adjudicate the lexicon, select preferred labels, canonicalize definitions, design the human-facing lexicon surface, publish, deploy, or mutate corpus/database state. Provenance: - `OEW-6.4.4.1-0004` (`docs/archaeology/mi-6.4.4.1-open-ended-whatnots.md`) - `docs/archaeology/mi-6.4.4.1-phase-ii-c-final-64-object-formulation-return-import-20260904.md` - `artifacts/analysis/mi-6.4.4.1-phase-ii-c-final-64-formulation-return-import-20260904/phase-ii-c-formulation-completion-accounting.json` - `artifacts/analysis/mi-6.4.4.1-phase-ii-c-final-64-formulation-return-import-20260904/phase-ii-c-current-lexical-state-after-final-64-formulation-import.json` - `docs/archaeology/mi-6.4.4-family-coordinated-thread-closure-execution-runbook-20260905.md` Pass-condition: explicit later authorization settles the lexicon's canonicalization/final-disposition/public-manifestation posture through a governed continuation, implementation, publication, disposition, or closure process, and that process records whether any surviving residual remains. Exclusions: - No Batch 3. - No corpus-scale formulation. - No return to the `493,082`-row observation universe. - No local definition formulation. - No automatic canonicalization. - No automatic preferred-label selection. - No automatic publication. - No automatic deployment. Notes: - Active custody transferred from `OEW-6.4.4.1-0004` by explicit David authorization during the final pre-Phase-A custody settlement. - Future activation requires explicit authorization. - This entry does not block repository-settled recognition that Phase II-C external formulation is substantively complete at proposed, noncanonical state. --- ## R-DEPLOY-PATH-01 - CLOSED / STALE REGISTER ENTRY RETIRED Classification: CLOSED / STALE REGISTER ENTRY / HISTORICAL Registered: MI 5.10.4.10(a) Closed: MI 5.10.7.1 Closure record: `docs/governance/r-deploy-path-01-closure.md` Correction recorded: MI 6.3.9 public-projection freshness and deployment-authority governance reconciliation. This entry was originally registered as `OPEN / ARCHITECTURAL` for the GitHub Pages deployment topology in which canonical deployment of `quasantum.org` required a manual temp-tree publish path, the `gh-pages` package deploy could not run from a dirty pre-commit checkout, the automated `main` Deploy Pages workflow reported persistent failure, and `CNAME=quasantum.org` was being manually preserved against prior custom-domain outage risk. That registered condition is no longer active. David adjudicated `R-DEPLOY-PATH-01` CLOSED at MI 5.10.7.1. The closure record states that the GitHub Pages topology that generated the residual was eliminated by the Cloudflare Pages migration, that no surviving residual belongs to `R-DEPLOY-PATH-01`, and that adjacent questions were reassigned to other governance territory. Stale-register correction: - This register previously continued to represent `R-DEPLOY-PATH-01` as open after the MI 5.10.7.1 closure record. - The present correction retires that stale open representation. - `R-DEPLOY-PATH-01` is not reopened. - The current public-projection freshness problem is not relabeled as `R-DEPLOY-PATH-01`. - A new residual may be created only if a later bounded execution corridor establishes durable unresolved debt that cannot be closed within that corridor.