Reference (contributor policy & ledgers)

Look-up material a maintainer consults rather than reads front-to-back: standing policy, exemptions, and the classification ledgers that pin how the codebase is kept honest.

• Known current friction points — the fast-drifting list of current repo/tooling gotchas an agent hits mid-mission.
• Coverage signals — reconciling the internal diff-coverage gate with SonarCloud coverage / new_coverage.
• tests/sync/ process-global and thread-seam inventory (#3115) — a narrowed inventory of process-global mutable state and thread-spawning seams in the tests/sync/ cone.
• Quality & tech-debt standing orders — the eight standing practices for spec-driven missions.
• Read-side placement-seam classification ledger — per-site verdicts for every production call site that bypasses PlacementSeam.read_dir(kind).
• Red main and release readiness — what a red main means and why CI status is the release authority.
• Terminology guard exemption policy — surfaces exempted from the terminology drift guards.

Docs site publication source

docs.spec-kitty.ai is intentionally deployed from the promotion-only upstream repository (Priivacy-ai/spec-kitty) by .github/workflows/docs-pages.yml. This EXPERIMENTAL repository is the source of the promoted tree, but it does not claim the custom domain: its Pages workflow skips when Pages is unavailable and its deployment guard accepts only upstream main. Documentation merged here reaches the public site through the controller's promotion loop, as ratified for the public 3.2.6 release and recorded in the programme's fork-reconciliation policy.

See also

• Development home
• How-to runbooks