Refine art. 27(1)(b) FRIA gating to Annex III §5(b)/§5(c)#4
Closed
abk1969 wants to merge 2 commits into
Closed
Conversation
Reg. 2024/1689 art. 27(1)(b) names credit-scoring (§5(b)) and life/health insurance (§5(c)) specifically — not the whole §5 bucket. Add ANNEX_III_5_SUBITEMS metadata (a/b/c/d), gate path (b) on (b) or (c) presence in answers.annexIII5Subitems, and expose a sub-question on Step 5 so users can refine their selection. §5(a) and §5(d) fall back to path (a) (deployerKind-dependent FRIA gate). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- friaB now names §5(b)/§5(c) explicitly instead of generic §5
- ANNEX_III_5_SUBITEMS[].ref is now {en, fr} (matches ANNEX_III_AREAS shape)
— UI resolves via t(sub.ref, lang) so French users see "Annexe III §5(x)"
instead of the English "Annex III §5(x)"
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced May 15, 2026
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
Stacks on top of #3. Closes the deferred follow-up from #3's review: precise art. 27(1)(b) FRIA gating per Reg. (EU) 2024/1689.
The earlier
computeRoleNotestriggered FRIA via path (b) for any Annex III §5 selection, but the regulation names only §5(b) credit-scoring and §5(c) life and health insurance. Items §5(a) (public benefits eligibility) and §5(d) (emergency dispatch / triage) are still high-risk but should NOT trigger path (b) — they fall back to path (a)'s deployerKind requirement.Changes
ANNEX_III_5_SUBITEMSexported fromclassify.js— 4 sub-items (a/b/c/d) with bilingualref(Annex III §5(x)/Annexe III §5(x)),label, anddesc.computeRoleNotespath (b) refined: replacesinAnnexIII5 = areas.includes(5)withinAnnexIII5bOr5c = areas.includes(5) && annexIII5Subitems.some(s => s === 'b' || s === 'c'). Path (a) is unchanged — a public-body deployer of §5(d) still gets FRIA via art. 27(1)(a).friaBlabel now explicitly cites §5(b)/§5(c) instead of generic §5.Tests
Annex III §5 sub-items — art. 27(1)(b) refinementblock; 2 pre-existing §5 tests updated to includeannexIII5Subitems).private_other→ no FRIA (correctly falls back to path (a) which fails the deployerKind gate)public_body→ FRIA via path (a) (art. 27(1)(a))['a','b']→ still triggers path (b)Regulatory citations
Stacking note
This PR targets
feat/classify-regulatory-gaps(#3) as its base. When #3 merges to main, GitHub will auto-rebase this PR's base to main. If you prefer to merge #3 first and then open this against main directly, close this PR and re-create.Test plan
private_otherdeployer → FRIA shown with art. 27(1)(b) reasonpublic_bodydeployer → FRIA shown with art. 27(1)(a) reason🤖 Generated with Claude Code