[Epic] Deferred work · conditions and budgets recorded in risks-and-decisions.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 5/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
This is a tracking epic, not a change to make. Read docs/roadmap/risks-and-decisions.md at the linked commit to see the deferred rows and their conditions, then read CONTRIBUTING.md under Finding Work: Issues and the Project Board. Pick a single sub-issue from the list, check its recorded condition, and treat done as that sub-issue's own closing criteria being met.
Written by the indexing model from the issue text.
Description
Epic · Roadmap · 24 issue(s)
Scope
Work that was deliberately deferred and recorded in risks-and-decisions.md with a condition or a budget instead of a date. Each sub-issue states the recorded condition: issues labelled deferred should not be started until it holds; the others are plain leftovers that can be picked up any time. A row leaves the decisions table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.
How to work on it
Each sub-issue can be claimed on its own. An issue labelled deferred names a condition: check that it holds before starting, and say so in the PR. See CONTRIBUTING.md, Finding Work: Issues and the Project Board; progress shows in the sub-issue list and in the project's Sub-issues progress field.
Done when
- Every sub-issue is closed (done, or closed with a reason).
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
- 8h 10m
- Merged PRs (30d)
- 5
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: dev-tooling bug severity: low source: roadmap wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Site: the theme-locked --code-comment grey (#6a6f80) on the dark code surface is 3.8:1, below WCAG AA, in both themes (F-W1-SITE-06)Possibly taken @vortsghost2025 claimed this 1 day ago. Openarea: site bug good first issue severity: low source: review-2026-09 wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Choosing-a-trainer table documents KTO rows as {prompt, response, label}, but the KTO loader requires a completion column (F-W1-DOCS-TRAIN-02)Possibly taken @vortsghost2025 claimed this today. Opendocumentation good first issue severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
-
documentation severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in HodeTech/ForgeLM
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
WingedGuardian/GENesis-AGI#3375 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#4601 ·
Maintainers usually reply within 1 day
-
approved Good First Issue scope: docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
hiero-ledger/hiero-sdk-python#2730 · 3 comments ·
Maintainers usually reply within 1 day