Schemas
Eight schemas. Tier 0 throughout. The shape of the evidence, not the evidence itself.
Every governed-AI artifact at GovernedAI emits in one of the following shapes. Publishing the shape is the discipline that lets a third-party evaluator know what to verify before requesting access. Publishing the contents is what requires access in the first place.
Schema registry
| Schema | Purpose | Tier | Format | Link |
|---|---|---|---|---|
disclosure_tiers.yaml |
The five-tier policy that governs every public surface | Tier 0 | YAML | view |
source_tiers.yaml |
Disclosure rules for source attribution (production scar, postmortem, design decision) | Tier 0 | YAML | view |
premium_value_gate.yaml |
Premium-value gate criteria for partner-tier surfaces | Tier 0 | YAML | view |
evidence_packet.schema.json |
JSON Schema for an evidence packet emitted to an auditor or regulator | Tier 0 | JSON Schema | view |
counterparty_registry.schema.json |
JSON Schema for tracking counterparties under partner agreement | Tier 0 | JSON Schema | view |
nda_status.schema.json |
JSON Schema for NDA status records | Tier 0 | JSON Schema | view |
institutional_access_request.schema.json |
JSON Schema for the eight-field access request | Tier 0 | JSON Schema | view |
rdl_registry.schema.json |
JSON Schema for the receipts registry entries | Tier 0 | JSON Schema | view |
Why the schemas are publishable
Each schema defines the shape of a piece of governed-AI evidence: what fields it has, what values are valid, what is required. A schema does not disclose any specific evidence; it discloses the contract under which evidence is produced. That contract is what a regulator, an auditor, or a counsel team needs to evaluate before requesting any specific artifact.
Publishing the schemas is the move that lets the partner-tier rooms remain partner-tier. An evaluator does not need to see a specific evidence packet to verify the shape is sound. The shape is published; the contents are scoped to the relationship.
Schema discipline
- Every schema is versioned. Version transitions are recorded in the receipts registry.
- Every schema in this release package is hash-anchored in the patch SHA256SUMS; public receipt anchoring is recorded in RDL-013 after deployment.
- Every schema declares its disclosure tier in its own front matter or root annotation.
- No schema enumerates restricted runtime specifics. The disclosure-tier policy is enforced at every audit.