fix(engine/v2): relax formality-spread penalty for SMART_CASUAL and AVANT_GARDE#39
Open
lucavandee wants to merge 2 commits into
Open
fix(engine/v2): relax formality-spread penalty for SMART_CASUAL and AVANT_GARDE#39lucavandee wants to merge 2 commits into
lucavandee wants to merge 2 commits into
Conversation
…ion bias QUIZ_STYLE_TO_ARCHETYPE: - classic: 1.0 CLASSIC (was 0.7/0.2/0.1 verdeeld over CLASSIC/BUSINESS/MINIMALIST) - smart-casual: 0.7 SC + 0.3 CLASSIC (was pure 1.0 SC) OCCASION_ARCHETYPE_BIAS: - work: BUSINESS 0.25→0.15, CLASSIC 0.2→0.25 (minder aggressieve business-push) - casual: + AVANT_GARDE 0.1, + STREETWEAR 0.1 (meer variatie in casual) - date: + AVANT_GARDE 0.1 (ruimte voor expressievere date-looks) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…VANT_GARDE The coherence checker penalized the signature looks of these archetypes: blazer+tee (smart-casual kern) triggered formality_mismatch, and avant-garde combos lost points for the proportional tension that defines the style. - evaluateCoherence now accepts an optional UserStyleProfile and picks archetype-aware formality thresholds. - SMART_CASUAL tolerates spread up to 0.55 without penalty (was ~0.25). - AVANT_GARDE tolerates spread up to 0.70 without penalty. - Default thresholds unchanged for other archetypes. - composer.scoreComposition forwards the profile to evaluateCoherence. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
✅ Deploy Preview for fitfiai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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
evaluateCoherencenow accepts an optionalUserStyleProfileand selects archetype-aware formality thresholds.formality_mismatch).composer.scoreCompositionnow forwards the profile.Why
Test-agents flagged that the coherence checker was punishing the signature looks of these archetypes. A blazer+tee (smart-casual kern) was being marked as a formality mismatch, and avant-garde compositions were losing points precisely for what makes them avant-garde.
Test plan
npm run buildsucceedsformality_mismatchreasonformality_mismatchat spread > 0.45