Validate your reasoning.json

Checks a file against ARP v1.3 (“Reader Profile”): required fields, provenance, the wording profile (third-person statements, no instructions to AI systems), the Ed25519 signature and the reasoning.md hash. A valid signature shows who published the file and that it is unchanged. It shows the origin, not the accuracy of the statements.

Spec: ARP v1.3 Schema: v1.3 (v1.2 files are read as v1.2) The file stays in your browser; for the signature check the page asks dns.google for the public key (only the DNS name is sent)
reasoning.json 0 characters

Enter a domain to fetch its /.well-known/reasoning.json:

The target server must allow CORS requests (Access-Control-Allow-Origin: *, SPEC §2.3). For fetched files the signature is checked against the domain of the URL.

Signature check options
Used for the DNS lookup of pasted files, like arp_cli verify --domain: a bare domain name (e.g. example.com) that matches the domain field.
With a key here, no DNS request is made (like arp_cli verify --pubkey).
Compared with the SHA-256 in representations before deployment.
--

Validating…

Circle: completeness of recommended fields (not a quality or truth rating)

Upgrade to v1.3

    Schema & Version
    Provenance (who published the file)
    Wording profile (ARP-W)
    arp_cli lint result (all rules)
    Identity
    Corrections
    Entity claims (self-described context)
    Length limits
    Signature block (_arp_signature)
    Readable representation (reasoning.md)
    Diagnostics
    Sources & audit metadata