NO ACCOUNTEXTERNALLY BOUNDSELF-REPORT ONLY

Turn a conformance run into public, signed evidence.

Bind the complete output from your own MandateShield offline runner to an HTTPS domain or one exact public GitHub commit. Publish a stable proof URL and badge that machines can verify independently.

01 · RUN

Generate the report externally

Run the published offline vectors in your own implementation and retain its complete observed-output JSON.

02 · BIND

Prove control of the subject

Publish one exact DNS TXT value or a fixed proof file in one exact public repository commit.

03 · VERIFY

Get a portable signed record

The public JSON, badge and compact signature preserve both the verified binding and the limits of the claim.

1 Bind subject2 Publish challenge3 Verify proof
STEP 01

Create an external binding challenge

Submit outputs from your own runner. MandateShield checks the report shape and expected offline outcomes, but does not run your implementation.

What will bind this report?

Public on finalization. Do not include credentials, private keys, personal data, or confidential test inputs.

Open canonical vectors ↗
PUBLIC PROOF RECORDS

Externally bound reports, visible as they actually exist.

0 PUBLISHED RECORDS

No externally bound proofs yet.

The network starts empty. A record appears only after its DNS or repository binding is verified and its self-report is signed.