jared/cc-os

Watch

Fork 0

How wayfinder decomposition plugs into os-backlog #246

New issue

Closed

opened 2026-08-03 14:43:12 +00:00 by jared · 2 comments

jared commented

2026-08-03 14:43:12 +00:00

Owner

Map: #239

Blocked by #240

Question

When os-backlog work crosses the map-tier threshold, what are the mechanics: who spawns the map, how children and an assembly issue (pattern: #58) are wired, and what labels/relations os-backlog uses to point at them?

Map: #239 Blocked by #240 ## Question When os-backlog work crosses the map-tier threshold, what are the mechanics: who spawns the map, how children and an assembly issue (pattern: #58) are wired, and what labels/relations os-backlog uses to point at them?

jared added the

wayfinder:grilling

label

2026-08-03 14:43:16 +00:00

jared referenced this issue

2026-08-03 14:43:45 +00:00

Assemble the os-backlog lifecycle design #247

jared self-assigned this

2026-08-04 10:37:01 +00:00

jared commented

2026-08-04 10:41:20 +00:00

Author

Owner

Resolution

Decided (grilling session 2026-08-04):

Map spawn: flag + human charts. When refine hits the map trigger (#240 — too big / too many open decisions), the refine agent stops, leaves a needs-map comment and bounces the capture; the human later invokes /wayfinder charting on it. Refine never auto-creates a map skeleton or runs charting inline — charting is HITL by definition, and an agent-drafted destination anchors wrong.
Relations: adopt wayfinder's conventions as-is. wayfinder:map + wayfinder:<type> labels, Map: #NNN child body line, Blocked by #NNN body convention (Forgejo native dependency API proved unreliable on this tracker). os-backlog documents these in its references and its skills read them; no parallel os-backlog-native vocabulary.
Assembly issue: created at charting, agent-maintained. Charting creates the assembly ticket up front as a wayfinder:task child blocked by every decision child (#58 pattern); any session graduating fog into a new ticket appends it to the assembly's Blocked-by list in the same bookkeeping pass (as #247/#249 on this map).
Readiness labels: wayfinder:<type> supersedes. Map children are exempt from the ready-for-agent/ready-for-human requirement — the type label already encodes routing (research/AFK-task = agent-runnable; grilling/prototype = HITL). os-backlog list/loop tooling treats wayfinder:* issues as map-owned and skips them in readiness sweeps.

## Resolution Decided (grilling session 2026-08-04): 1. **Map spawn: flag + human charts.** When refine hits the map trigger (#240 — too big / too many open decisions), the refine agent stops, leaves a needs-map comment and bounces the capture; the human later invokes `/wayfinder` charting on it. Refine never auto-creates a map skeleton or runs charting inline — charting is HITL by definition, and an agent-drafted destination anchors wrong. 2. **Relations: adopt wayfinder's conventions as-is.** `wayfinder:map` + `wayfinder:<type>` labels, `Map: #NNN` child body line, `Blocked by #NNN` body convention (Forgejo native dependency API proved unreliable on this tracker). os-backlog documents these in its references and its skills read them; no parallel os-backlog-native vocabulary. 3. **Assembly issue: created at charting, agent-maintained.** Charting creates the assembly ticket up front as a `wayfinder:task` child blocked by every decision child (#58 pattern); any session graduating fog into a new ticket appends it to the assembly's Blocked-by list in the same bookkeeping pass (as #247/#249 on this map). 4. **Readiness labels: `wayfinder:<type>` supersedes.** Map children are exempt from the ready-for-agent/ready-for-human requirement — the type label already encodes routing (research/AFK-task = agent-runnable; grilling/prototype = HITL). os-backlog list/loop tooling treats `wayfinder:*` issues as map-owned and skips them in readiness sweeps.

jared closed this issue

2026-08-04 10:41:20 +00:00

jared referenced this issue

2026-08-04 10:41:30 +00:00

Wayfinder map: os-backlog issue lifecycle & templates #239

jared commented

2026-08-04 11:44:23 +00:00

Author

Owner

Amendment (2026-08-04, post-review)

A Codex second-opinion review of spec #250 surfaced a contradiction between this decision's readiness-label exemption and #248's sweep-failure routing. Resolved (ADR-0096 amended, merged in ea9d019): a failed decision sweep applies ready-for-human even to wayfinder:* children — it is the sweep's routing verdict, not a readiness-tier claim; readiness sweeps still skip the issue because the wayfinder label wins.

## Amendment (2026-08-04, post-review) A Codex second-opinion review of spec #250 surfaced a contradiction between this decision's readiness-label exemption and #248's sweep-failure routing. Resolved (ADR-0096 amended, merged in ea9d019): a failed decision sweep applies `ready-for-human` even to `wayfinder:*` children — it is the sweep's routing verdict, not a readiness-tier claim; readiness sweeps still skip the issue because the wayfinder label wins.

jared referenced this issue

2026-08-04 11:44:23 +00:00

Define the weighted-decision block format and threshold sweep #248

No milestone

No project

No assignees

1 participant

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#246

No description provided.

Rows
Columns