Research-operations contracts
Version 0.1.0 defines strict JSON Schema 2020-12 contracts for five operational receipts:
review-record.schema.json— named reviewer appointment, qualifications, scope, independence, conflicts, access, findings, and signed disposition;publication-integrity-event.schema.json— correction, suspension, retraction, and retirement state with preserved history and public notice;archive-deposition-receipt.schema.json— frozen release, metadata, rights, files, persistent identifiers, and post-deposit verification;fieldwork-authorization-receipt.schema.json— fail-closed authority for specific recruitment and collection activities under one frozen protocol; andpublication-claim-receipt.schema.json— exact public wording, evidence, boundaries, approvals, expiry, and supersession for one claim.
Structural validity is not authority. Semantic invariants separately prevent a pending reviewer from being called independent, a planned archive from being called deposited, a synthetic fixture from authorizing fieldwork or a public claim, and a retraction from deleting history.
Fixtures are conspicuously synthetic. They contain no real reviewer, participant, author, affiliation, archive deposit, DOI, finding, or approval.
Run from the repository root:
node --test fde-benchmark/SCHEMAS/research-ops/tests/research-ops-contracts.test.mjs
Operational guidance lives in ../../docs/research/RESEARCH_OPERATIONS_RUNBOOK.md.
