docs(adr): separate RVF target from delivery status - #32
Open
proffesor-for-testing wants to merge 1 commit into
Open
docs(adr): separate RVF target from delivery status#32proffesor-for-testing wants to merge 1 commit into
proffesor-for-testing wants to merge 1 commit into
Conversation
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
os-isolation+wasmplanned until platform evidence existsrvmVersionMinremains unpublishedFixes #28
Verification
bash -n scripts/check-adr155-status.shscripts/check-adr155-status.shjq empty docs/rvforge-compatibility-matrix.jsonAdversarial review
NO BLOCK after correction. The first edit accidentally changed the plain WASM profile instead of the similarly named hosted profile; the new executable check caught the mismatch. Rechecked all eight criteria against source and retained the target contract without claiming implementation or validation. Residual risk: the RuVector canonical matrix must be reconciled separately by its owners.