Add a neutral memory evidence interoperability profile - #29
Merged
Conversation
Silentpartnercoding
marked this pull request as ready for review
August 9, 2026 19:13
Silentpartnercoding
pushed a commit
that referenced
this pull request
Aug 9, 2026
…s running PR #29 shipped interop/memory-evidence-profile-v0.1/validate.py with four examples and eight adversarial rejection cases. It works. Nothing executed it -- not the test suite, not CI, not the Makefile. Eight adversarial cases that never run are eight cases that cannot fail, which is the defect this programme spends most of its time finding elsewhere. It shipped here in the same session that merged a checker for exactly this shape. Found by the test count: nine files arrived and the suite did not move. A test count that does not change when tests arrive is the signal. Three tests. One runs the validator and requires it to pass its own corpus. One requires the adversarial corpus to be non-empty, since 'all cases rejected' is trivially true of an empty list. The third is the one that matters: it calls schema_validate and validate_semantics directly and requires the validator to REJECT a malformed record, because a validator that accepted everything would satisfy a check that only asks whether the program exits cleanly, and its eight rejections would mean nothing. An earlier draft of the third test skipped when it could not find an entry point named validate or check. A skipped test is barely a test, so it now uses the real entry points.
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.
What changed
Why
Opaque memory records can otherwise turn copies into apparent witnesses, partial searches into false absence claims, or commonly controlled checks into apparent independence. This profile makes those boundaries transportable without establishing truth, identity, authority, or permission.
Impact
This is an isolated interoperability artifact. It does not change the Minority Prophet research claims, runtime, authorization model, or provider neutrality.
Validation
python3 interop/memory-evidence-profile-v0.1/validate.py— 4 valid examples and 8 adversarial cases passnpm testpasses under Node 24npm run lintpasses under Node 24git diff --checkpasses