Specify provenance and accounting for mixed typed occurrence indexing

This commit is contained in:
2026-09-24 03:48:12 -07:00
parent 29e4f67206
commit 7cfdd13d3a
4 changed files with 276 additions and 0 deletions
+13
View File
@@ -536,3 +536,16 @@ be reserved before copying or retention. Revisit the split if actual ownership
work shows sites cannot be retained without duplicated models or repeated parsing.
Public source8, mixed editing, checked-save and root reconciliation remain later
dependencies, not capabilities delivered by this design decision.
## 2026-09-24 — preserve mixed bundle authority through index construction
Adopt the [mixed typed-index contract](analysis-mixed-index-contract-20260924.md):
consume the sealed complete-Project witness into a distinct read-only owner and
reuse private structural/token verification, with aggregate retained-ledger
accounting. A copied verifier would duplicate correction work; reparsing into
the old numeric-source Index would discard bundle/profile authority. The
[independent review](analysis-mixed-index-review-20260924.md) resolved storage
domain and completeness-proof ambiguities before adoption. This is a bounded
implementation decision, not runtime acceptance or full editing parity. Revisit
if a concrete verifier invariant prevents reuse or multiple retained owners
become necessary; no generic public indexing framework is justified now.