Specs
The documents that define what a QWED verification is, so that every engine, SDK, CLI and client speaks one protocol and anyone can implement it.
The atomic record of one verification: the formal statement plus the interpretation, proof, evidence and decision needed to reproduce and trust it.
The standard interface for deterministic verification: request and response formats, engines, errors and status codes.
A standard format for cryptographic proof that a verification happened: attestation models, JWT format and verification chains.
How AI agents verify actions before running them: registration, tool verification, budget limits and trust levels.
Core vocabulary
| Verified object | The formal statement being evaluated. |
| Verification context | Interpretation, proof, evidence and decision. |
| Verdict | VERIFIED, UNVERIFIABLE or BLOCKED. |
| Admission | ADMIT or DENY. A true statement is not automatically safe to act on. |
| proof_ref | A SHA-256 commitment to the evidence. It makes a result reproducible; it is not the proof itself. |
| Formalization | The mapping from natural language to the formal statement. Exposed, but never claimed as verified. |
Versioning
- Breaking changes bump the major version; additive changes bump the minor version.
- A released version never changes. Each new version lives in its own directory.
- Every spec is still a draft. Feedback is welcome in GitHub Discussions.