ENTITY v3.4.3 - Issue #28 Remediation Release

ENTITY v3.4.3

ENTITY v3.4.3 is a bounded remediation release based on immutable v3.4.2 commit
6dfa3d6cc738d9369cf092d2782676bf4f2a46e4.

Scope

This release addresses the two reproduced findings tracked in GitHub issue #28:

1. Derivative-revenue evidence substitution could create a second economic event and obligation for the same occurrence.
2. A zero-edge causal graph could return a positive self-trace for missing or empty endpoints and label an empty path evidence-bound.

Remediation

Derivative revenue now distinguishes authoritative occurrence identity from evidence identity. Exact replay is rejected. New evidence for the same occurrence is recorded as additional provenance without creating another obligation. Distinct authoritative occurrence_ref values can represent distinct revenue occurrences.

Causal tracing now validates both endpoints before traversal. Missing or empty endpoints fail closed. Existing-node self reachability may remain topologically connected, but an empty path is not treated as evidence-bound causation.

Qualification

• Issue #28 final remediation module: 76/76 PASS
• Full repository source suite: 279/279 PASS
• Full source-suite exit code: 0

Version boundary

• ENTITY release: 3.4.3
• BTDU component: 3.4.2 (unchanged)
• v3.4.2 remains immutable historical evidence.
• Production state and the active 30-day wall-clock qualification were not modified.

Claim boundary

This release is limited to the two reproduced Issue #28 defects. It does not establish external settlement, payment, legal-entitlement, fair-value, or broader economic-causality claims beyond the qualified behavior above.

Inherited unchanged-scope qualification

The following previously closed v3.4.2 qualification evidence is carried forward because v3.4.3 does not modify the qualified components or paths:

• Compiled Rust clean-room/conformance qualification: PASS (inherited unchanged scope)
  • Evidence SHA-256: 96a7b5175dc11e1d881a9a1aa53c3496dac93d182d7072e71ad4982921571754
• Real-world BTDU training qualification: PASS (inherited unchanged scope)
  • Evidence SHA-256: 4d31bc1a3ae8c8ff6dcf096b304914808e27cc60595510cc7088b5af021931ff

These are inherited qualification records, not re-executed v3.4.3 test runs.

ENTITY v3.4.2 — SUPERSEDED — Canonical BTDU Release

SUPERSEDED / UNSUPPORTED FOR CURRENT DEPLOYMENT

ENTITY v3.4.2 is retained as immutable historical provenance. The current supported canonical release is v3.4.3.

ENTITY v3.4.2 is the sole current supported canonical ENTITY release. This release introduces the Blackmore Technology Data Universe (BTDU) while preserving ENTITY authority, rights, provenance and economic semantics; ADAM deterministic state; NIKI bounded reasoning; BSIE world-state boundaries; BECP governance boundaries; and the Genesis primitives ENTITY -> AUTHORITY -> RIGHT -> EVENT -> VALUE. Qualification: 203/203 regression PASS; repository safety 3/3 PASS; GitHub dependency review PASS; public conformance smoke PASS; protected-state recovery PASS; exact restore true; restored sovereign signing true; v3.4.1 origin continuity true. Protected release commit: 6dfa3d6 Release tree: f90bf74e29899f82d0a4ee321604346241bba4de Release-origin attestation SHA-256: 0ba4b0cc8c34688d98ef3c3425fbd70ff5b59d26183a18a15506bbad3adea0c1 Canonical lineage: Shawn Blackmore -> Blackmore Technology Group -> ENTITY -> v3.4.2. Earlier ENTITY releases remain immutable historical provenance and are superseded for current deployment and conformance purposes. External ADAM promotion gates including RUST_COMPILED_QUALIFIED, REAL_WORLD_TRAINING, hardware-backed key custody, physical multi-host qualification, certified-device pilot, 30-day wall-clock operation, independent security audit and independent assessor receipt remain post-release qualification work and are not claimed complete by this release.

