Protocol specifications

​

Core specifications

​

What’s in a spec?

​

QWED-SPEC v1.0

• Request/response format — JSON schemas for API
• Verification engines — Math, Logic, Code, SQL, etc.
• QWED-Logic DSL — Grammar for logical expressions
• Error codes — Standardized error taxonomy
• Versioning — Semantic versioning rules

​

Verification Context v1.0

• Document format — the atomic JSON record of a verification
• Four context layers — interpretation, proof, evidence, decision
• Verdict invariants — VERIFIED requires a sha256 proof_ref; UNVERIFIABLE/BLOCKED require null
• proof_ref — canonical RFC 8785 evidence commitment
• Truth vs. admission — gate execution on admission == "ADMIT" only

​

QWED-Attestation v1.0

• JWT format — ES256 signed tokens
• Claims — Standard and custom JWT claims
• Trust anchors — Issuer verification
• Chain validation — Linked attestations

​

QWED-Agent v1.0

• Registration — Agent identity and permissions
• Action verification — Pre-execution checks
• Budget management — Cost and rate limits
• Trust levels — 0-3 autonomy scale

​

JSON schemas

specs/schemas/
├── request.v1.json
├── response.v1.json
├── attestation.v1.json
└── agent.v1.json

​

Implementing QWED

1. Parse requests per request.v1.json
2. Route to appropriate verification engine
3. Return responses per response.v1.json
4. Optionally generate attestations per QWED-Attestation

​

Conformance levels