ENTITY v3.4.2 + BTDU 3.4.2
ENTITY v3.4.2 is preserved as the immutable release that introduced the Blackmore Technology Data Universe and a large portion of the current digital-economic architecture. It is superseded for current ENTITY deployment by v3.4.3, but its exact release evidence remains historically authoritative for the campaigns that tested it.
What v3.4.2 established
BTDU
Governed atomic/bonded information topology layered on ADAM under ENTITY authorization.
Economic architecture
The five primitives and the DCO → instrument → market → settlement → entitlement → usage → consequence lifecycle were preserved as the economic semantics around the information universe.
Canonical lineage
Protocol origin/stewardship evidence remained explicit without converting canonical origin into downstream asset ownership or automatic royalties.
Qualification evidence
Release-specific tests, hashes, clean-room material and later qualifications remain attached to v3.4.2 rather than being silently relabeled as v3.4.3.
BTDU remains active as component 3.4.2
BTDU itself was not changed by the v3.4.3 remediation. The current ENTITY runtime still uses BTDU 3.4.2 as its governed information component. Therefore this archive remains important for BTDU implementation/evidence history even though the ENTITY runtime label advanced.
Economic semantics carried forward
Current documentation for the implemented exchange, participation and recovery system lives in the current portal. Use this archive when the exact v3.4.2 implementation or historical evidence scope matters.
Historical evidence rules
- v3.4.2 tags, commits, hashes and receipts remain immutable historical evidence.
- Compiled Rust / real-world BTDU qualification evidence inherited by v3.4.3 retains the v3.4.2 source scope where unchanged.
- Historical clean-room campaigns may intentionally target v3.4.2.
- Historical evidence does not mean v3.4.2 is the current deployment target.
- BTDU 3.4.2 continuing inside v3.4.3 does not make the whole runtime v3.4.2.