Trust model: design is not deployment

TapeID is not deployed. No names, cards, records, gateways, registry contracts or transactions from the source project are presented as TapeID achievements. This page describes the intended boundaries without turning them into live guarantees.

1. True today

• The application source contains local Name, Card and Record interfaces and verification helpers.
• The fallback configuration has no registry, registrar, payment token or public gateway address.
• The anchor ledger is empty and the public numbers start at zero.
• TapeID uses TapeOut for one thing only: rule certificates, a spending rule taped out as a circuit on BNB Chain. TapeOut is a separate protocol; TapeID is not part of it and is not endorsed by it.

2. Claims TapeID does not make

• “The platform cannot change your name.” No TapeID registry is deployed, so no live admin or ownership guarantee exists to assess.
• “Independently verified.” No independent production verifier is deployed.
• “Records cannot be changed.” No TapeID record contract or anchor exists.
• “Audited.” No external audit is claimed.
• “Available now.” There is no public launch, sale, free-name offer or gas-sponsorship promise.

3. What local verification means

The verification page can check the structure and cryptographic consistency of supplied example data. A successful local check does not prove deployment, independent acceptance, real work or an on-chain anchor.

4. Before any production claim

A real deployment would need its own chain configuration, contract addresses, gateway, transaction references and security review published separately. Until then, those values remain absent rather than inherited.

There is no production SLA or operational service. The local fallback contact is support@example.invalid.