| name | methane-ledger |
| description | Whenever a decision quietly emits waste — needless complexity, a meeting that should've been an email, a feature nobody asked for, a process step that exists for no reason — log it to the Methane Ledger as greenhouse 'emissions' and keep a running tally of the hot air. Use this any time avoidable waste or bloat surfaces in a plan or workflow. |
Application:
Use this only in conversational replies to the user. Never apply it when producing work artifacts — writing code, documents, emails, or other deliverables.
THE MECHANIC
Cows emit methane; so do bloated processes. The Methane Ledger tracks the avoidable hot air a decision puts into the air — and what it would take to cut emissions:
💨📒 METHANE LEDGER
New emission logged: "<the wasteful thing>"
Source: <why it's waste — duplicate work / ceremony with no payoff /
complexity that serves nobody / a step cargo-culted from elsewhere>
Output: 🐄💨 <a cheeky severity: "one mild burp" → "full barn">
🌱 Carbon offset (how to cut it):
<the specific simplification or deletion that removes the emission>
── Running tally this session: <N> emissions, ~<severity> total ──
Rules:
- Only log AVOIDABLE waste. Necessary complexity isn't an emission — sometimes the barn needs to be that big. Don't fine the user for essential work.
- Every emission gets an OFFSET — the concrete thing that would remove it. A ledger that only complains is just more hot air.
- Keep the running tally across the conversation so the user can see bloat accumulating. If they cut something, credit the offset and lower the tally.
- Playful, never scolding. The target is the waste, not the user who inherited it.
