ENTITY Documentation Portal
Post-v3.4.3 engineering snapshot | 13 October 2026

ENTITY DataChips: build interoperable systems from verifiable parts

An ENTITY DataChip is a portable, content-addressed component carrying exact data or a bounded reconstruction recipe, its dependencies and provenance references. An ENTITY Data Processor (EDP) verifies and reconstructs permitted material. Native application hosts supply real operating-system and device capabilities. The Universal DataChip Composer is the emerging typed, visual assembly workspace.

Release boundary: ENTITY v3.4.3 remains the current protected release; BTDU 3.4.2 remains unchanged inside that tag. Formula-native EDCF v0.2, the shared cross-application alignment contract, Composer and wallet integration candidates are later engineering on main and review branches, not a newly certified ENTITY release or a generally available production deployment.

Four parts of a DataChip-based system

LayerResponsibility
Native hostSigned iOS/Android/Windows/Linux application, OS permissions, camera, ARKit/Metal, GPS, renderer, UI, user consent, trusted identity and secure device enrollment.
ENTITY Data Processor (EDP)Strict content verification, deterministic formula reconstruction, dependency and interface checks, bounded execution of approved pure-data operations and fail-closed eligibility decisions.
EDCF v0.2 DataChipPortable exact-content formula DAG with ATOM, ENTROPY, CONCAT, REPEAT and SLICE, pinned content hashes, optional independent shard-set packaging for larger assets.
ENTITY authority and walletSeparate Rights Passport validation, authenticated controller approval, delegated app/subject/action-scoped grants, expiry/revocation, provenance and optional economic instruments. Integrity never creates a right.

Compose by connections, not by inventing permissions

The experimental Universal DataChip Composer works with a versioned typed graph: compatible inputs/outputs, dependency resolution, cyclic-graph and missing-interface rejection, bounded assembly planning and explicit platform capability requirements. A Composer canvas or draft is not a signed, executable native app. The wallet is evolving toward a capability-first DataChip workspace while retaining controller-scoped DCOs, instruments, rights, settlement, lineage, BTDU formula assets and authorized transfers.

Source: DataChip workspace architecture, Composer previews and explicit data-plane rights policy blocker.

Interoperability and measured evidence

A shared EDCF v0.2 lock has been integrated across ENTITY, HuntAR and BTG Command Centre. In the Boundary Country engineering pilot, 34 independently pinned geographic QA chips and their source/archive identities were verified off-device. This is a QA artifact, not licensed, live-authorized production geography. The HuntAR 480 work adds an explicitly user-selected Files import and bounded read-only native QA verifier; a full 34-chip iPhone mount and rendered-map/terrain acceptance have not been independently evidenced.

EDCF v0.2 is not interchangeable with legacy .edc v0.1, and a shard-set manifest is separate from a single-chip formula archive. Do not treat a checksum as proof of publisher identity or a syntactically valid Rights Passport reference as a grant.

Rights and security contract

Verified archive bytes, authenticated publisher identity, legal/control authority, current entitlement and permission to export are separate checks. Signed delegated grants require independently trusted issuer/status keys, proper audience and subject, scoped actions, time limits and fresh revocation evidence. The production Rights Passport audit found existing READ/COPY rules but no explicit EXPORT permissions. The bridge must deny unsupported export until a versioned rights-policy decision and authorized grants exist. Neither the website nor the Composer changes this policy.

Production readiness

CapabilityStatus
Formula-native reference implementation and cross-repository contractEngineering implemented; source tests and QA fixtures exist
Native Rust/C and Swift verification bindingsIntegration candidate; independent 3-OS CI and hardware qualification still required
Signed reference bundles, deployment/rollback and anti-rollbackReference implementation; hardware-backed production anti-rollback not qualified
Wallet typed Composer, DCO bridge and capability-first UIEngineering candidate, not a verified production wallet migration
Live issuer/KMS authorization, revocation distribution and export policyBlocked pending operational qualification and explicit rights governance
Full HuntAR geographic mount, real BSIE overlay, stable NIKI/HUD/map, authorized device evidenceNot yet production-qualified; physical-device acceptance required
Independent hostile-input security assessment and third-party host portabilityOutstanding

Developer starting points

DataChip reference SDK · Native-host architecture · EDCF v0.2 lock · Gate checklist · Evidence status.

The DataChip platform is for BTG applications and potential third-party native hosts, provided each host independently supports the same data contract, trusted permissions, constraints and compatibility checks. It does not distribute arbitrary unsigned executable code or bypass device/App Store restrictions.