ENTITY v3.4.0 — Global Passport & Continuous Provenance
ENTITY v3.4.0 — Global Passport & Continuous Provenance
Blackmore Technology Group Limited has published ENTITY v3.4.0, the current open-source protocol and reference implementation for persistent sovereign digital identity and authority, explicit rights, attributable evidence, provenance, provider-independent recovery, Global Passports, interoperability, and portable economic state.
The governing abstraction remains: ENTITY → AUTHORITY → RIGHT → EVENT → VALUE. v3.4.0 adds one composable Global Passport, signed and versioned profile stacks, continuous provenance, standards mappings, implementation packages, and deployment SDK/CLI surfaces without replacing those core primitives.
Complete public documentation
The new public documentation portal contains operator, developer, protocol, economic, security, domain, version, file, and generated API/symbol reference documentation for ENTITY v3.4.0.
Implementation package families
Healthcare — HL7 FHIR and DICOM mapping surfaces
Finance — ISO 20022, FIX and LEI mapping surfaces
Manufacturing — OPC UA and Asset Administration Shell mapping surfaces
AI — NIST AI RMF, SPDX 3 and CycloneDX mapping surfaces
Robotics — ROS 2 and Open-RMF mapping surfaces
Defence / Public-Unclassified — public data governance and originator-control patterns
Permanent claim boundaries
A valid ENTITY signature or Global Passport proves integrity and attribution within its defined protocol scope; it does not by itself prove that an external-world assertion is objectively true. Package/profile validation does not establish regulatory compliance. Provider custody does not create ENTITY authority. An asserted or indicative value is not automatically market value or accounting fair value. BTG-controlled cross-language implementations are controlled reproducibility evidence, not unrelated third-party validation.
ENTITY is developed by Blackmore Technology Group Limited and released under Apache-2.0 through the public GitHub repositories linked above.
Comments