jared
/
cc-os
1
0
Fork 0
Code Issues 17 Pull Requests Packages Projects Releases Wiki Activity

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

New Issue
Closed
opened 2026-07-10 17:22:36 +00:00 by jared · 2 comments
jared commented 2026-07-10 17:22:36 +00:00
Owner
Copy Link

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)
**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 commented 2026-07-13 13:44:38 +00:00
Author
Owner
Copy Link

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.
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
Copy Link

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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
research/clutter-inventory
Labels
Clear labels   
P0

Priority 0 — drop everything

  
P1

Priority 1 — next up

  
P2

Priority 2 — normal

  
P3

Priority 3 — someday

  
afk-ready

Autonomous end-to-end; closed after verification

  
hitl

Human-owned; never picked up autonomously

  
next

Human-curated next up — AI never applies or removes

  
ready-for-agent

Triage complete; an agent can pick this up

  
review

Shipped semi work awaiting human sign-off

  
semi

Autonomous through mechanical parts; stops at gates; ships to review

  
waiting

Blocked; blocker named in a comment

  
wayfinder:grilling

   
wayfinder:map

   
wayfinder:research

   
wayfinder:task
No Label
P0
P1
P2
P3
afk-ready
hitl
next
ready-for-agent
review
semi
waiting
wayfinder:grilling
wayfinder:map
wayfinder:research
wayfinder:task
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jared/cc-os#17
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?