Map: which ideas ganja pursues next, and where ideas live

Destination

Review every open bead — and three sources outside beads: the cloud fleet the README describes, proposals P2–P5 of the Jev usage research note, and the plan that had been on hold (a judge seam in the engine, an [evaluate] config table and a marker on untrusted tool results) — pick out the ideas about ganja's direction or new features, and make GitHub issues the home of those ideas. Every idea then carries a verdict (do / park / drop), and the ideas marked do are ranked by theme and, inside each theme, by idea. Day-to-day work — bugs, tasks, chores — stays in beads.

Notes

• Tracker: GitHub issues on this repository (recorded here; no drydock record exists). Document language: en (captain's ruling, 2026-09-19); sessions with the captain run in Japanese.
• Captain: @zchee. A navigator session resolves one ticket and stops.
• Destination redrawn once (captain, 2026-09-19, the same day it was signed): the README's cloud fleet and proposals P2–P5 of the Jev usage research note came back into scope. P2–P5 are: a semantic brake for --auto, constraint pinning across compaction, semantic reranking for tool_search, and self-authored tripwires (a watch tool). The note itself is local to the captain's machine.
• Destination redrawn a second time (captain, 2026-09-19, during #47): the plan that had been on hold came into scope as one idea, ext-jev-P1, because four ideas already marked do (ext-jev-P2…P5) depend on the judge seam it builds. The map now carries 41 ideas. A verdict is not an order to start: that plan stays unexecuted until the owner says so.
• Destination amended a third time (captain, 2026-09-19, during #49): the rank covers the ideas inside each theme as well as the themes.
• Granularity (signed with the chart): one verdict ticket per theme, then one cross-theme ranking ticket.
• Scale at charting time: 192 open beads — 77 task, 43 bug, 35 chore, 23 feature, 8 question, 6 docs. The source is .beads/issues.jsonl in this repository.
• Skills every session consults: beads:br for reading beads. A bead id written in a ticket is always followed by a short description.
• Vessels: all empty. Shaping #34–#39, Verdicts #40–#48 and the ranking #49 are closed.
• Census (2026-09-19, after session 17): THE MAP IS COMPLETE — 0 open tickets. All 41 ideas carry a verdict: 26 do (S ×10, M ×11, L ×2, XL ×3), 13 park, 2 drop, and the do ideas are ranked. Next: /oh-my-claudecode:launch with the mission brief the navigator wrote on the captain's machine.
• Sediment: this repository records decisions as D-numbers in its AGENTS.md files, not as ADR files, and CONTEXT.md is the glossary. Deferred sediment: the words idea, theme and verdict as this map uses them are tracker vocabulary, not product vocabulary; whether they earn a CONTEXT.md entry is decided at launch. Also deferred: the ruling that README direction outranks today's terminal-user value when the two conflict (#36) — a candidate for a recorded decision (a D-number) at launch. Also deferred: AGENTS.md's tracker section will have to say that ideas live on GitHub issues and how they are labelled (#37) — land it at launch, once #38 has settled the bead side. Also deferred (#38): the same launch retires the beads idea-label convention at AGENTS.md:315 — that section is rewritten to say ideas are filed through the GitHub issue form and beads carry work only. Also deferred (#46): ganja does not reach Claude's Remote Control — a native remote worker was refused in research and the probe was dropped, both over a vendor's OAuth token and the identity a client presents (D521); whether that earns a D-number is decided at launch.
• Published (2026-09-19): the 41 ideas are on GitHub as #37 decided. The ordered index is #100 (rank means priority, not sequence; re-ranking is one edit of that issue). The nine Theme: parents are #50–#58 in rank order, and the ideas are #59–#99 as their sub-issues, labelled idea plus verdict:* and, for do, size:*. The two drop ideas (#68, #99) are closed as not planned. Six blocking edges: #59 blocks #60, #61, #84 and #88; #63 blocks #64 and #65. New ideas come through the issue form .github/ISSUE_TEMPLATE/idea.yml — .yml because GitHub's documentation says issue forms need that extension. The 33 source beads are closed and linked as #38 decided: external_ref is the issue URL and the close reason is "moved to GitHub #N". Commits on main: dbf5df5 (the form, and AGENTS.md, which retires the beads idea label) and 22ad864 (the tracker); CI run 35440144392 for 22ad864 concluded success. Delivered without /oh-my-claudecode:launch: its yard gate stopped on the drydock findings listed below, and the captain chose delivery by an executor lane with a separate review lane and a separate verification lane; all composed content was reviewed before anything was public. Still open from the deferred sediment: whether idea, theme and verdict earn a CONTEXT.md entry, and the two D-number candidates (the ruling of #36 that README direction wins a conflict; the Remote Control position of #46).
• Deferred drydock --check findings (report-only, 2026-09-19), verbatim: shipyard.surface.missing.CLAUDE-md, shipyard.surface.missing.docs-adr-, shipyard.surface.missing.docs-standards-, shipyard.surface.missing.docs-business-, shipyard.surface.missing.design-system-, shipyard.surface.missing.-omc-skills-, shipyard.surface.missing.-mcp-json, shipyard.surface.missing.scripts-, shipyard.document-language.missing-frontmatter.

Decisions so far

• Inventory: which open beads are ideas, and what themes do they fall into?: 28 bead candidates and 8 ideas from outside beads in 10 proposed themes, 15 borderline, 149 not candidates — a first pass the captain confirms in #35.
• Confirm the candidates and the themes: 40 ideas carried (33 beads, 7 from outside beads) in 9 themes — 41 since #47 added ext-jev-P1; seq excluded as already implemented; nine borderlines stay in beads.
• What makes an idea do, park or drop?: do is a commitment with a rough size (S/M/L/XL), park needs a written reopening condition, drop is settled with a reason; a verdict weighs README direction, today's terminal users and evidence, direction winning a conflict; the captain gives every verdict, at most five do per theme (three until the captain raised it during #41).
• How is an idea represented on GitHub?: themes are parent issues (theme, Theme: …) with ideas as sub-issues; every idea is an issue labelled idea; verdict and size are verdict:* / size:* labels, drop closed as not planned; rank is one ordered index issue; a five-part body; new ideas come through an issue form.
• What happens to a bead once its idea lives on GitHub?: every idea bead is closed whatever its verdict, linked by external_ref plus a one-line close reason; a do idea gets fresh work beads from its plan; the beads idea label is retired; all of it in one launch after #49.
• How do ideas on GitHub relate to the Linear mirror?: they do not — Linear is ignored by the captain's ruling; publication does nothing in Linear.
• Verdicts: Teammates and team orchestration: do 2b6, n0e0, tvh (all M; tvh is an explicit exception to the probe rule) and, since the cap rose to five, 98v (S); park on a free slot 8q4r, e788; nothing dropped.
• Verdicts: Cross-session addressing: do umz (M, an explicit exception to the probe rule), crt (S), y7y (M), uul (S); park hie until the next cross-session landing; nothing dropped; the captain raised the cap to five do per theme here.
• Verdicts: Session lifecycle and compaction: do 6ojt (S) and ext-jev-P3 (L, an explicit exception to the probe rule; depends on a judge seam whose plan is on hold outside this map); park vtf5 until the next template-builtin landing and za2o until the next compaction landing; nothing dropped.
• Verdicts: MCP and deferred tool loading: do mi9 (S), r2e (M, an explicit exception to the probe rule), i72 (S), 6acv (S), ext-jev-P4 (M, the same exception and the same on-hold judge-seam dependency as ext-jev-P3); park 3qi until ext-jev-P4 has landed and v2l until a use report; nothing dropped; five do is the cap.
• Verdicts: Provider wires and options: do e9qp (M, which of its three answers is left to the plan) and v2yw (S, an explicit exception to the probe rule; the live probe is the owner's to run); park gsny until the next provider-options landing and copilot-identity-decision-x3n until the next Copilot-wire landing; nothing dropped.
• Verdicts: Usage, cost and live status display: do g20i (S) and s7u (S); park afay until the next TUI notice-line landing and shlm until the next cursor-wire landing; drop xt0o — polling is enough (the map's first drop).
• Verdicts: Serve, attach and remote access: do kwf (M, presupposes a peer drain and a held-message review surface in ganja serve); park 80g until a use report; drop 7gjf — the token and identity risk.
• Verdicts: evaluate and Jev judgments: the 41st idea ext-jev-P1 (judge seam, [evaluate] table, marker on untrusted results) was added and is do (M); do ext-jev-P2 (M) and ext-jev-P5 (L), both blockedBy ext-jev-P1, as are ext-jev-P3 and ext-jev-P4; all three are explicit exceptions to the probe rule; park l8n4 until ext-jev-P1 is built.
• Verdicts: Cloud fleet: do all three, each XL — ext-readme-1 (control plane), ext-readme-2 (scale) and ext-readme-3 (isolation), the last two blockedBy the first; the map's only XL ideas and its last verdicts.
• Rank the themes marked do: 1 evaluate and Jev · 2 Cloud fleet · 3 Serve · 4 Teammates · 5 Cross-session · 6 MCP and deferred tool loading · 7 Session lifecycle · 8 Provider · 9 Usage; ideas are ordered inside each theme; rank means priority, not sequence; the hold on ext-jev-P1 is lifted for after the launch.

Not yet specified

Out of scope

• Ideas that are not beads, other than the three sources the destination names: the parked Windows support. Ruled out by the captain while naming the destination (2026-09-19); it returns only if the destination is redrawn. (The plan that had been on hold was listed here until the captain brought it into scope during #47.)
• Moving bugs, tasks or chores to GitHub, and retiring beads.
• Anything on the Linear side — the mirror of beads in Linear is ignored (captain, 2026-09-19, #39): no clean-up of mirrored ideas, no re-sync, no GitHub-to-Linear sync.
• Implementing any idea.

Start with .beads/issues.jsonl, the issue decisions linked from #34–#49, and .github/ISSUE_TEMPLATE/idea.yml. Check the published theme and idea issues and ordered index described in the body, then verify that the 33 source beads are linked and closed while Linear is untouched. Done means all 41 ideas have verdicts, do ideas are ranked, and new ideas have the documented GitHub issue-form path.