Learn ENTITY itself
ENTITY Tutorials
The primary tutorial track follows ENTITY's actual architecture—not the external contribution campaign. Start with the five primitives, learn authority and rights, govern real information and evidence, understand BTDU/ADAM/NIKI, then move into passports, privacy, distributed operation, economics and recovery.
ENTITY → AUTHORITY → RIGHT → EVENT → VALUE
Current runtime: ENTITY v3.4.3 with BTDU component 3.4.2. The tutorial layer preserves the same boundaries as the implementation: custody is not authority; access is not ownership; provenance is not truth or automatic royalty; AI inference does not mint rights; trade is not verified payment; recovery does not create missing authority or evidence.
Primary path · Core ENTITY curriculum
Core curriculum · 13 tutorialsThe complete learning path for the platform itself: primitives, authority, rights, encrypted vaults, trust, provenance/value, BTDU/ADAM/NIKI, passports, privacy, federation, economics, recovery and standards.Start: Five primitivesLearn why ENTITY, AUTHORITY, RIGHT, EVENT and VALUE remain separate state and how governed objects fit the model.Authority & delegationDelegate bounded actions, test implicit-escalation failure and revoke authority.Rights & constraintsGrant explicit rights with purpose/jurisdiction/economic constraints and prove unauthorized actions fail.Encrypted information controlsStore content with per-object AES-256-GCM keys and add purpose/action/expiry/use-cap controls.Evidence & trustCreate attestations and threshold trust policies without equating evidence with objective truth.BTDU · ADAM · NIKIUnderstand governed information, deterministic execution/replay and bounded causal intelligence.Passports & profilesPackage rights, evidence, custody, profiles, economic state and BTDU bindings into signed portable envelopes.Federated/offline operationOperate CORE/REGIONAL/EDGE/SATELLITE/OFFLINE nodes with causal checkpoint recovery instead of last-writer-wins.Economic fabricMove governed rights through instruments, venues, orders/RFQs/auctions, clearing, settlement, entitlement, usage and revenue rules.Provider-independent recoveryExport, verify and restore the logical signed system rather than treating database bytes as authority.
Recorded qualification testing
After the tutorials, move into the recorded testing lab for storage, recovery and future qualification campaigns.
Code tutorials - run verified examples
These walkthroughs include exact scripts executed against current ENTITY source, recorded terminal output and fail-closed negative controls.
ENTITY Code TutorialsThirteen runnable tutorials with exact source, transcripts, execution records and browser-safe terminal replays for tutorials 6-13.1 - Create, verify and sign with an ENTITY identityCreate an ent2 identity, verify its manifest, sign a payload and rotate the signing key.2 - Exercise authority, rights and provenanceDelegate bounded authority, constrain rights and compute deterministic provenance allocation.3 - Export and verify a portable sovereign bundleExport a portable bundle, verify it, then prove tampering fails closed.4 - Require two independent attestationsRequire two signed attestations without inferring objective truth.5 - Initialize BTDU and verify the ADAM dependency boundaryInitialize BTDU with the verified ADAM source dependency and inspect runtime status.6 - Encrypt bytes and enforce one-use purpose accessStore encrypted bytes, grant one bounded RESEARCH/READ use, consume it, then prove a second use fails closed.7 - Issue and verify rights and global passportsIssue a rights passport for a governed dataset, register a global profile, then wrap both into a verifiable global passport.8 - Detect a divergent offline partition conflictCreate two EDGE nodes, sign offline work, publish concurrent divergent checkpoints and prove ENTITY refuses automatic last-writer-wins.9 - Execute a rights trade without pretending payment occurredCreate a venue, rights instrument, disclosure and listing, match BUY/SELL orders, then prove execution remains distinct from settlement and external payment.10 - Preserve retention evidence and enforce legal holdDestroy governed payload state while preserving its commitment, then prove a legal hold blocks destruction.11 - Encrypt confidential provenance metadataRecord private lineage metadata, reveal it with the correct key and prove a wrong key fails closed.12 - Map ODRL, VC and DID without importing authorityTranslate ODRL rights and capture VC/DID evidence while preserving ENTITY's authority boundary.13 - Require a 2-of-3 recovery quorumCreate a recovery policy, block an unauthorized approver and require two authorized approvals before readiness.
Developer cookbook · do one thing now
The cookbook complements the tutorials with minimal source-grounded examples you can copy into a disposable checkout/state directory.
Developer RecipesIdentity/signing, object authority and rights, encrypted vaults, trust policies, BTDU CLI, passports, offline partitions, market recovery and standards mapping.Object + authority + rights recipeSmall runnable example with positive and negative authorization checks.BTDU CLI recipeInitialize, ingest, inspect and reconstruct exact governed information.Market recovery recipeExport, verify and restore complete logical exchange/economic state.
Quick-start exercises
These shorter tutorials remain useful when you want one focused task rather than the full curriculum.
Create & sign with an EntityIdentity manifest, operational/recovery keys and signatures.Ingest & reconstruct with BTDUGovern a pinned repository and reconstruct exact bytes.Walk through a rights marketFollow one rights instrument across the market lifecycle.Run a recovery drillTest logical recovery and fail-closed partial restore.
Full-stack scenarios
Once you understand the core architecture, use scenarios to combine subsystems around realistic applications.
AI agent licenses governed dataDelegation, rights, market action, entitlement and use.Training & derivation rightsTraining, derivation, commercial use and output lineage.Enterprise data exchangeOrganization-to-organization rights exchange with portable market state.Zero-infrastructure recoveryRecover identity, BTDU and economic state after provider/workspace loss.
Case studies · real-world qualification
The contribution campaign is retained because it is valuable evidence of ENTITY operating against external organizations, but it is deliberately not the primary learning path.
Recorded engineering case studiesReproducible terminal records, test results, upstream state and ENTITY lineage for real external fixes.External contribution lineageHow an external issue, exact change-set, review/CI, upstream acceptance and economic state become a persistent evidence chain.Contribution economy scenarioHow accepted engineering could later connect to explicit commercial terms and independently evidenced settlement.Live evidence ledgerReal-world external evidence with technical acceptance and settlement kept separate.