Developer cookbook · ENTITY v3.4.3
Copy-paste recipes
These are deliberately small implementation patterns for developers who already understand the architecture and want to exercise the current reference source. They are not a substitute for deployment-specific security, policy, persistence or qualification work.
Repository-layout note: several current ENTITY source folders begin with numeric prefixes, so they are not conventional Python package names. The cookbook uses
importlib.util to load exact source files from a checked-out repository rather than inventing package imports that do not exist.Recipes
0 · Source loaderA reusable helper for loading the current canonical source files by path.1 · Identity & signingCreate an
ent2- identity, verify its manifest, sign a payload and rotate the operational key.2 · Object, authority & rightsRegister a dataset, delegate LICENSE authority, grant TRAIN rights and prove unauthorized actions fail.3 · Vault & purpose accessEncrypt bytes at rest and authorize a bounded purpose/action use with an evidence commitment.4 · Attestation & trustCreate signed evidence claims and evaluate a threshold trust policy.5 · BTDU CLIInitialize, ingest a pinned repository, inspect context and reconstruct exact bytes.6 · Rights/global passportsIssue and verify immutable portable rights state without turning custody or profiles into authority.7 · Offline & partitionsRegister an EDGE node, sign an offline envelope and test causal conflict handling.8 · Market recoveryExport, verify and restore complete logical exchange/economic state into a clean destination.9 · Standards mappingTranslate ODRL and capture VC/DID evidence without claiming semantic equivalence or authority.Recipe discipline
- Run experiments against disposable state directories.
- Use exact released/current source appropriate to the claim you are testing.
- Keep negative tests: unauthorized actions should fail.
- Do not convert conceptual Exchange adoption routes into claims of a hosted service unless your deployment actually implements one.
- Do not paste production private keys, credentials or confidential payloads into examples.