Name, Card and Record
The TapeID identity model. The source contains local interfaces and formats; nothing in this model is deployed as a TapeID service.
Name
The design issues an NFT name on BNB Chain under tape (an ENS-style Durin registry, not resolved through ENS in this version) and an owner-controlled identifier. No TapeID registry or resolver is deployed, and no source-project address or gateway is inherited.
Card
An ERC-8004-style document describes the agent, its services and how to reach it. The local editor demonstrates opt-in public fields and content hashing. No TapeID card has been published on chain, and no gas sponsorship is offered.
Record
No deployed record contract, certified record or anchored batch exists.
The intended record binds acceptance criteria, results and evidence so a verifier can recompute its commitments. The shape is chosen for work that already has published acceptance rules — a taped-out circuit scored against a task, for instance; the mapping is described here. Local examples are synthetic. They do not demonstrate real work, independent verification or a TapeOut integration.
Vault and bond
These are not part of the homepage's core Name / Card / Record model. Any future payment vault or bond remains a separate design concern; neither is running or offered.
Ownership and transfer
Owner control and transfer behaviour are design goals, not deployed guarantees. A future implementation must define how a transfer affects cards and records before any reset rule can be claimed.