Control an external subject
Prove DNS control of an HTTPS domain or bind the exact current default-branch HEAD of a public GitHub repository.
EXTERNALLY BOUNDSERVER OBSERVEDCRYPTOGRAPHICALLY SIGNED
Prove the control path before claiming adoption.
Each record below binds an external domain or exact public repository commit to one real MandateShield production reservation and one fresh, credential-bound permit redemption. MandateShield records no provider submission or provider evidence; activity outside MandateShield is not observed.
Run the exact live control path
Use isolated one-time credentials for a fixed one-cent test envelope. The official runner contains no payment-provider client.
Optionally publish bounded evidence
Private completion publishes nothing. A separate finalization with fresh explicit consent can create a signed record whose digest, expiry, badge, and explicit false claims are machine-verifiable.
PUBLIC ACTIVATION RECORDS
Active, public-key-verifiable URLs
NO ACTIVE EXTERNAL RECORDS YET
The evidence bar is intentionally real.
Sandbox runs, operator tests, registry entries, and configured billing are excluded. A card appears only after the production service observes the exact bound activation chain and the account separately gives fresh explicit publication consent.
Run the first bounded private pilot