Implement `output.cost_tracking` (per-GPU rates, alert / halt thresholds, audit and webhook events) — or retire the promise
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
Research direction
Start with the deferral row at docs/roadmap/risks-and-decisions.md:94 and the GPU-cost manual pages (EN and TR) that advertise output.cost_tracking. Confirm that ForgeConfig in forgelm/ has only the scalar training.gpu_cost_per_hour field. The maintainers have not chosen a path, so first ask whether to build the block or drop the promise. Done means either the schema, audit event, webhook event and EN/TR docs exist, or the manual and roadmap drop the promise. In both cases the row leaves the deferral table and the CHANGELOG names F-PR29-A2-04.
Written by the indexing model from the issue text.
Description
Deferred work ·
F-PR29-A2-04· severity Medium · cost ~1 day · recorded indocs/roadmap/risks-and-decisions.md:94
Summary
The GPU-cost manual (EN + TR) advertises an output.cost_tracking block with per-GPU rates, a currency and alert / halt thresholds, but ForgeConfig has no such field; only the scalar training.gpu_cost_per_hour exists. The PR #29 review deferred it because it needs a CostTrackingConfig model, an audit event when a threshold is crossed and a webhook lifecycle event (which extends the published webhook vocabulary). The documentation issues only correct the pages, so the build-or-drop decision is still open.
Condition or budget
None recorded (the row still names v0.6.x).
State today (re-checked 2026-10-09)
No cost_tracking or CostTrackingConfig exists in forgelm/; the manual labels its examples as forward-looking placeholders.
Related
#428, #241, #429 and #444 correct the cost documentation; none asks for the implementation.
Acceptance criteria
- Either the block exists (schema, audit event, webhook event, EN/TR docs) or the manual and the roadmap drop the promise and the row is closed with that reason.
- 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
- 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
-
area: site bug good first issue severity: low source: review-2026-09 wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation 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 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
topoteretes/cognee#5773 ·
Maintainers usually reply within 1 day
-
MiKTeX: a failed build reports no errors because texify --quiet switches the log to file:line: styleOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
SublimeText/LaTeXTools#1718 ·