Loop 2 followup: define fan out Snippet expansion once autonomous planning lands in Luca #4

Closed
opened 2026-05-23 20:55:37 +00:00 by coilysiren · 0 comments
Owner

Originally filed by @coilysiren on 2026-05-20T12:24:54Z - https://github.com/coilysiren/voice-flow-learning-loop/issues/13

🤖 Filed by Claude Code on Kai's behalf.

Problem

Loop 2 layer 1 snippet-mining (#5) surfaced fan out as a high-leverage two-syllable trigger Kai wants in Wispr Flow. Acoustically distinct, hard consonants, no English collision. The intent is "kick off the lights-out factory" - one short dictation that spawns N parallel Claude Code sessions over the highest-leverage backlog tickets, with no per-ticket enumeration cost.

The expansion is not pinnable yet. Autonomous engineering planning is mid-migration out of repo-recall and into luca. The current recall_dispatch_* MCP family in repo-recall is the right behavior shape but the wrong substrate going forward. If fan out expanded to lets do autonomous engineering dispatch today, it would fire recall_dispatch_begin against a substrate Kai is actively decommissioning.

Shape of the eventual expansion

The compact concept is "you enumerate the tickets, not me." The dictation is one short trigger, no refs. The downstream pipeline:

  1. Pull the org backlog.
  2. Score each ticket (AFK-ability, prior closed similars, autonomy confidence).
  3. Filter to picks above the dispatch threshold.
  4. Spawn a coily dispatch interactive session (or the Luca equivalent) per pick.

Whatever Luca exposes for steps 1-3 is what fan out should call. The expansion's exact wording lands when that surface exists.

Done when

  • Luca exposes a backlog-scoring + dispatch entry point that supersedes recall_dispatch_begin.
  • The fan out expansion is pinned to a phrase or command that fires that entry point.
  • The Snippet is entered into Wispr Flow and used in real dictation.

Depends on: the repo-recall -> Luca migration of autonomous engineering planning.
Related: #5 (the mining run that surfaced this candidate).

_Originally filed by @coilysiren on 2026-05-20T12:24:54Z - [https://github.com/coilysiren/voice-flow-learning-loop/issues/13](https://github.com/coilysiren/voice-flow-learning-loop/issues/13)_ > 🤖 Filed by Claude Code on Kai's behalf. **Problem** Loop 2 layer 1 snippet-mining (#5) surfaced `fan out` as a high-leverage two-syllable trigger Kai wants in Wispr Flow. Acoustically distinct, hard consonants, no English collision. The intent is "kick off the lights-out factory" - one short dictation that spawns N parallel Claude Code sessions over the highest-leverage backlog tickets, with no per-ticket enumeration cost. The expansion is not pinnable yet. Autonomous engineering planning is mid-migration out of repo-recall and into [luca](https://github.com/coilysiren/luca). The current recall_dispatch_* MCP family in repo-recall is the right behavior shape but the wrong substrate going forward. If `fan out` expanded to `lets do autonomous engineering dispatch` today, it would fire recall_dispatch_begin against a substrate Kai is actively decommissioning. **Shape of the eventual expansion** The compact concept is "you enumerate the tickets, not me." The dictation is one short trigger, no refs. The downstream pipeline: 1. Pull the org backlog. 2. Score each ticket (AFK-ability, prior closed similars, autonomy confidence). 3. Filter to picks above the dispatch threshold. 4. Spawn a `coily dispatch interactive` session (or the Luca equivalent) per pick. Whatever Luca exposes for steps 1-3 is what `fan out` should call. The expansion's exact wording lands when that surface exists. **Done when** - Luca exposes a backlog-scoring + dispatch entry point that supersedes recall_dispatch_begin. - The `fan out` expansion is pinned to a phrase or command that fires that entry point. - The Snippet is entered into Wispr Flow and used in real dictation. **Depends on:** the repo-recall -> Luca migration of autonomous engineering planning. **Related:** #5 (the mining run that surfaced this candidate).
coilysiren 2026-05-30 05:43:42 +00:00
  • closed this issue
  • added the
    P4
    label
Commenting is not possible because the repository is archived.
No description provided.