governance: define historical process disposition - #407
Merged
Conversation
…H2 H3 H4 H5 ) Accept only the exact retained Wave 5 request and snapshot as historical state, require the merged boundary and amended constitution on later delivery candidates, and reject added seal or panel artifacts. Add planted negatives and marker-free release notes so the amendment can be reviewed and landed as one coordinated change.
Validate the exact retained Wave 5 state and evidence digest before Wave 6 snapshot creation and at every exit boundary. Resolve the accepted Constitution 3.1.0 commit from fetched v3 first-parent history so copied bytes do not substitute and later amendments remain valid.
Move every program identifier, delivery state digest, and transition-specific condition out of the constitution. Keep only the durable governance rule for externally recorded historical process dispositions and prospective unanimous review.
Keep exact retained-state and transition mechanics in the feature artifacts while treating the constitution as generic governance. Retire the impossible historical recovery path, preserve the immutable records, and leave the prospective entry panel and every later delivery gate intact.
Freeze the disposed historical phase across mutating delivery commands, integrate the exact predecessor disposition into the ordinary exit gate, keep fetched-tip equality entry-only, and map retained-evidence failures to bounded process diagnostics.
Make the retained delivery and deferral records explicitly read-only, remove obsolete recovery and execution directions, and leave the prospective entry panel as the next executable boundary.
Carry the accepted predecessor disposition through later phases, bind it to the exact historical work-item projection, and recheck fetched integration freshness before the sole binding request while preserving post-merge close.
Retire every remaining historical execution instruction, classify missing host-generation and handler obligations against existing code, and assign unfinished work to prospective tasks before acceptance without reactivating the disposed phase.
… H19 ) Hash complete canonical historical manifest rows and graph nodes with exact bijection, carry the disposition through later phases, and require fetched-tip freshness before the sole binding request while keeping post-merge close valid.
Move the missing host-generation, handler-contract, and accepted-socket pidfd obligations into their governing member specs, then regenerate the authoritative work-item manifest and dependency graph with exact destinations and ordering.
Reduce prospective task rows to authoritative manifest pointers, fence every retired owner and action as read-only history, and make the complete retired-task scanner symmetric and multiline-aware.
Restore T604 as the closed feature-local composite acceptance owner, reconnect T479 and T480 to its exact evidence, and make retired-fence validation reject malformed and unbalanced markers.
Order Network broker-operation work after the accepted-socket pidfd writer, preserving the existing activation-to-transport dependency chain across shared broker wire, privilege, audit, runtime, and dispatch files.
Pin the exact T604/T479/T480 local coordination set, dependencies, evidence literals, active state, and fence exclusion, and require every historical mutation guard to precede its publication path.
Use exact work-item IDs for local coordination dependencies, serialize Makefile ownership, assign exact-candidate evidence and continuity to T479 after freeze, and make retired fences accept only whole-line approved markers.
Enforce the exact T604/T479/T480 local task set, manifest and local dependencies, Makefile ordering, fixture ownership, evidence literals, candidate execution order, and active fence state.
Promote the local coordination policy to an enforcing top-level test and pin the regenerated dependency edge count after authoritative prospective ownership and shared-writer serialization.
… H42 ) Assign the real-KVM guest acceptance case and its Makefile recipe to ADR046-ch-001, then regenerate authoritative work-item and graph artifacts so local T604 ordering references a manifest-backed first writer.
Use the exact W6 graph query without duplicate dependencies, scope generated authority to provider implementation, preserve closed local acceptance coordination, and bind the self-check fence to one exact quickstart block.
Compare the exact typed local coordination contract, resolve every manifest dependency and the 258-item W6 query against the generated graph, and reject mutations to dependencies, ownership, evidence cardinality, execution order, revalidators, and contract uniqueness.
Parse local coordination JSON with recursive duplicate-key rejection, fail on malformed claimed blocks, require one exact contract, and add duplicate-key and malformed competing-contract negatives.
Parse JSON fences structurally and reject malformed competing contracts so formatting or escaped artifact kinds cannot evade the authority census. Bind the exact acceptance resource identities and correct the active task census.
Track fence delimiter type and length so longer backtick, tilde, and unclosed JSON contracts cannot evade the feature-local authority census. Add duplicate and malformed negatives for each accepted Markdown form.
Treat the first info-string token case-insensitively as the fence language so attributed or capitalized JSON contracts cannot evade the authority census. Extend the fence-form negative matrix accordingly.
Recognize only fence delimiters with zero to three leading spaces, leaving overindented and tab-indented pseudo-closers in the JSON body. Add discriminating coverage for shorter, opposite-type, longer, and pseudo-closing delimiters.
Exercise duplicate local-task contracts at every valid zero-to-three-space CommonMark indentation boundary so valid indented JSON fences cannot silently drop out of the authority census.
Allow only ASCII spaces and tabs after a closing fence delimiter, matching CommonMark instead of Rust Unicode whitespace. Add a planted non-breaking-space pseudo-closer case using an escaped codepoint.
Use the clippy-preferred control flow, remove a no-op mutation setup, and refresh the compiler-derived API input fingerprint after the policy test changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
make test-rust-mainmake test-policymake test-changelogmake check-tier0