Specifications.

Veritas Protocol — Architecture Document

The canonical architecture reference. Locks terminology across the working paper, the system diagram, and all seven RFCs (two published, five forthcoming). Defines the five-layer model (sources → validators → chain → federation → consumer), the three on-chain registries, the cascade-event semantics, and the cross-spec consistency rules. Includes appendices on consumer-product surfaces (B2C, including pre-protocol shippable products) and patentable mechanisms.

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.

Cascading Falsification & Source-Authenticated Retraction Protocol

Specifies the cascade-event types (RETRACTED_BY_SOURCE, RETRACTED_BY_ATTESTATION, CORRECTED_BY_SOURCE, SUPERSEDED_BY_REVISION, AUTHORITY_TRANSFERRED), source-authentication requirements with N-of-M chapter-convenor co-signatures for high-impact events, velocity throttling, forensic-reversal SLA (4 hours target), DID-method hardening (did:plc / did:ion recommended for high-authority sources), and the on-chain encoding of the L2 Cascade Event Log. Closes the source-retraction-forgery attack vector flagged CRITICAL · BYPASSABLE in the V2 super-review.

Canonical Consensus-Domain Registry

Resolves the hyphen-lowercase vs CamelCase naming ambiguity that the V2 super-review identified as the single remaining v0.2 CRITICAL finding. Selects hyphen-lowercase (scientific-default) as canonical; publishes the v0.3 initial registered set (22 domains); specifies the migration table from v0.2 CamelCase aliases (cpml:ScientificConsensus/CochraneGRADE → scientific-default-cochrane-grade); defines the registration-governance process (proposal, public-comment, dispute-panel review). Closes V2-W2G G1.1 — the last v0.2 CRITICAL.

IPI-Safe AI-Grounding Interface Contract

Specifies the output-sanitation contract that AI-laboratory grounding adapters MUST honour when consuming Veritas attestations. Defines input typing (plain-text-only for validator-supplied fields), the sanitation pipeline (length-cap → NFKC → homoglyph filtering → bidi+zero-width stripping → URL hardening → markup stripping), the veritas:UntrustedValidatorText envelope wrapping convention, and the canonical-hash robustness amendment to RFC-FACTCHECK-v0.2 § 4.1. Closes the highest-impact omission of v0.2 (V2-W2F § A10) — indirect-prompt-injection attacks against the AI-laboratory grounding pipeline.

Validator Credential Issuance & Revocation

Specifies the W3C Verifiable Credentials 2.0 profile for Veritas validator credentials: issuer eligibility and vetting, credential schema with domain-scoped authorisedDomains[], three credential tiers (individual / institutional / editorial-board), Status List 2021 revocation-check profile, lifecycle (issuance, renewal, key rotation, recovery from compromised key), and on-chain registration. Credentials are post-hoc reputation primitives — permissionless write at the chain layer is preserved.

Aggregator Resync, Reorg, Partition Tolerance

Specifies how federation aggregators handle chain reorgs (finalisation depth: 64 blocks on Base), gossip-network eclipse defence (≥3 independent relays from ≥2 operators, cross-aggregator divergence detection), consumer-facing freshness indicators (_meta.freshness), periodic checkpoint-snapshots (24-hour cadence with N-of-M co-signatures), and disconnect-recovery (48-hour staleness window before full bootstrap). Closes V2-W2F § A7 + ancillary findings on federation-layer attacks.