Record ordering groups G1 and G2 (workflow guidance; client-neutral core and session roles)

[dsnger]

Planning only, nothing implemented. Records three leaves from the advisory comparison with AlexPEClub/ai-coding-starter-kit (21a97bb5) as ordering group G1 in todos.md (Next), with a cross-link in vision §11's dashboard entry.

• G1a, the first candidate: a controlled-change procedure for an existing story or spec, in sparring and intake. It feeds 2c part 3 (spec-delta) and does not compete with it. Ready for intake; not activated.
• G1b: a per-criterion evidence view (AC-ID → evidence → result → revision). It is attached to P5 light and vision leaf 4e, which keep ownership, order and safeguards.
• G1c: the status read's output shape. It is attached to P1, whose staging and trigger are unchanged.

Daniel asked that this serve the Dark Factory's monitoring: all three leaves are inputs to the computed live view (vision §4). None of them adds a status store, a QA gate, a routine approval step or an agent fleet, and no gate obligation changes.

Open for Daniel: whether the profiled 2c stories already meet P5 light's trigger.

Docs-only (docs/**.md and todos.md), so Gate B is N/A under CLAUDE.md §5.

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 20 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 3566c002-1ae9-4b92-81cc-8782bb49cc92

📥 Commits

Reviewing files that changed from the base of the PR and between 7cbbce4 and 915cc86.

📒 Files selected for processing (2)

• docs/superpowers/specs/2026-08-30-dark-factory-vision.md
• todos.md

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

[Low risk] Documents workflow planning and ordering groups.

The documentation-only PR appears safe to merge.

Summary

The PR records G1’s workflow-guidance leaves and adds G2 as a planning direction for a shared Claude Code/Codex workflow with session-local roles.

• It links both groups to the proposed computed live view without activating a leaf or changing a gate obligation.
• The previously reviewed G1 findings were resolved and do not require new comments.

_{Reviews (3) · Last reviewed commit: "docs(roadmap): G2a — name the hook match..."}

[dsnger]

Added ordering group G2 in todos.md (Next, after G1), with a vision §11 cross-link. It covers one workflow core for Claude Code and Codex, with configurable independent reviewers and session-local roles (coding agent / sparring / reviewer). Four leaves, G2a–G2d; G2a (inventory and contracts) is the first candidate. Nothing is implemented, and no leaf is activated. G2 links to G1 instead of duplicating it. Docs-only, so Gate B is N/A.