Repository navigation
8000
Phase 2: enforce versioned source and claim schemas #9
Description
Product outcome
Replace untyped source and claim payload acceptance with committed, versioned contracts that preserve source text separately from normalized truth-valued claims.
Acceptance criteria
- Rust types exhaustively model the
SourceandClaimfields required by sections 8.1, 8.3, and 12 ofSPEC.md. - Claim kinds are an exhaustive enum with no proof-status field.
- Source licensing, redistribution, redaction, locator, citation, and provenance fields are explicit.
- Claim source reference, normalized statement, assumptions, variables/domains, concept links, citations, and ambiguity notes are explicit.
- Committed JSON Schemas exist under
schemas/source/andschemas/claim/with explicit schema versions and closed objects. - Schema consistency tests compare committed schemas to the Rust-owned schema contract.
- Canonical record creation and versioning validate supported source and claim schema versions before persistence.
- Unknown fields, malformed hashes, empty required text, excessive collections, and unsupported schema versions fail with structured errors.
- Rejected payloads leave no canonical record or idempotency receipt.
- Valid typed payloads survive restart and exact lookup unchanged.
Trust checks
- Original source content is never silently normalized into a claim.
- A source and claim remain distinct stable objects and versions.
- No direct proved, disproved, certified, or novelty status exists in either payload.
- Validation is enforced in code, not by prompt instruction.
Out of scope
Formalization schemas, fidelity review, source acquisition, URL fetching, literature authority, CLI/MCP exposure, and claim truth derivation are separate deliverables.
Activity
Mnehmos commentedon Jul 19, 2026
Local acceptance evidence is complete in commit
5e8fcaaonfeat/spec-driven-rust-rebuild.Implemented:
schemas/source/source-1.schema.jsonandschemas/claim/claim-1.schema.json;provedstatus, malformed hashes, blank required text, excessive collections, and unsupported versions;Local validation:
cargo fmt --check: passedThis does not implement fidelity review, truth derivation, source acquisition, or formalization. The issue remains open pending authenticated branch push and remote CI.
Mnehmos commentedon Jul 19, 2026
Remote preservation update: local commit
5e8fcaawas replayed as remote commitd618c1aon draft PR #11. CI is now running against the durable GitHub branch.