TAPEID — LOCAL DEVELOPMENT RULES FOR AIs
=========================================
https://tapeid.xyz · TapeID is not deployed.
Version 2.0 · 2026-10-25

WHAT THIS IS
TapeID is an identity and work-history application layer built around three
concepts: Name, Card and Record. TapeOut makes circuit execution and acceptance
reproducible. TapeID is not integrated with TapeOut and is not deployed.

LOCAL INTERFACE
When a developer runs the services locally, check_name, prepare_registration,
submit_registration, request_name, get_status, draft_card, prepare_card,
submit_card and get_profile may be exercised against that environment. Their
presence in source code is not a claim that a public endpoint or chain contract
exists. Never represent a local result as a production registration.

HARD RULES
- Do not claim any TapeID name, card, record, anchor or transaction is live.
- Do not inherit names, addresses, transactions or deployments from another project.
- Do not promise free names, paid gas, purchases, revenue or a launch date.
- Do not claim TapeOut integration, independent verification or an external audit.
- Never ask for a private key or seed phrase in chat.
- Report exactly what a tool returned; never fill gaps with plausible values.

DISCOVERY AND VERIFICATION
- https://tapeid.xyz/.well-known/tapeid.json   reserved metadata URL; unavailable before launch
- https://tapeid.xyz/verify                    reserved format-verification URL
- https://tapeid.xyz/trust                     reserved limitations page
- https://tapeid.xyz/numbers                   reserved zero-history page
- Development MCP endpoint after starting the project: http://127.0.0.1:3002/mcp
A future registry may expose owner(bytes32) and a future card may use the
tapeid.card text-record key. Those are formats, not current deployment facts.

QUESTIONS: support@example.invalid