Loop 2 layer 8: conflict dedup against existing Wispr Flow Snippets #6

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

Originally filed by @coilysiren on 2026-05-20T12:01:08Z - https://github.com/coilysiren/voice-flow-learning-loop/issues/11

Context

Layer 8 of the 8-layer build path for Loop 2 documented in README.md. Closes the loop.

Goal

Don't propose snippets for phrases Kai has already snippet-ized. Read the existing snippets list and exclude duplicates from layer 7's proposals.

  • Until Wispr Flow ships a snippets-list API or MCP, this is manual export: Kai exports her snippets list from the Wispr Flow desktop app to a file (JSON/CSV/whatever Wispr produces), and the asker reads it.
  • Detect both trigger-collision (proposed trigger already used as a trigger in the existing list) and expansion-collision (proposed expansion already exists as another snippet's expansion).
  • Report collision types separately in the candidate output so Kai sees which proposals were filtered and why.

Done when

  • Layer 7's proposals are filtered against the exported snippets list.
  • Trigger and expansion collisions are reported as separate categories in the output.
  • README documents the manual-export step until a Wispr Flow API or MCP lands.
  • A snippets-export-path config option points the asker at Kai's exported file.

Depends on: layer 7. Unblocks: closed-loop validation when Wispr Flow exposes an API (out of scope for this issue; tracked as a separate forward-looking thread tied to the Tanay conversation).

_Originally filed by @coilysiren on 2026-05-20T12:01:08Z - [https://github.com/coilysiren/voice-flow-learning-loop/issues/11](https://github.com/coilysiren/voice-flow-learning-loop/issues/11)_ **Context** Layer 8 of the 8-layer build path for Loop 2 documented in [README.md](../blob/main/README.md). Closes the loop. **Goal** Don't propose snippets for phrases Kai has already snippet-ized. Read the existing snippets list and exclude duplicates from layer 7's proposals. - Until Wispr Flow ships a snippets-list API or MCP, this is manual export: Kai exports her snippets list from the Wispr Flow desktop app to a file (JSON/CSV/whatever Wispr produces), and the asker reads it. - Detect both **trigger-collision** (proposed trigger already used as a trigger in the existing list) and **expansion-collision** (proposed expansion already exists as another snippet's expansion). - Report collision types separately in the candidate output so Kai sees which proposals were filtered and why. **Done when** - Layer 7's proposals are filtered against the exported snippets list. - Trigger and expansion collisions are reported as separate categories in the output. - README documents the manual-export step until a Wispr Flow API or MCP lands. - A `snippets-export-path` config option points the asker at Kai's exported file. **Depends on:** layer 7. **Unblocks:** closed-loop validation when Wispr Flow exposes an API (out of scope for this issue; tracked as a separate forward-looking thread tied to the Tanay conversation).
coilysiren added
P4
and removed
P3
labels 2026-05-31 07:01:25 +00:00
Commenting is not possible because the repository is archived.
No labels
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/voice-flow-learning-loop#6
No description provided.