kodebeat / papers / greenops
Making CI carbon visible, then enforceable
Carbon-badge and carbon-budget-action.
CI is the most easily optimised compute an organisation controls and the least examined. carbon-badge prices thirty days of job-minutes at each runner's power draw and labels every wattage measured, declared or guessed, because the gap between guessed and declared can be a factor of nineteen. carbon-budget-action then fails a pull request that exceeds a budget you set, with a report mode that cannot fail anything.
What is in it
- The problem — what goes unanswered without it, and who notices first.
- Why the obvious alternative falls short — stated plainly, including where it is the better choice.
- How it works — the method, not a feature list.
- Concrete use cases — with console output quoted from the repository, never reconstructed.
- The methodology behind any number it emits — every term shown, so the figure survives a question.
- What it deliberately does not do — the section most papers leave out.
Part of the GreenOps theme.
Get the PDF
One email with the download link, and this paper already selected. No follow-up sequence.