ENTITY Documentation Portal
Developer manual · qualification & interoperability

Conformance

Conformance means an implementation reaches the protocol-defined verification and authorization conclusions for the applicable frozen target. Runtime release qualification, Protocol 1.0 conformance, package smoke testing and unrelated external validation are different evidence classes and must remain separately labeled.

Current boundary: supported runtime = ENTITY v3.4.3; BTDU component = 3.4.2 unchanged; ENTITY Protocol 1.0 remains the frozen external conformance target. A v3.4.2 clean-room result does not become a fresh v3.4.3 execution merely because the unchanged scope is inherited.

Evidence ladder

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

No lower rung silently upgrades itself into a higher one.

Protocol 1.0 vector campaign

A useful sealed campaign contains valid and invalid cases. A conforming implementation must accept all valid records and reject all invalid records under the applicable frozen semantics, then publish reproducible evidence of the run.

Cross-language evidence

BTG-controlled Rust, TypeScript, C#, Go, Swift and Java baselines remain useful reproducibility evidence. Because BTG controls those implementations, they are not unrelated third-party validation. Their current sealed/package artifacts remain v3.4.2 evidence unless separately rebuilt and qualified for another target.

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.

Current v3.4.3 release qualification

The v3.4.3 release records 76/76 PASS for the Issue #28 remediation module and 279/279 PASS for the full repository source suite. The signed v3.4.3 tag resolves to commit 528b70aabd05b1e930b77e4933f157731e47274f.

Inherited v3.4.2 qualification

The v3.4.3 release carries forward compiled Rust clean-room/conformance qualification and real-world BTDU training qualification from v3.4.2 because those qualified components/paths were unchanged. These remain explicitly inherited unchanged-scope records, not re-executed v3.4.3 tests.

Reporting a result

Publish the exact target (runtime release, protocol version or package), 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.