# Reference (contributor policy & ledgers)

- [Reference (contributor policy & ledgers)](/development/reference/README.md) - Reference material for maintainers — friction inventories, coverage-signal reconciliation, seam ledgers, standing orders, red-main policy, and terminology exemptions.
- [CI and Architectural Gate Mechanics](/development/reference/ci-gate-mechanics.md) - What trips each spec-kitty CI gate — marker gates, the architectural battery, docs-freshness registration, and accept-to-consolidate close-out — with symptom and repro.
- [Coverage signals — reconciling the three "coverage" numbers](/development/reference/coverage-signals.md) - Why SonarCloud coverage, new_coverage, and the internal diff-coverage CI gate disagree — and how to tell an expected scope difference from a real coverage regression.
- [Events in core](/development/reference/events-in-core.md) - Contributor rules for writing and reading event logs in core today, what not to do, and how to adopt a new spec-kitty-events release without a red nightly.
- [Issue-Matrix Verdict Reference](/development/reference/issue-matrix-verdicts.md) - The five issue-matrix verdict values, which transitions each one gates, the reference-classification model that decides whether a row is required, and the evidence-token rule.
- [Known Current Friction Points](/development/reference/known-friction-points.md) - A time-stamped, fast-drifting list of current repo and tooling friction points a maintainer or agent hits mid-mission; re-verify against the tracker before trusting specifics.
- [Lock-interop spike (#6193)](/development/reference/lock-interop-spike.md) - Pointer: the #6193 lock-interop spike report moved to spec-kitty-events with the services it verifies.
- [Consumers of the optional Lamport clock](/development/reference/optional-lamport-clock-consumers.md) - Every core site that reads or writes Event.lamport_clock or the spec-kitty-events ordering keys, with a verdict and the test that pins it, following spec-kitty-events 11.0.
- [Quality & Tech-Debt Standing Orders](/development/reference/quality-and-tech-debt-standing-orders.md) - Eight-section standing orders for spec-driven missions: adversarial squads, campsite cleaning, test discipline, architectural gates, sources, git workflow, and mission hygiene.
- [Read-side placement-seam classification ledger](/development/reference/read-side-seam-classification.md) - Per-site verdicts (migrate-fail-loud / stay-lenient / sanction-infra) for every production call site that bypasses PlacementSeam.read_dir(kind).
- [Red Main and Release Readiness](/development/reference/red-main-and-release-readiness.md) - What a red main branch means, why CI status is the authoritative release gate, how P0 bugs carry failing reproduction tests, and how maintainers prioritize recovery.
- [Terminology Guard Exemption Policy](/development/reference/terminology-exemptions.md) - Policy for the six surfaces exempt from spec-kitty terminology guards: ADRs, migrations, archived pages, archival plans, dated reports and the Unreleased-only CHANGELOG scan.
- [Version taxonomy](/development/reference/version-taxonomy.md) - The five version-relevance tags every docs page carries, what each means for the active release line, and how the leakage check enforces them.
