Specify complete mixed Project admission and retained provenance
This commit is contained in:
@@ -515,3 +515,24 @@ Missing global and scoped parameter IDs remain explicit stabilization metadata,
|
||||
not new random identities assigned on each parse. Public source8 integration must
|
||||
thread the same accounting through the outer project and included files; this
|
||||
private checkpoint does not itself admit a complete version8 source bundle.
|
||||
|
||||
## Complete mixed Project before typed editing index — 2026-09-23
|
||||
|
||||
Choose the [private Project-first contract](analysis-mixed-project-contract-20260923.md)
|
||||
as the next semantic dependency, conditional on acceptance of its frozen syntax
|
||||
prerequisite. Reuse ordinary construction and typed lowering once, then check the
|
||||
complete Project and retain original syntax, the global lowering-site arena and
|
||||
its file ownership for later indexing. Including the typed index now would also
|
||||
change source-view/updater compatibility and several simultaneous allocation
|
||||
phases, while still leaving ordinary occurrence editing incomplete. This split
|
||||
preserves a concrete no-rescan/no-relower continuation and isolates model
|
||||
correctness from later edit authority; it does not narrow the required parity goal.
|
||||
|
||||
The [independent critique](reviews/mixed-project-contract-20260923.md) requires a
|
||||
full hand-authored retained-site oracle and a single admission result preserving
|
||||
static usage and every warning. Existing raw architectural diagnostic production
|
||||
is explicitly outside preallocation accounting; new mapped/retained storage must
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user