ENTITY v3.4.1 — SUPERSEDED — Protocol Origin Lineage & Sovereign User Bootstrap

SUPERSEDED / UNSUPPORTED FOR CURRENT DEPLOYMENT

ENTITY v3.4.1 is retained as immutable historical provenance. The current supported canonical release is v3.4.2.

ENTITY v3.4.1 ΓÇö Protocol Origin Lineage & Sovereign User Bootstrap ENTITY v3.4.1 is a qualified patch release correcting the fresh-bootstrap protocol-lineage defect identified after v3.4.0. ## Release integrity - Protected main commit: 9822b1b65f8269ebc17208a342809720729ae2f8 - Protected main tree: 17eadf6801748ee34eb35bcb999bd0f043805e73 - Signed immutable tag: v3.4.1 - Post-tag release-origin body SHA-256: ad4649d5d7947b08359fad365fe8c4facd958e915ab2b5808676c506bfad56a4 - ENTITY_CURRENT_RELEASE_ORIGIN.json SHA-256: d81bc3bdd6fab5acf8d923eccf24210ac1c65970826ad1f11fbe03f07aa0caa8 The release-origin sidecar is signed by the canonical ENTITY protocol identity and binds this tag to the exact release commit and tree without creating a self-referential commit hash. ## Qualification - Full ENTITY regression: 185/185 PASS. - Protocol-origin, migration and economic-lineage tests: 8/8 PASS. - Global Passport/package tests: 33/33 PASS. - Sealed Global Passport campaign: 24/24 PASS ΓÇö 12 valid and 12 invalid vectors. - Canonical result SHA-256: ac7504cce70576008cff069607619660a4b9bf0cad43b3f3de81078f1e80d9ba. - Rust, TypeScript, Go, C#, Java and Swift BTG-controlled qualification workflows: PASS. - Six executable domain implementation packages: PASS. ## Corrected behavior - Fresh users do not become issuer/originator of canonical ENTITY profiles. - Canonical protocol ancestry remains Shawn Blackmore ΓåÆ Blackmore Technology Group Limited ΓåÆ ENTITY ΓåÆ immutable release. - User asset provenance and user control remain independent from protocol origin. - Existing v3.4.0 user Entity IDs, objects, Rights Passports and signed Global Passports remain unchanged. - Historical deployer-signed profile variants remain verifiable by body hash. - New v3.4.1 issuance fails closed without the exact verified current-release origin sidecar. - Data-economy lineage remains attached to the actual data/instrument originator and explicit signed terms; protocol tax remains 0 bps. ## Claim boundary The six native implementations are BTG-controlled reproducibility evidence, not unrelated third-party interoperability. Independent external implementation/live interoperability, independent security or cryptographic review, deployment-specific legal/regulatory treatment, real external market adoption and external standards-governance adoption remain external milestones. Historical release tags remain immutable. This release does not rewrite earlier release history.

v3.4.0 — SUPERSEDED / UNSUPPORTED

SUPERSEDED / UNSUPPORTED

This release is retained solely as immutable historical provenance in the canonical ENTITY lineage. It is not a current deployment or conformance target. Removing or replacing the canonical Shawn Blackmore -> Blackmore Technology Group -> ENTITY ancestry creates a derivative implementation, not canonical ENTITY.

