Adopters publish their SCCT verdict (L0–L4) and link to the public evidence. The standard's credibility is the codebases that ship it. List here when you conform.
No constitution found.
Canonical artefacts exist; schemas validate.
Every rule has a passing CI gate.
Project emits its own audit chain.
Every named surface is in a generated meta-index.
Production codebases self-attesting at the published level. Verdicts re-issued on each main-branch CI run.
Runtime authority + evidence protocol. Every named surface bijected in a generated meta-index; every privileged action emits its canonical audit chain. Six rule classes pass on every PR; SCCT verdict re-issued on every main-branch push.
If your codebase conforms at any level, list it here. Open a PR with: (a) public repo URL, (b) SCCT verdict JSON, (c) one-line description, (d) a stack tag.
Three commands and a pull request.
# 1. Run SCCT on your repo and capture the verdict npx scct . > scct-verdict.json # 2. Fork softwareconstitution/site and add an entry to adopters.html gh repo fork Software-Constitution/site --clone # 3. Open a PR with the verdict JSON attached gh pr create --title "adopt: <your-repo> at L<n>"
PRs are reviewed for verdict integrity (the JSON must validate against the SCCT schema and the repo must be reachable). No editorial gating — every conforming repo is listed.