Your repo already stands.
Reinforce it.
rungs installs and maintains a repository's agentic development system — backlog, findings, gates, skills — composed from modules extracted from four repos that already paid for the lessons.
Retrofit first: npx @rungs/cli add <module>, then rungs doctor.
The rung check: modules state their threshold before installing above your level.
npx @rungs/cli check 20 pass 0 fail 0 unimplemented · Phase 6 in progress Read in date order they are one operator learning the same lessons four times. What worked became a module; what hurt became a guardrail. No repo has all four stages — that gap is the product.
tracked is the rung two of the four source repos never reached — and both paid the same price.
The entry point, the bridge, path-scoped rules, and the render pipeline
The runner, the registry, the ledger, and the structural gate set
Work items with ids, a lifecycle, and a board
The register for what is noticed before it is decided
Decision records, with an admission rule
Handoff state across sessions
Matrix workflows, and a proliferation check
Behaviour specs with story ids and honest status
Decision procedures — reuse, tiering, decomposition
Skill-authoring discipline, and the gates that hold it
An audit procedure whose output is rows, not documents
Candidate/release lines, and the release procedure
An external design authority, synced two ways
Topic ownership, and rule propagation across surfaces
Many sessions on one integration branch
audit → findings → backlog (268 unactioned audit reports) ·
workflows → skills (an uninvocable 9-step procedure) ·
doc-authority → gates (non-negotiables that decayed in place).