Specify provenance and accounting for mixed typed occurrence indexing

2026-09-24 03:48:12 -07:00
parent 29e4f67206
commit 7cfdd13d3a
4 changed files with 276 additions and 0 deletions
@@ -214,6 +214,11 @@ the semantic boundary implemented by the separate private checkpoint below.
 Published private complete-Project source
 **aaec78fcc9b273d1485497126392afdd1fb2e54e** retains the original syntax, bundle,
 budgets and limits while resolving/admitting the complete ordinary/typed model.
+The next [mixed typed-index contract](analysis-mixed-index-contract-20260924.md)
+is accepted after source review and resolved accounting/completeness findings;
+it has no implementation or runtime acceptance yet. It consumes the sealed
+Project witness, reuses private index verification and keeps old updater
+authority separate. Complete mixed editing and public source8 remain required.
 Its [Windows evidence](experiments/analysis-mixed-project-20260924/README.md)
 distinguishes runtime source **71cadfa0cd0e112caa29588d2494753301f3cb6c** from
 the formatting-only aaec successor. Strict core all-target Clippy, actual listing