Conformance directory

Codebases governing themselves with the standard.

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.

software/constitution™ (KYE™ Open Source), step by step

Demo data

You learn: What happens at each step. You can: Step through it.

  1. Step 1 of 5

    KYE Protocol™

    Constitution Kit™ — the gate runner

    1 / Kit public/oss/software-constitution/kit/{run.mjs,init.mjs,lib/,schema/,recipes/} . Reads constitution-kit.json , runs every declared gate, emits an L0–L4 verdict. Pluggable recipes (canonical-triple coverage…

  2. Step 2 of 5

    KYE Protocol™

    Signal-ingest harness (§48)

    2 / Wake-up contract public/oss/software-constitution/kit/wake-up-contract/ . Three independent layers: L1 per-PR webhook, L2 post-push verifier ( verify-ci-triggered.mjs ≤ 90s), L3 session-resume ( signal-ingest.sh +…

  3. Step 3 of 5

    KYE Protocol™

    One implementation per concept

    3 / Canonical-triple discipline The §0 red line: every canonical concept appears exactly once . The kit ships a recipe ( recipes/canonical-triple-coverage.mjs ) that hard-fails any PR that introduces a parallel…

  4. Step 4 of 5

    KYE Protocol™

    The codebase declares what governs it

    4 / Self-description gate Every constitution chapter / amendment binds to at least one executing enforcer. An unenforced chapter carries a decay deadline; silent extension is itself a violation. Pattern…

  5. Step 5 of 5

    KYE Protocol™

    Patent-safe by construction

    5 / IP/OSS line Explicit path-rule (§33): what is OSS-track (carries SPDX-License-Identifier: Apache-2.0), what is IP-track (no SPDX, no mechanism content in public/). The kit ships a gate ( ip-oss-line.mjs ) that…

How this widget is built
Demonstrates
KYE Protocol™
Components
  • The steps this page describes
Flow
Each step in order, as the page sets it out. Architecture diagram
Used on

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.

Current adopters.

Production codebases self-attesting at the published level. Verdicts re-issued on each main-branch CI run.

L4 · Platform-bijected

KYE Protocol™

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.

Sector · regulated AI runtime Stack · Cloudflare edge · TS/Py/Go SDKs License · Apache 2.0 mirror

kyeprotocol.com → · github.com/KYE-Protocol →

Your repo

Run SCCT → publish your verdict

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.

Anyone can list — Apache 2.0 standard, Apache 2.0 directory.

List your adoption.

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.