The requirement changed while the agent was working
Someone updated a requirement mid-story, and the agent kept building against the old version.
For: Team developer, Product owner
What happened
Halfway through a story, the product owner changed a requirement it implements. The agent carried on with what it had read an hour earlier.
Why it happens
The agent read the context once, at the start. Without a signal it has no reason to read it again.
What Corpole does
- Notices when a record the agent is working on changes after the agent last read it, and tells the agent in its next reply to read again first.
- Lets the agent ask exactly what changed, by whom and why, with
get_changes.
What you do
- Tell the agent the requirement changed, or let the signal do it.
- Ask it to re-read the work context and say what the change means for the work already done.
- Decide together whether to adjust or restart.
Keep it from happening again
- Give the reason when you change an Authority record; the agent sees it and can explain the impact.
Ask your agent
"What changed in Corpole since you started this story, and what does it mean for the work so far?"