Repository navigation
docs(rfc): Ultra Mode task hierarchy redesign (on hold) - #34241
chenmingwei23 wants to merge 1 commit into
Conversation
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Docs only: this adds a draft RFC and plan that are on hold, plus their index rows. No code, contract or user-facing surface changes. [DESIGN-REVIEWED] 031039d Description read[DESCRIPTION-READ] 7039b6aba58f1534b8a9edd4e680c383c02f576a95ab71907f09c7bc066714ba That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Opus 5.5 Review — ✅ no blocking findingsReviewed Review detailsNo findings. Notes:
[OPUS-REVIEWED] 031039d Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
a79f636 to
4f2588d
Compare
|
This adds a new concept, so it needs a design sign-off from a maintainer before it can merge. A maintainer will post the decision here. To propose a design, follow the request-for-change process in CONTRIBUTING.md (docs/request-for-change/). Review result: no blocking findings on this head. The change is docs only: a draft RFC, its task plan, and one index row in each of the two READMEs. PR Readiness is green on this commit. The code claims we checked hold at the stated audit commit Optional:
|
4f2588d to
a1220e8
Compare
Code change approver recommendation: A person should decideWhy: the decider estimates a 12% chance that this change introduces a defect, within the 12% limit for approving on its own, but it changes 576 lines, more than the 400 it may approve on its own. Docs-only PR that adds a draft RFC (on hold), its 7-PR plan and one index row in each of the two RFC indexes. It changes no code, config or tests, and all CI checks passed. §11 says the design adds no new trust boundary, which holds: every new action is a conductor-side work_ledger_record write behind the existing caller checks. Lifetime item creates are already unbounded on main. The remaining problems are stale or inconsistent wording, with no behaviour impact. An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit |
|
I read the whole diff at a1220e8. It's docs only: the RFC, its task plan, and an index row in each README. The RFC marks itself on hold. The front matter says The documents are consistent with that state. The plan's own row says 0 of 7 tasks done at When the project resumes, please move the status line and both README rows off "on hold" in the same push that asks for review. The sign-off can then be judged against the current design. |
a1220e8 to
031039d
Compare
|
Rebased onto main to clear a conflict, no content change. |
|
Closing. The project is on hold, and section 6 of this RFC is now out of date: it keeps a separate team-lead skill, while decision #37696 (merged 2026-11-15) moves conductor mode back to kirocrew-conductor and folds the useful team-lead rules into goal-conductor. The branch stays; tracking issue #34239 keeps the design link. If the task hierarchy work resumes, reopen and rewrite section 6 against #37696 first. |
Problem / Motivation
Goal: Record the Ultra Mode task hierarchy redesign and its task plan in the repository, so the work can resume later from a written design.
Ultra Mode's work ledger is flat: one task maps to one session. A level of tasks exists only as another conductor ledger, a worker session holds one open item, nesting depth is capped at 2, and there is no way to say that one task waits on another or that several sessions share a task. Larger goals cannot be decomposed without folding hand-offs into a single item.
Why it matters
Without a written design, the three gaps (task tree, dependency edges, many-to-many assignment) have no agreed shape and the owner's rulings on the open questions are not recorded. The owner paused this project on 2026-11-09, so the document is the only place the design and the 7-PR plan (R0, F1-F4, U1, S1) will live until work resumes. Tracking issue: #34239.
Not a goal
draftand the project stays on hold.What changed (motivation -> approach -> change)
The RFC replaces the flat ledger with three structures: a task tree of any depth, dependency edges between tasks (cycle-checked, ready-set dispatch, critical path first), and many-to-many assignment of tasks to sessions. The principle is to write facts and derive everything: only facts go into the crew log, and the tree, roll-ups, ready set and caps are derived by the
workfold at read time, so old ledgers read unchanged. Open questions Q1-Q6 are replaced by a rulings table.docs/request-for-change/rfc-ultra-mode-task-hierarchy.md(statusdraft, on hold).docs/request-for-change/plans/2026-11-08-ultra-mode-task-hierarchy.mdand its row indocs/request-for-change/plans/README.md.docs/request-for-change/README.md.Backwards compatibility
Compatible: documentation only, nothing that works today stops working.
Tests
Docs only.
test/test_pr_quality_gates.py -k "rfc or request or index or front": 4 passed locally after the rebase.Proof: not provable -- docs or config only
Manual verification
N/A -- docs only; the index row and links were checked by reading the rendered diff.
Related Issues
Tracking issue: #34239
Checklist