Fix criterion-bound Mission completion and durable successor planning - #149
Merged
Merged
Conversation
Owner
Author
|
Independent review and exact candidate qualification Candidate:
Candidate-only artifact digests (not published release bytes):
The reviewers did not author this implementation. This comment records their actual independent source assessments; it is not a fabricated GitHub review or product Mission assurance. Source review, candidate artifacts, protected finalization, published artifacts and installed activation remain distinct. The first failed real-provider qualification is retained; the corrected real invocation used11942input/378output within unchanged limits and produced one durable successor without a live Host call. |
This was referenced Sep 18, 2026
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
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.
Problem and behavior
A canonical COMPLETE receipt previously proved every Mission criterion, so partial Action A could close the Mission without planning B. Forge now requires exact Architecture-approved evidence predicates, collects immutable delivery-bound JSON observations, and independently evaluates every criterion. Remaining scope and observed reasons reach the ordinary durable successor planner; one genuinely complete Action can still close directly.
The change preserves original observations and historical terminal results, distinguishes current-revision assertions from historical delivery, prevents repeated/no-progress work, and resumes the evidence-to-successor boundary without duplicate logical Actions or submissions. Schema 39 provides a reader fence while preserving all nonmetadata rows. The existing updater supports only the bounded 2.7.24→2.7.25 transition.
Validation
Scope and delivery
Assignment
L1-CRITERION-PLANNING-REPAIR-20260918. Version 2.7.25 selected once under the release policy. Release workflow qualifies exact wheel bytes before publication and repeats composition qualification against registry-downloaded bytes. This PR is implementation; finalization, normal release, safe updater activation and sanitized final handoff remain in this same assignment.Repository assertions prove their approved structural properties only. Host command-control evidence is not available through current EP producer readback and remains explicitly unsupported; no EP source modification or invented host evidence. Mission 3, production reset and historical Mission reassessment remain excluded. #148 retains NIET_GEHAALD / NIET_GESTART.