Verify an assistant-guide.txt file
A verifier checks a guide against the Human-Verifiable Assistant Guide profile and reports what it found. It confirms form. The human still confirms meaning.
Interactive verifier
The hosted verifier at this URL is in development alongside the v0.1.0 draft. Until it ships, verify guides with any conformant verifier built against the verifier conformance profile and its fixture corpus.
What a verifier checks
- Reachability of the guide at
/.well-known/assistant-guide.txtand the compact verification instruction. - The strict ASCII byte profile, the 8 KiB size cap, and absence of disallowed constructs.
- Required sections, the assistant safety contract, and explicit approval gates.
- Provenance signals: the sidecar manifest and the cross-channel hash, where present.
What a verifier reports
A GuideCheck conformance claim is valid only when backed by verifier output, the guide SHA-256, the achieved level, and the findings.
verifier: human-verifiable-assistant-guide-verifier 0.1.0 guide-url: https://example.com/.well-known/assistant-guide.txt guide-sha256: a1b2c3d4 ... (review the guide before use) achieved-level: 3 findings: - 0 blocking - 1 advisory: last-reviewed older than 90 days note: conformance is not safety
Conformance is not safety
A passing result, at any level, does not mean a guide is safe to follow or that its publisher is trustworthy. It means the file has the form the profile requires. Read the guide in full, apply the security practices a competent operator would already apply, and keep the human in the approval loop.
Build your own verifier
GuideCheck never presents its hosted verifier as the only authoritative one, and never as a root of trust. Anyone may build a conformant verifier; the fixture suite is how independent implementations stay in agreement. See verifier-conformance.md.