ENTITY Documentation Portal
ENTITY v3.4.3 · mandatory factory production contract

DCO Production Pipeline

A DCO is not ready for economic issuance merely because it has a name and supply. The factory now requires a qualified underlying asset, sealed provenance, both passport layers, profile/BTDU binding and only then economic instruments.

BUILD ASSET → QUALIFY / TEST → SEAL PROVENANCE → REGISTER DCO → RIGHTS PASSPORT → GLOBAL PASSPORT → ROBOTICS / AI / BTDU BINDING → EEP INSTRUMENTS → OPTIONAL SHARED BRIDGE → PUBLIC-SAFE EVIDENCE

Rights Passport

The Rights Passport is the rights layer around the underlying object. It records allowed, required and prohibited actions; conditions; obligations; authority and jurisdiction references; custody locators; provenance/disclosure references; privacy profile and economic terms.

Custody is not authority. A storage provider or external system cannot silently become the controller of the asset.

Global Passport

The Global Passport binds the verified Rights Passport to qualification evidence, provenance, jurisdictional context, industry profiles, standards mappings, economic state and the BTDU reference where appropriate.

Robotics/AI DCOs can compose global, robotics, ai and manufacturing profiles without creating separate passport protocols.

BTDU binding modes

Exact BTDU atomization is preferred when the universe can be recovered inside the available process memory. A Global Passport can also carry an explicit content-addressed BTDU reference binding when full recovery/atomization is deferred. That mode must say so; it must not claim that bytes were atomized when they were not.

Either mode preserves the same boundary: BTDU topology creates neither ownership nor economic entitlement.

Shared bridge rule

100 DCOs do not imply 100 software bridges. Many DCOs bind to a small set of reusable integration families.

The first shared robotics family is ENTITY_ROBOTICS_INTEGRATION, with correspondence for ENTITY API, ROS 2, Open-RMF and external custody/data systems. A DCO binding records enabled interfaces and exposure mode; it does not create rights.

Public-safe publication

Public manifests may expose DCO ID, name, class, hashes, controller/originator, version, public rights summary, passport hashes, qualification hash, benchmark summary, public provenance references and economic state.

They reject live object/instrument/wallet/treasury IDs, runtime paths/databases, credentials, private keys, private settlement details and customer entitlements.

Economic-state boundary

POTENTIAL → OFFER → CONTRACTED → ACCRUED → SETTLED → REALIZED

Passports and supply do not manufacture value. A newly qualified DCO can correctly remain at POTENTIAL / CAD 0 until real market activity changes its state.