Case

My agent followed a decision we had dropped

An old document in the repository still describes the approach you abandoned, and the agent read it as current.

For: Solo builder, Product owner, Team developer

What happened

You changed direction weeks ago, but the agent rebuilt something the old way, citing a file in the repository.

Why it happens

A file has no state. Nothing tells an agent that an ADR or a note in docs/ no longer applies, so it treats everything it finds as current.

What Corpole does

  • Gives every record a state. A Retired record never reaches the agent's context.
  • Flags a pull request that cites a Retired record, and the GitHub check fails on it.
  • Tells the agent that only Authority binds; Draft and Approved are informative.

What you do

  1. Find the record that describes the dropped approach and retire it, ideally with a replaces relation to the one that holds now.
  2. Move the old file's content into Corpole with /corpole:handover, so the file stops being an authority.
  3. Ask the agent to redo the change against the current Authority records.

Keep it from happening again

  • Retire a record the moment it stops applying; do not just edit its text.
  • Keep direction-setting documents in Corpole rather than in the repository.