Skip to content

Commander native in Core: remaining phases (2, 3 rest, 4-9) #1495

Open

Description

@trissim

Tracks the commander-native plan (commander scripts -> Core tools) phase by phase. Each phase gets a commander order (Core todo) when dispatched; this issue lists what is on main.

Phase State on main (8a9062d)
0 retained-store conversion done (#1412)
1 one owner for orders done (#1409); P554 done (#1612, fa26fc8): judge verdicts live only on Todo.verdicts; copied-root judge ok passed; leftovers: edits.jsonl, rules.jsonl (rules.py:21), growth_seen.json (growth_watch.py:12), fleet-board/fleet-narrative markdown (cli_commands.py:1391) still written by scripts
2 design reconciled with what shipped ordered 18:06 inside P83's slice series (cn-p7), after PlanIdle
3 record plane partly: PlainText, OrderText and StrikeTodo in todos.py (#1414). Missing: Verdict on the order, StrikeLimit + fire, delivery states (merged to main / other branch / not merged), strike voiding (P47 in progress)
4 review queue (comms_order_work, comms_unjudged) done: comms_unjudged merged (PR1654, 41e4ec7): unjudged edits come from native turns keyed by tool call id; edits.jsonl deleted
5 order and fleet stories not started
6 commander page in Toad not started
7 control plane (heartbeat, StandingRule, CommanderLoad, growth, UnitStorage, send guard on Core) in progress: P83 StandingRule + PlanIdle (cn-p7, fire 18:31); next the six rotate.py rules, then UnitStorage. Order progress and stall alarm: P73 (ci-1370); P582 (core-commander-2, due 21:20): DETACHED and REQUEST STALLED become StandingRule members, IdleUnits reads native turns
8 cutover blocked on 4-7 and the parity gate
9 skill uses only Core tools blocked on 8

Dependencies: 2 <- 1; 3 <- 0; 4 <- 3; 5 <- 4; 6 <- 5 (alarms fill with 7); 7 <- 3; 8 <- 4,5,6,7 + parity gate; 9 <- 8.

Why it stalled: after phases 0, 1 and part of 3 merged on 2026-10-18 the commander put every unit on decoder cleanup orders and never dispatched phase 2 or 4-9; the plan lived outside Core, so no open item showed the gap.

🤖 Generated with Claude Code

Activity

  1. trissim commented on Oct 18, 2026

    @trissim
    ContributorAuthor

    Root cause of the stall and its fix is P48 (owner requests become commander-thread goals; every order names one; rotation alarms on a request with no open order). Until P48 lands, this issue tracks the phases.

  2. added 6 commits that reference this issue on Oct 18, 2026
  3. trissim commented on Oct 19, 2026

    @trissim
    ContributorAuthor

    Owners as of 2026-10-19 13:45 local (every unit is a gpt-6.1-sol Pi thread on ts-gaming, own checkout ~/wt/--P1):

    Phase Unit Holds
    2 design reconciled pi-cn-phase2 design doc reconciled with main by file:line; gaps become plan rows
    3 record plane pi-cn-phase3 Verdict, StrikeLimit + fire, delivery states, strike voiding on the order record
    5 stories pi-cn-phase5 order and fleet stories derived from records; script-written board/narrative markdown deleted
    6 commander page pi-cn-phase6 first slice: ui_model commander model, board pane, expandable unit cards, alarms pane; runs now, not after 5
    7 control plane pi-cn-phase7 first: rotation starts and orders a Pi unit for ready unowned work (PlanIdle, standing_rules.py:204)
    8 dependencies pi-plan-claims CutoverPhase waits on 3, 4, 7 and the parity gate; 5 and 6 become views; failing parity rows for 3, 4, 7 listed from the check

    Phase 4 is done (#1654). Live overlaps to merge around: #1912 (P701), #1756 (P202).

    🤖 Generated with Claude Code

  4. trissim commented on Oct 19, 2026

    @trissim
    ContributorAuthor

    Unfinished automatic firing is preserved at branch checkpoint/cn-phase3-fire-1495 (86fcf24), separate from P254 ratchet repair on #1935. Not accepted, merged or installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions