The Harness
The Rings

Ring 1 · Branch Rules

Brief validation

ci

Ever seen a PR title that told you nothing about what changed?

Re-checks in CI that a pull request’s title and brief sections are properly formed.

View source

Closes linkage

ci

Ever had a PR merge and it wasn't clear which ticket it actually closed?

Re-checks that a pull request names the Issue it closes.

View source

Single-plan-PR guard

ci

Ever had two people plan the same work at the same time, unknowingly?

Re-checks that no two open pull requests are planning the same work at once.

View source

Coherence check

ci

Ever found a task marked "done" that was never actually merged?

Re-checks every task’s recorded state against what actually merged.

View source

Documentation gate

ci

Ever shipped a change and forgot to update the doc explaining it?

Re-checks that a change carrying real code also updates the docs explaining it.

View source

Test-plan state

ci

Ever merged a PR with an unchecked "did you test this" box?

Re-checks that the pull request’s test plan is genuinely ticked.

View source

Typecheck + unit tests

ci

Ever had a change silently break something it wasn't even touching?

Re-runs the type checker and the unit tests for every package this change can reach.

View source

Conventions

ci

Ever opened a PR full of inconsistent formatting and naming?

Re-checks formatting and naming against the repo’s own conventions.

View source

AI review

ci

Ever wished every PR got a second pair of eyes, even at 2am?

Puts an automated reviewer on every pull request, whatever the hour.

View source

Review gate

ci

Ever had a PR merge with nobody actually approving it?

Holds the merge until the required review verdicts actually exist.

View source

Implementation exists

ci

Ever read about a safeguard that turned out not to actually exist?

Re-checks that every gate the doctrine describes has real code behind it.

View source

No orphan hook/CLI

ci

Ever found a script nobody remembers the purpose of?

Re-checks that every hook and CLI in the repo is one the doctrine claims.

View source

No seventh way into GitHub

ci

Ever discovered a backdoor that skipped all your checks?

Re-checks that no route into GitHub exists beyond the ones the doctrine gates.

View source

Cited forge numbers resolve

ci

Ever read a doc that cited a ticket number that didn't exist?

Re-checks that every Issue and PR number cited in the docs resolves to a real one.

View source

Role/contract integrity

ci

Ever had a process doc reference a role that was never actually defined?

Re-checks that every role and contract the doctrine references is really defined.

View source

reader-resolvable-prose

ci

Ever read a doc that assumed you already worked here?

Re-checks that reader-facing doctrine and site pages don't cite a forge number/tranche slug the reader can't resolve, or use coined vocabulary without defining it.

View source