Mark license
Legal authorization for the exact product scope; copying remains technically possible.
Badge and verification
The badge is a doorway to proof—not the proof itself.
The intended design is a live registry, dynamic web badge, status-neutral static mark, signed credential, controlled license, and correction system.
Use this static form in apps, stores, print, and screenshots.
Public registry
Current status, scope, issue/expiry, limitations, history, and complaint route.
Live and static assets
Live web SVG may show status; static art always says Check Live Status.
Signed credential
ES256 signature proves issuer and integrity at issuance; live status still controls.
What was rejected
No NFT or app secret theater.
Transferable tokens add friction and make revocation/privacy harder. A secret in a mobile executable can be extracted. CORS and Referer do not prove ownership.
What happens on revocation
The registry and live badge change immediately.
Static screenshots cannot update, so the mark license, credential ID, official link, monitoring, correction notices, and platform/legal channels complete the system.