ENTITY Documentation Portal
Architecture overview · non-normative for Protocol 1.0

BTDU — Blackmore Technology Data Universe

How BTDU formulas become DataChips

BTDU is ENTITY's governed information and reconstructive formula foundation. Experimental EDCF v0.2 exposes bounded portable formula-plus-entropy content to an independent DataChip Processor; it does not replace the authoritative BTDU object, erase source, or grant export rights. The DataChip architecture, native-host boundary and Composer are documented as post-release engineering, separate from frozen Protocol 1.0 semantics and the protected ENTITY v3.4.3 tag.

BTDU means Blackmore Technology Data Universe. It is a governed information-substrate component used by the current ENTITY runtime architecture; it is not part of the normative ENTITY Protocol 1.0 clean-room conformance target.

What BTDU is

The published BTDU architecture contract describes BTDU as a governed universal information substrate. The current public ENTITY documentation describes it as an atomic/bonded information architecture in which reusable atoms, bonds and compounds can be connected to ENTITY provenance, authority, rights and economic state.

Atoms → Bonds → Compounds → Governed Objects → Provenance / Rights / Economic Lineage

BTDU is a representation model for structured, semantic and relational information. It is not presented as generic raw-file compression.

Architecture roles

ComponentPublished role
ENTITYAuthority and rights.
ADAMDeterministic state engine.
NIKIReasoning consumer.
BTDUGoverned universal information substrate.

Version boundary

ENTITY v3.4.3 is the current supported runtime. The BTDU component remains version 3.4.2 unchanged inside that runtime release.

Post-tag formula-storage implementation (2026-10-12)

Current main includes src/40_BTDU/formula_kernel.py and storage_kernel.py. BTG local migration/verification receipts report 4,933/4,933 formula bindings and exact reconstruction for their tested scope. Formula reconstruction still requires retained entropy for information that cannot be derived from reusable structure. The measured local full BTDU subtree includes separate atomic checkpoints and indexes; small primary-formula byte ratios must not be advertised as full-disk savings or universal compression. The protected v3.4.3 tag remains unchanged. Current implementation and qualification status.

Protocol 1.0 boundary

If you are implementing ENTITY Protocol 1.0 from the sealed conformance kit, you do not need to implement BTDU, ADAM or NIKI.

The Protocol 1.0 clean-room challenge is defined by the sealed conformance kit: the interoperability profile, canonicalization/cryptography rules, schemas, implementation interface, vectors and pass criteria. The clean-room rules exclude BTG runtime internals such as ADAM and NIKI from the implementation path.

The BTDU example on the AUTHORITY page is therefore only an illustration of how ENTITY authority can be applied by a current BTG runtime component. It is not an additional Protocol 1.0 requirement.

Why this distinction matters

ENTITY Protocol 1.0
= public interoperability/conformance target

ENTITY runtime v3.4.3
= current BTG implementation/runtime release

BTDU 3.4.2
= runtime architecture component / governed information substrate

Protocol 1.0 conformance
≠ implementing BTDU, ADAM or NIKI

For independent implementation work, treat the sealed Protocol 1.0 conformance kit as authoritative for what must be implemented.