How a change becomes a verified fact.
All capabilities · Running
Promises about trust are settled in the boring part: what happens between someone deciding to change something and that change being in front of a community. A system is only as governable as its release path.
proposalstandards gatetestsconformance
Release
Only from a green, merged, identified state.
Verify
The artifact is checked by its content, not its version.
Revert
The way back is stated before the rollout, not during it.
a failed gate returns the change to its author
The path
A change is proposed in the open
Work arrives as a reviewable proposal against a stated contract, not as a state someone applied directly to a running system.
Standards are machine-checked
Repository shape, naming, structure, dependency policy, and documentation contracts are enforced by tooling rather than remembered by reviewers. Sensitive paths require explicit approval, and the approval is recorded.
Tests run where the code lives
Verification sits beside the thing it verifies, so a module without checks is visible as a gap rather than hidden in a distant suite.
Compatibility is proven, not asserted
Shared contracts carry conformance suites. An implementation claims compatibility by passing them, which is what lets independent parties build against the ecosystem without private permission.
Release is an event with evidence
Publication is gated on a green, merged, identified state, and the released artifact is verified by its content rather than by a version number appearing somewhere.
Rollback is designed
Every rollout has a stated way back, and reversibility is part of the review rather than a question asked during an incident.
Structured experiments
Uncertainty is handled explicitly instead of being resolved by argument.
One question per experiment
A hypothesis, a method, and a decision the result will inform, written before the run.
Runs are recorded
Inputs, environment, and outcome are kept, so a result can be re-examined when the conclusion it supported is questioned.
Findings graduate or expire
An experiment either becomes a standard, becomes a documented dead end, or is closed. Nothing stays permanently interesting.
Assurance as a community-facing property
Every element of this path exists so that a claim made on this site can be checked by someone who does not trust us. Conformance suites let another implementation prove itself. Release evidence lets a community verify what it is running. Standards gates make the rules visible instead of cultural. Assurance is how architecture stops being a description and becomes a commitment.