ENTITY v3.4.0 ΓÇö Global Passport & Continuous Provenance ENTITY v3.4.0 turns the existing sovereign authority, rights, evidence and economic architecture into a more directly deployable developer surface without changing the five core primitives: ENTITY ΓåÆ AUTHORITY ΓåÆ RIGHT ΓåÆ EVENT ΓåÆ VALUE The release introduces one universal ENTITY Global Passport that can carry a composable stack of jurisdiction, industry, privacy, trust and technical profiles. Industry packages populate that passport; they do not create incompatible industry-specific passports. ## Primary additions 1. Global Passport Envelope. 2. Fail-closed Composable Profile Stack. 3. Signed, immutable Versioned Global Profile Registry. 4. Versioned Standards Mapping Framework. 5. Continuous Provenance and Passport Derivation. 6. Executable Industry Implementation Packages and deployment SDK/CLI. The operational adoption concept is simple: give this digital or physical asset an ENTITY Passport. ## Executable implementation packages The first v3.4 package families are: - Healthcare ΓÇö HL7 FHIR and DICOM mappings. - Finance ΓÇö ISO 20022, FIX and LEI mappings. - Manufacturing ΓÇö OPC UA and Asset Administration Shell mappings. - AI ΓÇö NIST AI RMF, SPDX 3 and CycloneDX mappings. - Robotics ΓÇö ROS 2 and Open-RMF mappings. - Defence-public ΓÇö public/unclassified asset, originator, custody and provenance patterns; classified material is explicitly rejected by this package. Packages include pre-engineered object types, profile composition, rights defaults, evidence expectations, privacy defaults, mapping rules, templates, configuration schemas, positive/negative conformance fixtures and quick-start material. Developers configure organization-specific facts rather than redesigning ENTITY. The deployment model is: Select package ΓåÆ configure organization facts ΓåÆ connect systems/data ΓåÆ ingest ΓåÆ verify passport ΓåÆ run conformance ΓåÆ deploy. External standards remain externally authoritative. ENTITY mappings state correspondence under a mapping version; they do not redefine those standards or claim normative equivalence. ## Qualification - Full ENTITY regression: 177/177 PASS. - v3.4 Global Passport/package targeted tests: 33/33 PASS. - Sealed v3.4 conformance campaign: 24/24 PASS ΓÇö 12 valid and 12 invalid vectors. - Sealed kit SHA-256: 5869a3fd0ed6cb9f65bf4b20c3bd64933cad82f4aef05c5809e2e05af921f230. - Global Passport schema SHA-256: 4fbfed9be1b1484bc5d28b8101d1c908b2ccced13e4e99ec896c5b054892ebdd. - Canonical cross-language result SHA-256: ac7504cce70576008cff069607619660a4b9bf0cad43b3f3de81078f1e80d9ba. - Rust, TypeScript, Go, C#, Java and Swift BTG-controlled native implementations all passed the same campaign in protected repositories. - Clean CLI deployment smoke test passed through initialization, package planning, ingestion and Global Passport verification. ## Permanent boundaries A passport is not proof that an external assertion is objectively true. Cryptographic verification proves integrity and attribution within its scope. Profiles do not create sovereign authority. Package validation does not establish regulatory compliance. Provider custody does not create ENTITY authority. Market observations do not become accounting fair value. Information bytes remain nonrival; economic scarcity resides in explicitly bounded rights or interests. The six native implementations are BTG-controlled interoperability evidence, not unrelated third-party independence. Unrelated external implementation/live interoperability, independent security review, deployment-specific legal/regulatory treatment, and real external market adoption remain external milestones.

v3.3.0 — SUPERSEDED / UNSUPPORTED

SUPERSEDED / UNSUPPORTED

This release is retained solely as immutable historical provenance in the canonical ENTITY lineage. It is not a current deployment or conformance target. Removing or replacing the canonical Shawn Blackmore -> Blackmore Technology Group -> ENTITY ancestry creates a derivative implementation, not canonical ENTITY.

