docs: propose active preference selection research - #147
Draft
PhysShell wants to merge 2 commits into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
docs/proposals/active-preference-selection.mddocs/proposals/README.mdWhy
S8 now captures favorite / reject / history / provenance, while S9 plans the canonical feedback contract and a simple explainable reranking baseline. CODA suggests a useful later question: can Griff spend limited user attention on the comparisons that most reduce uncertainty?
CODA's classification machinery does not fit Griff directly. Musical preference is not an objective class label, candidates are different musical objects, and the preferred strategy is context-dependent. The proposal therefore adopts the posterior → hypothetical update → acquisition loop, but recommends pairwise/contextual preference models and offline replay rather than porting CODA's code or confusion matrices.
Guardrails
Decision requested
Approve only a future Phase 0 audit and benchmark contract after the S9 feedback contract and simple baseline are accepted. Implementation and product promotion require separate evidence and acceptance contracts.
Validation
Docs-only branch compared against
main: