Split `forgelm/compliance.py` into a sub-package (`_audit_log`, `_annex_iv`, `_provenance`, `_gdpr`) — deferred until Phase 16 S9 has landed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 18/100
Research direction
Do not start until Phase 16 S9 (#895) has landed, since the issue makes that a precondition. Then read forgelm/compliance.py and note its seams (audit log, Annex IV, provenance, GDPR), plus _DEFERRED_SPLITS in tools/check_module_size.py and the row at docs/roadmap/risks-and-decisions.md line 80. Done means a sub-package with every public name still importable from forgelm.compliance, the guard entry removed, test patch targets retargeted, and the CHANGELOG naming F-PR29-A1-06/07/08.
Written by the indexing model from the issue text.
Description
Deferred work ·
F-PR29-A1-06 / A1-07 / A1-08: compliance.py· severity Low · cost ~4-8 h · recorded indocs/roadmap/risks-and-decisions.md:80
Summary
forgelm/compliance.py is a deferred module split: the EU AI Act Art. 9-17 surface, Annex IV, the hash-chained audit log, provenance and the GDPR primitives live in one file. The module-size guard holds it to a fatal no-growth budget, but nothing pays the debt down until someone takes the split.
Condition or budget
Phase 16 S9 has landed and its audit-chain fixtures are re-verified; S9 is #895
State today (re-checked 2026-10-09)
2492 code lines against a budget of 2492 at 08f2426 (deferred at 2147; ~1500 at PR #29).
Related
#667 and #668 track how the module-size guard counts lines and accepts budget raises; decide them before relying on a module's budget.
Acceptance criteria
- The module becomes a sub-package along the recorded seams, behaviour-neutral, with every public name still importable from its current path.
- Its
_DEFERRED_SPLITSentry is removed fromtools/check_module_size.pyand every resulting module is under the normal ceiling. - Test patch targets that named the old module are retargeted to the module that resolves the name at call time (the
forgelm/verify.pysplit found five that silently moved). - The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).
Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.
- Dominant language
- Python
- Stars
- 9
- Forks
- 1
- Avg merge
- 11h 6m
- Merged PRs (30d)
- 29
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HodeTech/ForgeLM
-
area: site bug good first issue severity: low wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
HodeTech/ForgeLM#961 · 1 comment ·
Maintainers usually reply within 1 day
-
area: dev-tooling bug severity: low source: roadmap wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
documentation severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in HodeTech/ForgeLM
Similar issues
-
tunneld on Windows: Wi-Fi devices are not discovered because uvicorn runs on a ProactorEventLoopOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
doronz88/pymobiledevice3#2051 ·
Maintainers usually reply within 1 day
-
Remove DatacircleOpen
Difficulty 1/5 Under an hour Newbie friendliness 90/100
collabnix/awesome-mcp-lists#230 ·
Maintainers usually reply within 9 days
-
Groc schedules with out of range values pass config validation and fail later when the scheduler is builtPossibly taken @auraseb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
autowarefoundation/autoware_carla_scenario#342 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ianktoo/project-monitor#14 ·