Protocol conformance testing
ENTITY publishes deterministic verification surfaces so an evaluator can test behavior instead of accepting architectural claims on trust.
What conformance means here
A conformance campaign asks whether an implementation produces the required accept/reject and semantic results for a frozen set of public inputs under a specified protocol/profile version. Passing a campaign is evidence for that bounded scope; it is not a blanket security, legal or real-world correctness certification.
Evaluation path
1. Verify sealed material
Confirm the exact protocol, schemas, trust material and vectors being tested.
2. Run valid vectors
Every required valid vector should be accepted with the specified deterministic semantics.
3. Run invalid vectors
Negative cases are first-class evidence: invalid authority, malformed state and prohibited transitions must fail as specified.
4. Publish reproducible evidence
Record environment, implementation version, result hashes and any divergences so unrelated reviewers can reproduce the finding.
Three ways to contribute
Current claim boundary
ENTITY v3.4.3 records 76/76 PASS for the Issue #28 remediation module and 279/279 PASS for the full repository source suite. Those results describe the published test scope; they do not establish external settlement, legal entitlement, universal security or correctness outside the tested behavior.