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.
- Version taxonomy — the five version-relevance tags every docs page carries, relative to the active release line.
- 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). - Events in core — how to write and read event logs in core today, what not to do, and how to adopt a new
spec-kitty-eventsrelease safely. - Red main and release readiness — what a red
mainmeans and why CI status is the release authority. - Terminology guard exemption policy — surfaces exempted from the terminology drift guards.
- CI and architectural gate mechanics — what trips each CI/arch gate (testing & marker gates, the arch battery, docs-freshness registration, accept-to-consolidate close-out) with symptom and local repro.
- Issue-matrix verdict reference — the five verdict values, which transitions each gates, the reference-classification model, and the evidence-token rule.
Historical / prior cycle
Kept as a record; not current reference.
tests/sync/process-global and thread-seam inventory (#3115) — deprecated; maps thetests/sync/cone, which was deleted with the sync transport.