Phase 2 proposal schemas
Status: Proposed / Not authorized
Runtime registration: None
Data classification for fixtures: Synthetic only
These strict JSON Schema 2020-12 documents are design contracts for the Phase 2 proposal. They do not amend the immutable v0.1 contracts and are not registered with the v0.1 runtime. Schema validation is necessary but not sufficient: cross-field chronology, state reduction, digest lineage, active privacy floors, protected count arithmetic, and candidate-to-public consistency must also pass the deterministic proposal invariant gate.
trust-readiness-record.schema.jsonkeeps trust progression, readiness, and result lifecycle separate; requires a complete genesis history, policy and scope bindings, review facts, and a reducer declaration; prohibits referral-only T2; and structurally permits no evidence-maturity or numeric-result field. Display copy follows the canonical T0–T4 mapping.aggregate-register-candidate.schema.jsonmodels protected pre-publication threshold evaluation, protected numerator/complement counts, organization plausibility, active privacy-policy bindings, and candidate digests.aggregate-register-public-release.schema.jsonexposes opaque identifiers, controlled copy IDs, broad count and share bands, bound safe participation measures, suppression, and privacy attestations. It permits no exact share, public denominator, display-name, or free-form publication text.behavioral-risk-event.schema.jsonrequires reason-coded, bounded, expiring, human-reviewable, appealable restrictions; mandatory referral disposition; controlled notice templates; and prohibits geographic, prestige, capability, employment, and automatic voucher-penalty authority.recency-policy.schema.jsonlimits decay research to evidence freshness and re-verification and requires policy expiry, bounded withholding, review, appeal, alternate evidence, and accommodation controls.axis-composition.schema.jsonfixes a weightless, 12-axis profile vector.common.schema.jsoncarries proposal-only shared types.
Validation is documented in the proposal test README.
All fixtures remain synthetic and non-inferable. The proposal schemas use opaque hexadecimal synthetic identifiers and controlled template or definition IDs so a valid public payload cannot smuggle named people, exact counts, country aptitude, rankings, scores, or operational claims through free text.
