ENTITY itself · core curriculum
Learn ENTITY from the primitives outward
This is the primary ENTITY tutorial track. It teaches the system itself—not the external contribution campaign. The Vector, Memnox and AWS work remains useful as real-world evidence, but it is a case study after you understand the core fabric.
ENTITY → AUTHORITY → RIGHT → EVENT → VALUE
Everything else in the platform composes around those primitives: governed objects, authority delegation, machine-readable rights, evidence and trust, encrypted information, BTDU topology, deterministic ADAM state, bounded NIKI reasoning, passports, privacy controls, global/offline topology, market execution, settlement and provider-independent recovery.
Learning rule: every tutorial asks the same questions: What exists? Who may act? What right exists? What event occurred? What evidence supports it? What value or obligation followed? Can the state be recovered without silently changing authority?
Core curriculum
1 · Five primitives & governed objectsRegister real objects and understand why ENTITY, AUTHORITY, RIGHT, EVENT and VALUE are separate state.2 · Delegate and revoke authorityGrant bounded ACT/SIGN/ACCESS_DATA/EXECUTE/PURCHASE/LICENSE/SETTLE/PUBLISH/RESOLVE/DELEGATE/CONTROL authority and prove revocation.3 · Grant, constrain and revoke rightsWork with INSPECT/READ/COPY/DERIVE/TRAIN/INFER/EXECUTE/MODIFY/REDISTRIBUTE/COMMERCIALIZE/CONTROL/TRANSFER.4 · Encrypt data and control purpose-bound accessUse the owner-controlled vault, purpose/action grants, expiry, use caps and revocation without placing plaintext on the ledger.5 · Evidence, attestations and trust policiesCreate claims backed by evidence hashes and evaluate threshold/allowed/required attestor policies without declaring evidence to be objective truth.6 · Provenance and economic lineageConnect parent/child objects, deterministic contribution weights and explicit VALUE states without converting provenance into ownership.7 · BTDU, ADAM and NIKI boundariesUnderstand governed information topology, deterministic state/replay and bounded causal reasoning—and which subsystem is allowed to create authority.8 · Rights passports and global passportsPackage existing rights, evidence, profiles, custody references, economic state and BTDU bindings into portable signed envelopes.9 · Privacy, retention and evidenced destructionUse selective disclosure, confidential provenance, retention periods, legal holds and destruction evidence.10 · Federated, edge and offline operationRegister CORE/REGIONAL/EDGE/SATELLITE/OFFLINE nodes, create offline envelopes and recover partitions without last-writer-wins.11 · Run the economic fabricConnect rights instruments to listings, disclosures, orders/RFQs/auctions, trades, clearing, settlement, entitlements, usage and revenue rules.12 · Provider-independent recoveryExport, verify and restore identity/rights/evidence/information/economic state as logical signed state instead of provider-owned database bytes.13 · Standards and industry adoptionMap ENTITY into existing standards and industry profiles without claiming false normative equivalence or allowing adapters to mint authority. Where the contribution campaign belongs
After the core curriculum, use the external contribution lineage case study and the contribution-economy scenario to see the fabric applied to Vector, Memnox and the active AWS contribution. Those are examples of ENTITY in the world, not the definition of ENTITY.