Governance 2.2.0

Find the governance contract you need

This retrieval surface keeps the accepted JSON Schema bytes, plain-language orientation, and their exact source coordinate together.

Accepted source c8d7150b8c4e6277bc504a7c69289cb5b949b0ee

A steady path from question to check

1

Choose the record

Start with the catalog description that matches the decision, receipt, or evidence relationship you need to carry.

2

Use the accepted bytes

Download the schema from this release path and keep its stable identifier with your validation record.

3

Keep authority visible

Schema validation establishes structural agreement. Named governance roles still own meaning, suitability, acceptance, and authorization.

Two useful jobs

Guidance explains; schemas validate

Human-readable governance explains purpose, roles, evidence, and review. The byte-identical JSON Schema files define machine-checkable structure for this release. Each can do its own job without asking one signal to establish the other.

Source you can inspect

The release contains 29 schemas. The source catalog, accepted source tree, and deterministic manifest preserve the route back to the exact revision.

The repository collaboration guide shows how to follow one schema across these source, release, and retrieval roles.