System design · not vibes
Building Web3 is a registry and lifecycle requirement.
NFTs, tokens, AATEMs, and MTN wrappers only count as Web3 infrastructure when they pass four encoded criteria, survive gap_checker scans, and clear simulation gates. Everything else is art_only or legacy_mode.
Scanning gaps…
Four criteria (all required for web3_native)
On-chainReal ledger state — XRPL, Polygon, Apostle 7332, Solana — verifiable, not DB-only metadata.
Canonical registryRow with owner, purpose, chain, contract — wired to Platform Hub and deed registry.
Utility circuitsCallable rights — x402, agents, loans, energy, MTN flows, resort booking, redemption paths.
Event emissionTransfers, redemptions, burns — listened to by Nerve agents and repair workflows.
Enforcement stack
| Layer | Role |
|---|---|
canonical_master_registry | Source of truth — no row, no Web3 existence |
gap_checker | Nightly scan for missing on-chain bindings → repair_board |
asset-class-templates | NFT, AATEM, MTN wrapper, token — required lifecycle + utility schema |
| Agent gates | Mint/claim/delegate blocked on WEB3_COMPLIANCE_FAIL |
| Donkai Scenarios | Reference simulation required per asset class before promotion |
Asset class templates
Loading…
AATEM gate
AATEM = Asset-Anchored Tokenized Exposure Model — published by UnyKorn. Umbrella meta-standard for any asset-backed token. Asset-backed classes require aatem_id in the registry; mint/list/portfolio promotion blocked without it.
Example: Genesis simulation twin
Platform-class deed — not AATEM asset-backed. Canonical registry + DOI IPFS anchor LIVE; Apostle deed mint STUB.
twin live
web3_partial
simulation_engine
Live gap sample
Assets failing criteria — queued to repair_board for deploy, bridge, wrap, or re-index.
Loading…