ENTITY Documentation Portal
Developer manual · ENTITY v3.4.3 · portable governed state

Global Passport API

Version boundary: ENTITY v3.4.3 is the current runtime. Global Passport is part of that current runtime. When a passport carries a BTDU binding, BTDU remains component version 3.4.2 unchanged.

The Global Passport is a portable signed envelope over existing ENTITY objects, Rights Passports, evidence, provenance, profiles and economic context. It is not a new sovereignty root and it does not make a profile, provider or standards mapping authoritative over the underlying Entity.

Implemented composition

ENTITY object + Rights Passport → profile stack → evidence/provenance refs → jurisdiction/standards context → economic state → optional BTDU binding → Global Passport

The registry verifies that the object/controller and Rights Passport match, resolves the exact profile stack, binds standards mappings without claiming normative equivalence, records economic state without calling observations accounting fair value, and signs the resulting immutable passport version.

Profiles

Profiles are versioned constraint/interpretation layers. A deployment can compose global, jurisdictional, industry, privacy, trust and disclosure profiles. Profile composition explicitly does not create authority.

Standards mappings

Mappings describe correspondence between ENTITY and external standards. They must not claim normative equivalence. The external standard remains authoritative for its own semantics.

BTDU binding

A BTDU binding can carry universe_root, object_ref, content_sha256 and sovereign_entity_id. Boundary flags require that protocol origin is not asset provenance, topology does not create ownership and topology does not create economic entitlement. For the v3.4.2 BTDU-bound profile, the implementation also prohibits an automatic protocol royalty.

Verification order

  1. Validate schema/core primitives and boundary flags.
  2. Verify the referenced Rights Passport.
  3. Resolve exact profile versions/hashes.
  4. Check standards mappings preserve non-equivalence.
  5. Verify any BTDU binding and protocol-origin binding.
  6. Recompute the passport body hash.
  7. Verify controller signature.
  8. Keep objective-truth and legal-compliance conclusions outside the passport unless separately evidenced.

Domain packages

Healthcare, Finance, Manufacturing, AI, Robotics and Defence/Public-Unclassified are deployment profiles/packages over the same passport model. They do not create separate passport protocols.

Historical relationship

v3.4.2 remains the historical predecessor release and the current BTDU component version. Historical passports/evidence remain under their original labels; the current overall runtime label is v3.4.3.