Public Contract Schemas
The JSON Schemas in json-schema/0.1.0/ are the language-neutral wire
contracts for the v0.1 public draft. They use JSON Schema 2020-12 and reject
unknown fields at trust boundaries.
Contract rules:
- published schema versions are immutable;
- all score-like quantities are integer basis points from 0 through 10,000;
- evidence lifecycle, verification outcome, integrity state, and public result class are separate axes;
- evidence maturity is assessed on a claim-to-capability link, not inferred from the artifact as a whole;
- private artifact content is referenced, never embedded in a general API payload;
- public-draft and calibration profiles cannot contain numeric scores.
- every release in the 0.1 line structurally rejects official calculation and publication modes;
- numeric evaluator proposals are prohibited; the first accepted numeric rubric finding is a bound human-review decision;
- scoring input is synthetic-only and binds tenant, subject, purpose, authorization, consent, permitted use, retention, evidence lineage, review, and contradiction state; scoring consumes full digest-verified review, capability-link, lineage, and actor-bound gate records rather than trusting caller-supplied identifiers;
- the immutable calibration release binds the exact policy and competency-to-rubric registry digests, preventing same-version topology, threshold, gate, or competency inflation;
- every result and profile references a deterministic calculation manifest, authorization context, appeal policy, supersession state, and revocation state;
- replay digests identify RFC 8785 canonicalization plus the versioned schema-declared set normalization used for scoring inputs;
- every research chart manifest binds its metric definition, denominator, missingness, uncertainty, method, accessible table, citations, privacy suppression policy, correction path, artifact digests, and synthetic warning;
- no contract supports a global human score, cost-per-person measure, or named-person leaderboard;
- Evidence Strength, Recency, and Time to Production remain raw research measures until their methodology is calibrated and governed.
The fixtures under examples/valid/ are synthetic and non-inferable. Files
under examples/invalid/ are adversarial mutations that must fail their named
Ajv trust boundary.
Isolated Phase 2 proposal contracts
The schemas in json-schema/0.2.0-proposal/
are nonnormative research proposals. They are not registered with the v0.1
runtime and cannot activate a trust service, score, profile, credential,
restriction, register, or public API.
The proposal package defines scoreless T0–T4 trust-readiness records, a
weightless 12-axis composition, bounded and appealable behavioral-risk events,
research-only recency policies, and disclosure-controlled aggregate-register
candidates and public projections. Its synthetic fixtures and adversarial tests
live under docs/proposals/phase-2/.
Run the isolated proposal gate from the repository root:
node --test docs/proposals/phase-2/tests/proposal-contracts.test.mjs
Outcome architecture proposal contracts
The isolated contracts under
outcome-architecture/0.1.0-proposal/
define three separately governed future outputs—a factual Verified Production
Record, a multidimensional Capability Profile, and a non-issued Governed
Credential Tier candidate—plus a future scalar-score authorization gate and a
Shared Work Challenge Battery design.
These schemas are synthetic-only, are not registered with the v0.1 runtime, and cannot authorize a score, tier, credential, real-person record, comparative human/model result, or employment use. Run their focused gate from the repository root:
node --test docs/proposals/outcome-architecture/tests/outcome-contracts.test.mjs
