Your team decides.
Nieme remembers.
Reality has the last word.
An AI cleans up a billing workflow. Every test passes. Two days later, a customer gets charged twice. Nieme connects the decision, the work, what happened in production, and what the next agent should already know.
- 01The team decides
- AAnaThis step in the billing flow looks redundant. I can’t find any documentation explaining why it exists.
- TTheoLooks like duplicated state. Simpler without it.
- MMayaAgreed. Let the agent simplify it.
SettledSimplify the billing flow without changing what customers seeCaptured as the objectiveWhy the step existed was never written down anywhere. The decision to remove it is.
- A
- 02The AI works with itIN CONTEXT
- Objective · #eng, 12 Sepsimpler flow, nothing changes for customers
- Repository rulesbilling service
- CI green
- Tests pass
- Review accepted
ShippedA reasonable refactor. Cleaner code, every check green. Nobody did anything wrong.
- 03Reality answers
- RRui · SupportAcme says they received the same invoice twice. INV-2291, 30 seconds apart.
- TTheo · EngProvider logs: the invoice was created. Our request timed out before the confirmation arrived, so the system retried.
- Linked by NiemePR · Simplify billing writes
NOT ACHIEVEDThe code passed. The objective didn’t.The provider did the work; the answer never came back. Nieme connects the complaint, the shipped change, the provider logs and the original objective.
- R
- 04The next one starts aheadIN CONTEXT
- Objectiveadd invoice sync to the subscription billing system
- Learned · from validated prior worka timeout is not proof the write failed — check provider state before repeating a consequential write
- Why it is herechange → incident → evidence → validation → decision
Lessons this run inherits1paid for last timeA different integration, months later, on any model. It starts with a lesson production already charged for.
The company doesn’t pay twice for the same lesson. Generating the next code isn’t the hard part anymore; making the next agent inherit what production taught the company is. Each move lands in one record — an operation.on. You never have to type it.
