Skip to content

fleet-mission-control — local board note

No full local board exists for this repo yet. Canonical tracking is Jira project FLT (https://workwingman.atlassian.net) plus Vikunja project 2. This file exists only to record one collision so it isn't repeated.

⚠ Local ticket labels here are NOT Jira keys

The design/image capability-routing work in this repo (docs/DESIGN-capability-routing.md, docs/BRIEF-capability-routing.md, branch wt/WT-0026/FLT-19-capability-routing, and every commit/code comment referencing "FLT-19") used a locally-minted number, assigned when the work session started, never checked against real Jira.

Real Jira FLT-19 is a different, unrelated, already-Done ticket ("FLT-D7 token-roi: CPDT metering + Stop hook"). The actual record for this feature is FLT-102 (minted 2026-07-17 after the work had already landed), related to the umbrella epic FLT-46 ("FLT-13 Mission Control frontend").

This is the same collision class fleet-harness/docs/BOARD.md documents under "Board IDs and Jira keys are NOT the same numbering space" — a second instance, in a repo that had no board file to carry the warning. Before minting a new local ticket number in this repo, check it against real Jira first, or use the Jira key directly instead of inventing one.

Landed commits for FLT-102: API 60bb555/789a899/df554e7/1818d3f/aeb2bed, UI 1272dcf.

Active work in this repo

Ticket State Note
FLT-193 To Do (epic) auto routing guardrails + live seat telemetry. Scope-cut 2026-08-05: the survey-fit/ledger half is cancelled — see the epic for the non-stationary-bandit reasoning.
FLT-194 Needs Human Review — landed 4fcc3bf Codex tier collapse: ("codex", _) => "gpt-5.5" served all three tiers → luna/terra/sol. 693 tests pass; guard proven to fail on the old map. Awaiting Andrew on a real behavior change: mechanical codex work drops from gpt-5.5 to luna, ceiling rises to sol.
FLT-195 To Do seat-policy.yaml — hard constraints only, no fit scores.
FLT-196 To Do RED is a veto in every auto mode + explicit allowRed.
FLT-197 To Do Telemetry Layer 1 — session-log meter feeding the governor live.
FLT-198 To Do Telemetry Layer 2 — live transcript pane + WezTerm pane text.
FLT-199 PARKED ConPTY streaming. Needs a named receipt to revive.
FLT-200 To Do Land the family survey's durable half as docs/process, not router weights.
FLT-207 To Do (bug) Dead MCP server silently degrades the codex seat on greatroom.

Model-map source of truth (FLT-194)

CapabilityRouter.ConcreteModel maps family × tier → the identifier that rides the wire verbatim into each CLI's model flag. The canonical per-tier table is llm-council/council.config.json.

Do not edit that map from a survey, a doc, or memory. Dump the producer and paste the output in the PR:

agy models
codex exec -m <slug> --skip-git-repo-check --sandbox read-only "Reply with exactly: OK"

Two traps confirmed 2026-08-06: - agy accepts both gemini-3.5-flash-high and "Gemini 3.5 Flash (High)", but --effort conflicts with either form — effort is already baked into the -high/-low suffix. - A wrong agy label exits 0 with empty stdout, so an unverified edit fails silently at dispatch rather than loudly at review. That is why the producer dump is a hard gate.