test(runtime): characterize backend result integrity - #1150
Merged
Conversation
This was referenced Aug 14, 2026
doublewhy
force-pushed
the
158-backend-falsification-matrix
branch
from
August 18, 2026 07:30
ece01b1 to
8d8f322
Compare
Exercise RuntimeManager.apply with controlled result perturbations to record which RAE-owned portable transition invariants are enforced. Attribute the existing predecessor-snapshot rejection and keep admitted cases as assertion-only strict expected failures. Part of #158
Brad-Edwards
changed the title
Brad-Edwards
force-pushed
the
158-backend-falsification-matrix
branch
from
August 19, 2026 04:03
8d8f322 to
677857d
Compare
Collaborator
|
Updated to match the revised #158 scope: reframed the change as RuntimeManager result-integrity characterization, corrected the predecessor-snapshot case, asserted the exact transition diagnostic, limited strict expected failures to AssertionError, removed the inaccurate conformance/#663 claims and vendor attribution, and merged current dev. No runtime behavior or published contract changed. |
Align the draft requirement with ADR-004 and ADR-036. Keep RAE responsible for validating portable results admitted at the execution boundary while excluding external backend certification and infrastructure verification.
Collaborator
|
Draft ASR-532 is now aligned with the revised issue scope. It requires validation of portable results admitted at the execution boundary and excludes external backend certification, manifest truth verification, and substrate observation. |
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
2 participants
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.
Plain-language summary
raes_runtime.RuntimeManager.applyresult integrity, attribute the existing transition rejection precisely, and limit strict expected failures to assertion failures.Issue tracking
Closes #158
Verification
uv run --frozen python -m pytest tests/test_issue_158_runtime_result_integrity.py -q -rxX: 2 passed, 4 expected failuresruff checkandruff format --check: passedRAES_REQUIREMENT_UID=ADR-036 make policy: passedRAES_REQUIREMENT_UID=ASR-532 make policy: local policy checks passed; Ground Control requirement lookup returned 404 and was skipped by the checkerChecklist
Notes for review
The four expected failures record currently admitted result inconsistencies; they do not certify backend behavior or infrastructure realization. The unplanned-address case remains characterization pending a contract decision on backend-derived portable resources.