ENTITY v3.3.0 - Verifiable Reality, Evidence and Economic Causality ENTITY v3.3.0 extends the protected v3.2.0 adoption release with an explicit evidence layer connecting external-world claims to governed ENTITY state. ## Added - first-class signed Evidence Objects; - typed claim states including observed, asserted, inferred, attested, externally verified, adjudicated, disputed, revoked and unknown; - scope-limited and revocable attestation authority; - external reality anchors and snapshots that remain evidence rather than automatic ENTITY authority; - contestability and supersession with preserved historical state; - evidence-backed causal economic nodes and edges; - sealed 20-vector verifiable-reality clean-room kit; - professional developer gateway, engineering-evidence ledger and graduated interoperability challenge. ## Preserved The five core primitives remain ENTITY, AUTHORITY, RIGHT, EVENT, VALUE. The market lifecycle remains: DCO -> Instrument -> Listing -> Disclosure -> Order/RFQ/Auction -> Price Discovery -> Trade -> Clearing -> Settlement -> Entitlement -> Usage -> Derived Output -> Economic Consequence v3.2 Rights Passports and adoption semantics compose without rewrite. ## Qualification - complete regression: 144/144 PASS; - targeted v3.3 suite: 16/16 PASS; - sealed v3.3 reality vectors: 20/20 PASS (10 valid / 10 invalid); - canonical sealed kit SHA-256: f8b39ee01fb7346f33a57530e925b545d2bf9a770c7ec60724e28a4971d55a46; - schema SHA-256: 6e1c7e621e0aa84627e009febf8999503b7a61f92627b885ed10a19f2ef7d767; - deterministic result SHA-256: 82bd1f1fb328edd37a26d8ea60ede5a599c7d9af5027bffd73b9e52843b5a51d; - release overlay: 22/22 files verified; - overlay snapshot SHA-256: 35dcb51846abda0d7ced7aa5e40c95f34c2504a2393bd1222f5d21ceb0427c26; - composed release snapshot SHA-256: a5b19ae2e698b7170dc060d468f0b6f27fe462204c80d0f3b61ba6ffc7779642; - protected release commit: 9c79f987207592cb6791e1a8956f23351cdfb2d3 (GitHub-signed and verified). ## Permanent boundary ENTITY does not claim that a valid signature, valid protocol transition or external attestation makes a real-world statement objectively true. v3.3 makes those distinctions explicit and machine-readable. BTG-controlled qualification is not unrelated third-party validation. Independent implementation/interoperability, independent security review, deployment-specific legal/regulatory determinations and external market liquidity remain separate milestones.

v3.2.0 — SUPERSEDED / UNSUPPORTED

SUPERSEDED / UNSUPPORTED

This release is retained solely as immutable historical provenance in the canonical ENTITY lineage. It is not a current deployment or conformance target. Removing or replacing the canonical Shawn Blackmore -> Blackmore Technology Group -> ENTITY ancestry creates a derivative implementation, not canonical ENTITY.

