os-backlog slice 8: operations board + measurement wiring + routing ADR

jared commented

2026-07-10 17:22:36 +00:00

Owner

Type: Semi · Triage: ready

Parent

PRD: issue #9 (os-backlog plugin). State pointer: Planka card https://planka.hyperthrive.io/cards/1816234194716592051

What to build

The measurement and record-keeping close-out. Three parts:

Operations board: a general board in the Dev project for cross-project recurring/AI-checked cadence work (e.g. the biweekly orchestration IRL audit card), created via board-ensure. Recurring cards accumulate progress history as comments — a human-readable trail alongside machine ledgers. (Tick-fed population is blocked on planka gem issue 13 — out of scope; manual cards in scope.)
Rubric category: the biweekly IRL audit rubric in os-orchestration gains a capture/route/promote category so session compliance with the tracker convention is measured from production evidence. No dedicated wording-eval grid unless audits show persistent misses.
Follow-up ADR: record the tracker-routing convention (Planka = state / git issues = specs, tracker key, promotion rule) in the cc-os ADR log, since it amends the pilot plan's Forgejo rule.

Semi: board creation and rubric edit are mechanical; the ADR text and rubric wording are decision gates for human review.

Acceptance criteria

Operations board exists with uniform lists/labels; the IRL-audit recurring card lives there with at least one progress comment
os-orchestration audit rubric contains the capture/route/promote category (cross-plugin edit consistent with ADR-023 ecosystem framing)
ADR added to docs/memory-system/03-architecture-decisions.md recording the tracker-routing convention, human-approved
implementation-status.md and build-plan records updated per repo convention

Blocked by

#16 (injection note + /to-issues routing)

**Type:** Semi · **Triage:** ready ## Parent PRD: issue #9 (os-backlog plugin). State pointer: Planka card https://planka.hyperthrive.io/cards/1816234194716592051 ## What to build The measurement and record-keeping close-out. Three parts: 1. **Operations board**: a general board in the Dev project for cross-project recurring/AI-checked cadence work (e.g. the biweekly orchestration IRL audit card), created via `board-ensure`. Recurring cards accumulate progress history as comments — a human-readable trail alongside machine ledgers. (Tick-fed population is blocked on planka gem issue 13 — out of scope; manual cards in scope.) 2. **Rubric category**: the biweekly IRL audit rubric in os-orchestration gains a capture/route/promote category so session compliance with the tracker convention is measured from production evidence. No dedicated wording-eval grid unless audits show persistent misses. 3. **Follow-up ADR**: record the tracker-routing convention (Planka = state / git issues = specs, `tracker` key, promotion rule) in the cc-os ADR log, since it amends the pilot plan's Forgejo rule. Semi: board creation and rubric edit are mechanical; the ADR text and rubric wording are decision gates for human review. ## Acceptance criteria - [ ] Operations board exists with uniform lists/labels; the IRL-audit recurring card lives there with at least one progress comment - [ ] os-orchestration audit rubric contains the capture/route/promote category (cross-plugin edit consistent with ADR-023 ecosystem framing) - [ ] ADR added to `docs/memory-system/03-architecture-decisions.md` recording the tracker-routing convention, human-approved - [ ] implementation-status.md and build-plan records updated per repo convention ## Blocked by - #16 (injection note + /to-issues routing)

jared added the

ready-for-agent

label

2026-07-10 17:22:36 +00:00

jared referenced this issue

2026-07-12 22:25:52 +00:00

PRD: os-backlog plugin — the AI's process-management surface #9

jared referenced this issue

2026-07-13 13:19:10 +00:00

os-backlog slice 7: SessionStart injection note + /to-issues routing #16

jared commented

2026-07-13 13:44:38 +00:00

Author

Owner

Codex review adjustments (2026-07-13), adopted before implementation:

ADR goes to docs/adr/ via os-adr (bin/adr-new + index regen), NOT docs/memory-system/03-architecture-decisions.md (frozen historical monolith since the 2026-07-12 retrofit).
Operations board NAME is a human decision gate before creation (durable key).
The ADR is a minimal canonization of already-implemented practice (Planka=state / git issues=specs, tracker key, promotion rule), cross-referencing route SKILL.md, /to-issues step 5, and the slice-7 session-start note rather than restating them.
Rubric edit targets plugins/os-context/skills/audit-sessions/references/rubric.md (os-orchestration renamed to os-context 2026-07-13, ADR-0031).
Rubric category stays narrow: capture/route/promote compliance only; no wording-eval grid unless production audits show persistent misses.
Records close out per index+leaf convention (implementation-status.md one-liner + os-backlog leaf); the old build-plan file is not revived.
Live Planka evidence (board/card/comment IDs) reported at close-out, since repo inspection can't verify those criteria.

Codex review adjustments (2026-07-13), adopted before implementation: 1. ADR goes to docs/adr/ via os-adr (bin/adr-new + index regen), NOT docs/memory-system/03-architecture-decisions.md (frozen historical monolith since the 2026-07-12 retrofit). 2. Operations board NAME is a human decision gate before creation (durable key). 3. The ADR is a minimal canonization of already-implemented practice (Planka=state / git issues=specs, tracker key, promotion rule), cross-referencing route SKILL.md, /to-issues step 5, and the slice-7 session-start note rather than restating them. 4. Rubric edit targets plugins/os-context/skills/audit-sessions/references/rubric.md (os-orchestration renamed to os-context 2026-07-13, ADR-0031). 5. Rubric category stays narrow: capture/route/promote compliance only; no wording-eval grid unless production audits show persistent misses. 6. Records close out per index+leaf convention (implementation-status.md one-liner + os-backlog leaf); the old build-plan file is not revived. 7. Live Planka evidence (board/card/comment IDs) reported at close-out, since repo inspection can't verify those criteria.

jared commented

2026-07-13 14:00:56 +00:00

Author

Owner

Shipped in 49c8f5e. Live Planka evidence: Operations board 1818308120145822783 (Dev project, uniform lists/labels), recurring IRL-audit card 1818310715438531668 (P2+semi), first progress comment 1818310889929966683. ADR-0033 Accepted (docs/adr/); rubric category 8 tracker-routing added to os-context audit rubric. Bonus fix found live: label color fallback now rescues Planka::BadRequestError (Planka rejects unknown colors as HTTP 400, not 422). Records updated; suite 91/0.

Shipped in 49c8f5e. Live Planka evidence: Operations board 1818308120145822783 (Dev project, uniform lists/labels), recurring IRL-audit card 1818310715438531668 (P2+semi), first progress comment 1818310889929966683. ADR-0033 Accepted (docs/adr/); rubric category 8 tracker-routing added to os-context audit rubric. Bonus fix found live: label color fallback now rescues Planka::BadRequestError (Planka rejects unknown colors as HTTP 400, not 422). Records updated; suite 91/0.

jared closed this issue

2026-07-13 14:00:56 +00:00

jared referenced this issue from a commit

2026-07-13 20:13:46 +00:00

os-backlog slice 8: Operations board + tracker-routing rubric + ADR-0033 (issue #17)

jared referenced this issue

2026-07-31 20:08:40 +00:00

PRD: os-sdlc:implement v2 — fresh agents every round, sharded parallel programmers, deterministic lint pre-pass #195

jared referenced this issue

2026-08-01 16:52:42 +00:00

os-sdlc v2: deterministic smoke/parity gate subcommand #218

jared referenced this issue