docs(spec): 009 note-detection capability domain (draft stub, refs #727)#323
Open
byrongamatos wants to merge 1 commit into
Open
docs(spec): 009 note-detection capability domain (draft stub, refs #727)#323byrongamatos wants to merge 1 commit into
byrongamatos wants to merge 1 commit into
Conversation
Scheduling placeholder for the next capability-domain slice after audio-input (006) and audio-monitoring (007): a per-binding, chart-decoupled, multi-consumer control plane over the existing detection DSP, exposing a monophonic pitch primitive and a polyphonic note-set verification primitive scored against a requester-supplied tuning context. Consolidates the two fragmented detection surfaces (minigames YIN + window.noteDetect) behind one contract; does not implement DSP or own consumer judgment. Driven by a real non-chart consumer (SlopScale, Chord Sprint) the current surfaces can't serve. Interim bridge: notedetect setVerifyTarget(notes, ctx) (plugin #62), whose per-call context maps onto this domain's per-binding context. spec.md + plan.md only; full data-model/contracts/tasks on scheduling, per the Spec 003 migration gate. Refs #727. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> (cherry picked from commit 7b40a63a4656a1d1e473113d83c2927241993702)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #727.
Adds
specs/009-note-detection-domain/(spec.md + plan.md) — a draft stub scheduling the next capability-domain slice after audio-input (006) and audio-monitoring (007).What it specifies
A per-binding, chart-decoupled, multi-consumer control plane over the existing detection DSP:
slopsmithMinigames.scoring.createContinuousmono-YIN +window.noteDetect) behind one contract → one DSP source of truth, so improvements (bass persistence floor, distortion, future models) land once and reach every consumer.Why a stub
Per the spec-kit flow, this PR is spec.md + plan.md only; data-model / contracts / tasks are generated when the slice is scheduled, passing the Spec 003 migration gate. It depends on 006 and 007 (007 currently paused at #667), so it isn't startable yet — this fixes the scope and names the requesters now.
Relation to the "work now" bridge
The interim, forward-compatible step is already in flight on the plugin: notedetect
setVerifyTarget(notes, ctx)(slopsmith/slopsmith-plugin-notedetect#62), consumed by a SlopScale adapter (fork PR). Its per-call tuning context maps 1:1 onto this domain's per-binding context — the bridge is re-pointed, not discarded, when the domain lands.No code/runtime changes; docs only.
🤖 Generated with Claude Code
Summary by CodeRabbit