ENTITY v3.2.0 ΓÇö Adoption Layer and Rights Passport Infrastructure ENTITY v3.2.0 is an additive adoption release built directly on the protected v3.1.0 global-infrastructure and Data Economic Sovereignty baseline. It does not redesign the five core primitives and it does not replace the existing ENTITY Exchange Protocol market lifecycle. The governing abstraction remains: ENTITY → AUTHORITY → RIGHT → EVENT → VALUE The preserved economic lifecycle remains: DCO → Instrument → Listing → Disclosure → Order/RFQ/Auction → Price Discovery → Trade → Clearing → Settlement → Entitlement → Usage → Derived Output → Economic Consequence ## What v3.2 adds ### ENTITY Rights Passport A signed, immutable, versioned Rights Passport can now bind an existing ENTITY object to: - controller and authority references; - machine-readable rights and prohibitions; - jurisdiction-profile references; - semantic/ontology references; - provider-neutral custody locators; - provenance and disclosure references; - privacy profile; - economic terms; - external legal-classification assertions. The passport explicitly preserves these boundaries: - custody provider is not sovereign authority; - moving storage providers does not change the ENTITY object identity; - underlying information is not silently transferred by a rights instrument; - information bytes do not have to be artificially scarce; - legal classification remains dependent on external authoritative law/evidence. ### Standards adapters v3.2 adds explicit translation/evidence adapters for: - W3C ODRL; - W3C Verifiable Credentials; - DIDs; - Gaia-X; - International Data Spaces. Mappings are explicit crosswalks. ENTITY does not silently declare semantic equivalence and an external standard or credential does not automatically become ENTITY authority. ### Provider-neutral connectors The adoption layer can describe custody in: - AWS S3; - Azure Blob; - Google Cloud Storage; - Snowflake; - Databricks; - PostgreSQL; - SQL Server; - local filesystems; - HTTP/API endpoints. These locators contain no provider credentials and do not grant authority to the infrastructure provider. ### Developer adoption facade The new adoption SDK composes existing v3 rights, jurisdiction, resolution and exchange profiles through a smaller developer-facing surface. It does not acquire authority and it does not bypass the underlying profiles. ### Federated resolver deployment v3.2 exposes a fail-closed federated resolver deployment profile requiring multiple resolvers. Resolver participation itself does not create sovereign authority. ## Market structure remains intact The existing ENTITY Exchange Protocol remains the market engine. v3.2 does not replace: - Digital Commodity Objects; - rights instruments; - listings; - signed orders; - RFQs; - auctions; - price discovery; - clearing; - settlement; - entitlements; - usage metering; - derivative participation; - EOPP originator participation; - treasury positions. Instead, v3.2 makes those instruments easier for outside systems to understand, locate, map to standards, verify and use across providers and jurisdictions. ## Qualification - Official v3 regression: 128/128 PASS. - Targeted v3.2 adoption tests: 12/12 PASS. - Sealed adoption conformance vectors: 8 valid + 8 invalid. - Sealed compact kit SHA-256: 44e7a00f910c89aced3b3c1b5e9cba486809ca313e9bfb4b7bc9266095c10c14. - Common six-language v3.2 result SHA-256: 1eb59e09ab08da86bfd8584df4a64ba331f7bbbce3d236b9b94f351606c90e18. - Native BTG-controlled implementations: Rust / TypeScript / C# / Go / Swift / Java ΓÇö PASS. Each clean-room repository runs its inherited v3.1 campaign and then independently evaluates the pinned v3.2 sealed kit in its native runtime. ## Release lineage v3.2.0 is based on protected v3.1.0 commit: b985b7cf875bdeeadb228d4d1885395cbcaf19f1 The qualified v3.2 source/kit point is: ee3587a6e65c2565eaab2e815e85415ab705ea47 This preserves the v3.0.1 and v3.1.0 histories rather than rewriting them. ## Claim boundary The six implementations remain BTG-controlled. This release does not claim unrelated third-party implementation, independent external cryptographic/security review, deployment-specific legal approval, or demonstrated external market liquidity. Those remain external qualification and commercialization milestones.

v3.1.0 — SUPERSEDED / UNSUPPORTED

SUPERSEDED / UNSUPPORTED

This release is retained solely as immutable historical provenance in the canonical ENTITY lineage. It is not a current deployment or conformance target. Removing or replacing the canonical Shawn Blackmore -> Blackmore Technology Group -> ENTITY ancestry creates a derivative implementation, not canonical ENTITY.

