Share resource history interpretation across working and acknowledged scans

This commit is contained in:
2026-11-10 01:50:14 +08:00
parent fb997f23a8
commit c087d32e84
4 changed files with 86 additions and 45 deletions
+10
View File
@@ -808,3 +808,13 @@ The transaction materializes an owned document once before publication; a
non-create command can materialize earlier through the normal change path.
These views are unpublished preparation, not a second document store or durable
queue. Rollback drops them without publishing history, ledger or runtime state.
Resource retention now shares one synchronous history/ledger analysis between
working and acknowledged document scans. The temporary scanner holds interpreted
transition ranges, the earliest pending sequence, the resource-field union and
schema candidates only for IDs used by historical/pending data-field changes.
Create-only histories need no per-element schema table. Both documents still
produce their own pins and completeness result; all supported transitions,
including resolved evidence, are validated. Cross-schema fallback pins and owner
order are preserved. The scanner is internal to one retention pass and is not
stored across Roots, projects or registry changes.