ENTITY Documentation Portal
Current implementation status: The immutable v3.4.3 tag and later BTDU/wallet developments are distinct. See built capabilities, measurement scope and outstanding qualification gates.
ENTITY v3.4.3 · operations

Operator Manual

Operate the full ENTITY fabric: identities and keys, governed objects, rights, evidence, market/economic state, passports, security, backup, recovery and provider-independent continuity.

Operational scope: ENTITY is not only identity/recovery infrastructure. Operators may be responsible for venues, rights instruments, balances, listings, orders, trades, clearing, entitlements, usage, revenue rules, treasury participation, settlement-verifier authorizations and payment attestations in addition to authority/evidence state.

Operational domains

Core operating controls

Information and passport workflows

Market-state continuity

VENUES → INSTRUMENTS → BALANCES → LISTINGS → ORDERS / RFQs / QUOTES → TRADES → CLEARING → ENTITLEMENTS → USAGE → REVENUE RULES → SETTLEMENT EVIDENCE

A correct recovery must preserve the economic meaning of this state together with treasury/participation records. Copying database files without semantic verification is not the authority model.

Operational boundary: a running database does not prove lawful authority, a trade row does not prove payment, and restored state must not silently create permissions or rights that did not exist before failure.

Lifecycle & troubleshooting