ENTITY Documentation Portal
Developer reference · ENTITY v3.4.3

SDK Reference

Post-tag DataChip SDK and application hosts

EDCF v0.2 DataChip/EDP and Universal Composer architecture documents the newer formula-native reference SDK, signed-grant test tooling, read-only registry bridge, assembly graphs, Rust C ABI and Swift adapter candidate. Portable `.edc` v0.1 remains a distinct format. Production Swift/Android/Windows ABI parity, live export rights, signed revocation and independent field-device qualification are still pending. The protected v3.4.3 SDK guidance below is not automatically upgraded by engineering changes on main.

Current support boundary: production integrations should pin to the supported v3.4.3 release or exact release commit 528b70aabd05b1e930b77e4933f157731e47274f. BTDU remains component version 3.4.2 unchanged. Use v3.4.2 only for explicitly historical qualification/reproduction work.

ENTITY's SDK layer is the preferred application boundary. Applications should use SDK/runtime surfaces to request scoped actions rather than directly editing state files or impersonating sovereign identity.

Implemented SDK boundary: Python reference SDKs, application binding, Global Passport tooling and JSON schemas exist. The sdk/apple_sdk, sdk/android_sdk, sdk/web_sdk and sdk/windows_sdk folders carry subsystem requirements, not verified full native authority SDKs. A desktop wallet and iOS portable-snapshot inspection client are not mobile signing/settlement parity. Later changes on main require exact-commit qualification. See Current implementation and qualification status.

SDK areas

AreaUse
sdk/simple_sdk/Minimal developer facade for common ENTITY operations.
sdk/global_passport_sdk/Global Passport construction/verification and profile/package workflows.
Principal/device/application bindingSeparates the producer application from the asset controller and requires explicit binding before canonical ingestion.

Integration principles

BTDU

BTDU exposes operator CLI and Python runtime surfaces under src/40_BTDU. In ENTITY v3.4.3 the BTDU component remains 3.4.2 unchanged. Applications integrating BTDU should keep ENTITY authorization as the mutation gate and treat ADAM/BTDU as state/information infrastructure rather than authority.

Version pinning

Pin production behavior to v3.4.3 or the exact v3.4.3 release commit. Do not depend on moving main when immutable semantics matter. When reproducing a sealed v3.4.2 campaign, use its historical tag and evidence exactly rather than translating the result into a v3.4.3 test claim.