ENTITY v3.1.0 ΓÇö Global Infrastructure and Data Economic Sovereignty ENTITY v3.1.0 is a feature release built on the security-hardened, internally qualified v3.0.1 base. It keeps ENTITY Core small and adds independently versioned profiles for the semantic, institutional, privacy and topology pressures that arise when sovereign digital infrastructure crosses organizations and jurisdictions. ## Data Economic Sovereignty Doctrine v3.1.0 formally adopts the Data Economic Sovereignty Doctrine. Data may represent economically valuable productive capital, but ENTITY does not require artificial scarcity of information itself. Information can remain non-rival and technically copyable while scarce economic interests are expressed as explicit machine-verifiable rights, entitlements, capacities, durations, jurisdictions, usage quantities, derivation rights, participation rights and transferability constraints. Those bounded interests may be issued, reserved, licensed, transferred, traded, cleared, settled, exercised, revoked, superseded or extinguished under their governing terms. Originator participation may continue through primary issuance, secondary exchange, derivative creation or later economic use only where the participation interest was validly established. > ENTITY establishes market infrastructure through which data can become measurable economic capital. > ENTITY transforms data from an opaque digital possession into a provenance-backed economic asset whose rights can be defined, issued, exchanged, exercised and economically accounted for. ## Global infrastructure profiles The release adds implemented and tested profiles for: - jurisdiction/domain overlays with effective dates, precedence, supersession and fail-closed conflict detection; - governed semantic namespaces, immutable ontology terms and explicit signed crosswalks; - multi-stakeholder standards governance with stakeholder-class diversity and recusal; - purpose-bound access, selective retention/destruction, confidential provenance and proof-verifier interfaces; - core/regional/edge/satellite/offline topology, partition checkpoints and conflict handling; - cryptographic-suite transition with dual-sign migration and downgrade resistance. These mechanisms are profiles above ENTITY / AUTHORITY / RIGHT / EVENT / VALUE; they do not turn infrastructure possession, ontology publication or governance participation into sovereign authority. ## Qualification - Complete corrected-base regression: 116/116 PASS. - New global/doctrine targeted tests: 22/22 PASS. - Sealed global conformance vectors: 8 valid + 8 invalid. - Six BTG-controlled native clean-room implementations: Rust / TypeScript / C# / Go / Swift / Java - PASS. - Common v3.1 clean-room result SHA-256: 879c8e1eba2549a9a1962605760b715b0fd47d3ea640fb9c6f29be5c63cfb8c5. - Feature evidence snapshot: a26be5480b94f7669d41158cbceb1e8d31146afbbcba88f3ee4857c323cf25fc. ## Economic and legal boundaries ENTITY v3.1.0 is not a cryptocurrency and introduces no mandatory protocol token or protocol tax. The open protocol does not declare copied bytes to be scarce property. EEP instruments must identify the bounded right or entitlement being exchanged and cannot silently transfer ownership of underlying information. Protocol records do not themselves determine legal title, statutory meaning, accounting or market fair value, regulatory classification, or objective bank/payment truth. Those remain dependent on applicable law, external authorities/evidence and deployment context. ## External qualification still required BTG-controlled cross-language reproducibility is complete for this profile set, but v3.1.0 does not claim unrelated third-party implementation, independent external cryptographic review, or deployment-specific legal/regulatory approval. Those remain external milestones. v3.0.1 remains immutable release history. v3.1.0 supersedes it as the current feature release without rewriting the v3.0.1 tag or evidence.

v3.0.1 — SUPERSEDED / UNSUPPORTED

SUPERSEDED / UNSUPPORTED

This release is retained solely as immutable historical provenance in the canonical ENTITY lineage. It is not a current deployment or conformance target. Removing or replacing the canonical Shawn Blackmore -> Blackmore Technology Group -> ENTITY ancestry creates a derivative implementation, not canonical ENTITY.

ENTITY v3.0.1 Release Notes Released: 2026-09-23 Qualification: BTG internally qualified maintenance release ENTITY v3.0.1 is a security-hardening maintenance release for the v3.0.x protocol/reference line. It preserves v3.0.0 EEP/EOPP/MSRP market semantics while strengthening signing-key lifecycle verification and publishing the completed BTG-controlled post-release qualification evidence. ## Security hardening - Enforce signing-key created_at_ms for v2 signature records. - Enforce retired/revoked key cutoffs while preserving signatures made before the cutoff. - Remove obsolete local operational private-key material after successful key rotation/recovery. - Add dedicated regression and randomized adversarial coverage. ## Qualification closeout - 94/94 patched regression PASS. - Five controlled native language implementations converge on identical v3 state/recovery/result roots. - 1,000,000 assets + 3,000,000 events with signed Merkle evidence and destructive restore PASS. - 4,000 fully settled scale trades PASS. - 900-second operational soak PASS. - Internal crypto/privacy and regulatory-engineering tracks closed for the documented scope. Unrelated third-party interoperability, independent external security review, and deployment-specific regulatory/legal determinations remain external by definition.

v3.0.0 — SUPERSEDED / UNSUPPORTED

