ENTITY v3.4.3
Open infrastructure for sovereign digital authority, data rights, continuous provenance and interoperable economic state. v3.4.3 is a bounded remediation release; the BTDU component remains 3.4.2 unchanged.
Run it. Verify it. Break it. Implement it independently.
Choose your technical entry point
Sovereign digital authority
Persistent identity, delegated authority, scoped application access and provider-independent recovery.
Data rights & provenance
Rights-bearing data, continuous provenance, evidence, usage and bounded economic consequences.
Protocol conformance testing
Deterministic vectors, accept/reject behavior, reproducibility and qualification evidence.
Clean-room interoperability
Independent implementation from public specification and sealed material without BTG implementation code.
Verify the current release
External verification
Challenge v3.4.3 with reproducible failures, portability reports, counterexamples or independent implementation work.
Real-world repository qualification
Follow ENTITY/BTDU ingestion, provenance, rights, deduplication, recovery and provider-independence qualification on real open-source repositories.
Independent implementation
Build from public specification and sealed material without using BTG implementation code. Frozen campaign versions remain tied to their exact evidence artifacts.
Standards review
Review authority, provenance, rights and portable-state semantics against existing standards without treating participation as endorsement.
The protocol in one line
Version boundary
ENTITY v3.4.3
Current supported runtime. The release fixes the two reproduced Issue #28 defects and records 76/76 remediation PASS and 279/279 full source-suite PASS.
BTDU 3.4.2
The BTDU component is unchanged in v3.4.3. Its atom/bond topology, provenance and rights boundaries remain the inherited component scope.
Historical v3.4.2 evidence
Sealed v3.4.2 campaigns, tags, hashes, receipts and frozen audit targets remain immutable. Their version labels identify the artifact actually tested and are not current-release advertising.
Claim boundary
Protocol origin, upstream ownership, BTG fork custody, BTG metadata authorship and automatic economic entitlement are distinct. Ingestion or verification does not transfer upstream ownership.
Current release identity
| Field | Value |
|---|---|
| ENTITY release | v3.4.3 |
| Release merge commit | 528b70aabd05b1e930b77e4933f157731e47274f |
| Immutable predecessor | 6dfa3d6cc738d9369cf092d2782676bf4f2a46e4 |
| BTDU component | 3.4.2 (unchanged) |
| Canonical origin | Shawn Blackmore → Blackmore Technology Group → ENTITY |
Historical qualification scope
Issues #58–#62 were created against the frozen v3.4.2 release. They remain valid historical qualification targets unless explicitly retargeted. The active 30-day wall-clock qualification was not modified or reset by v3.4.3.