Specifications.
RFC-style working drafts of the protocols that make up the Veritas system. IETF / W3C conventions; intended for upstream submission as input documents.
Two specifications are published in this section. Both are working drafts; neither is yet a finalised IETF RFC or W3C Recommendation. Comments and proposed amendments are welcome via the contact form on the brief.
Available drafts
Consensus Profile Markup Language
Defines a portable, signable, JSON-LD file format that lets a reader, AI agent, or institution declare which validators and consensus domains they trust for which topics, with what weights and conflict-resolution rules.
CPML is consumed by Veritas aggregators to compose per-consumer verdicts from the plural attestation pool. v0.1 specifies operational semantics; one of three formal-grounding paths (Value-based Argumentation Framework, probabilistic-logic, engineering-pragmatic) will be selected before v1.0.
Self-Claims Reporting Protocol — /factcheck.json
Specifies the simplest entry-point to Veritas: any website may publish a /factcheck.json file declaring its factual claims, sources, verification statuses, and per-domain verdicts. v0.2 extends v0.1 (originally at github.com/homototus/veritas) with stable claim-hash identity, per-domain verdicts (per RFC-CPML), third-party-attestation references, and an event-feed mechanism for retraction propagation.
Backwards-compatible with v0.1 readers; forward-compatible discovery via existing <link rel="factcheck"> tag.
Coming in v0.3
Three additional specifications are under preparation:
- RFC-VERITAS-VC — Validator credential issuance (W3C Verifiable Credentials profile).
- RFC-VERITAS-CPML-REGISTRY — Signed CPML discovery registry (defends against trojan-CPML-via-SEO attacks).
- RFC-VERITAS-CASCADE — Source-authenticated retraction cascading (closes the $100K source-forgery attack from the critical review).
Each will be published as a draft at this URL with the same RFC-style format.
Process
Comments, amendments, and proposed forks of these drafts are welcome. The path forward:
- Public comment — through the contact form until the v0.3 working paper is published.
- Editor's draft — incorporates comments; published at this URL.
- Submission to standards bodies — Phase II of the working paper roadmap. W3C Credentials Community Group as input documents; IETF SCITT as use-cases.
- Standards-body review — formal review by the relevant working groups; not under the Working Group's control.
Brief · Working paper · Critical review · Self-declarations · Consensus frames research