SUPERSEDED / UNSUPPORTED

This release is retained solely as immutable historical provenance in the canonical ENTITY lineage. It is not a current deployment or conformance target. Removing or replacing the canonical Shawn Blackmore -> Blackmore Technology Group -> ENTITY ancestry creates a derivative implementation, not canonical ENTITY.

ENTITY v3.0.0 Release Notes Released: 2026-09-23 Qualification: BTG internally qualified ENTITY v3.0.0 introduces the provider-independent sovereign state and data-rights market architecture built around ENTITY, AUTHORITY, RIGHT, EVENT and VALUE. ## Major release components - Universal Transaction Fabric and sovereign object lifecycle. - Versioned profile architecture with schema immutability and negotiation. - ENTITY Exchange Protocol (EEP) for trading rights in data. - ENTITY Originator Participation Profile (EOPP). - Market State Recovery Profile (MSRP). - Privacy, dispute, recovery, federated-resolution, AI-delegation and physical-binding profiles. - EEP JSON Schema and sealed valid/invalid conformance vectors. ## Release qualification The release gate includes the complete v3 regression, EEP conformance vectors, reference/mirror convergence, adversarial authorization and concurrency campaigns, EOPP accounting/economic-integrity tests, destructive market recovery and a bounded 500-settled-trade load run. This release does not claim external unrelated-party v3 interoperability or production exchange certification. Those remain explicit post-release qualification tracks. See docs/qualification/ENTITY_V3_0_0_RELEASE_QUALIFICATION_2026-09-23.md and ENTITY_V3_RELEASE_MANIFEST.json for the evidence and claim boundary.

v1.0.0-rc2.2 — HISTORICAL / UNSUPPORTED

HISTORICAL / UNSUPPORTED

This release is retained solely as immutable historical provenance in the canonical ENTITY lineage. It is not a current deployment or conformance target. Removing or replacing the canonical Shawn Blackmore -> Blackmore Technology Group -> ENTITY ancestry creates a derivative implementation, not canonical ENTITY.

ENTITY 1.0.0-rc2.2 Repository-wide Unicode/UTF-8 repair release for Blackmore Technology Group's provider-independent sovereign digital authority protocol and reference implementation. RC2.2 supersedes v1.0.0-rc2.1 for public checkout and use. Earlier RC2 tags remain immutable release history. ## What RC2.2 fixes The public repository contained UTF-8 mojibake in multiple text/source files, including README box-drawing characters such as ??? being rendered as malformed Windows-1252 text. RC2.2: - repairs 219 malformed UTF-8 sequences across 61 tracked files; - restores box-drawing characters, em dashes, arrows, quotes and related Unicode text; - corrects the README repository tree and includes 08_Data_Vaults; - adds .editorconfig with UTF-8/LF defaults; - adds an automated repository-safety test that rejects invalid UTF-8, Unicode replacement characters, and reconstructable Windows-1252/UTF-8 mojibake; - preserves the existing security checks for live bindings, credentials, private keys, state databases and backups. ## Protocol compatibility There is no ENTITY Protocol 1.0 semantic change in RC2.2. - ENTITY Protocol: 1.0 - FROZEN_FOR_EXTERNAL_CONFORMANCE - Master requirements: SERS-ENTITY-003 v2.2 - 172 normative sections - Sovereign Domain profile: SERS-ENTITY-DOMAIN-001 v1.0 - Independent external interoperability qualification: PENDING The hash-pinned engineering requirements were not modified by the Unicode repair. ## Validation - repository-wide mojibake scan: 0 findings after repair - Unicode replacement-character scan: 0 findings - JSON validation: PASS - Python compileall: PASS - clean-clone public contract/repository-safety tests: 5/5 PASS - GitHub Actions Ubuntu run 35293194570: SUCCESS - local main, GitHub main, and RC2.2 tag commit verification: PASS ## Source commit dca93ae228ed39e4441138822ec0d0972b970f2c Licensed under Apache License 2.0.