Specs
The documents that define what a QWED verification is, so every engine, SDK, command line tool and client speaks one protocol, and anyone can implement it.
- 4 specifications
- All drafts, open for feedback
- v1.0Draft
Verification Context
The atomic record of one verification: the formal statement plus the interpretation, proof, evidence and decision needed to reproduce and trust it.
- v1.0.0Draft
QWED-SPEC
The standard interface for deterministic verification: request and response formats, engines, errors and status codes.
- v1.0.0Draft
QWED-Attestation
A standard format for cryptographic proof that a verification happened: attestation models, JWT format and verification chains.
- v1.1.1Draft
QWED-Agent
How AI agents verify actions before running them: registration, tool verification, budget limits and trust levels.
Core vocabulary
The words every spec uses the same way. The Verification Context defines them; the other specs build on it.
- 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
Every spec is still a draft, so details can change. Changes follow these rules.
- 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.
- Feedback is welcome in GitHub Discussions.