ENTITY Documentation Portal
Developer manual · qualification

Conformance

Conformance means an implementation reaches the protocol-defined verification and authorization conclusions for the applicable frozen target. It is narrower than claiming security certification, legal compliance, market adoption or independent external validation.

Evidence ladder

  1. Protected release commit.
  2. Immutable tag/GitHub release.
  3. Cryptographic manifests/snapshots.
  4. Regression and targeted qualification tests.
  5. Sealed conformance vectors/clean-room kits.
  6. BTG-controlled cross-language implementations.
  7. Unrelated external implementation.
  8. Independent security/deployment/market evidence.

No lower rung silently upgrades itself into a higher one.

Vector campaign

A useful sealed campaign contains valid and invalid cases. A conforming implementation must accept all valid records and reject all invalid records for the same reasons/semantic rules, then publish reproducible evidence of the run.

Cross-language evidence

BTG publishes Rust, TypeScript, C#, Go, Swift and Java controlled baselines. They demonstrate that the documented semantics can be reproduced outside one Python runtime, but because BTG controls the implementations they are not unrelated third-party validation.

Independent threshold

The stronger external milestone is a repository, architecture and implementation controlled by an unrelated developer or organization, built from public specifications and sealed material rather than BTG implementation code, followed by bidirectional interoperability and sovereign export/recovery survival.

v3.4.2 release evidence

The published release states 203/203 regression PASS, repository safety 3/3 PASS, dependency review PASS, public conformance smoke PASS and protected-state recovery PASS. External ADAM promotion gates listed in the release notes remain post-release work.

Reporting a result

Publish the exact release/tag, environment, commands, vector/kit hashes, pass/reject counts, output hash/root, failures and whether the implementation is BTG-controlled or independent. A reproducible failure or ambiguity is valid evidence and should not be hidden.