Case

My agent forgot what we decided yesterday

A decision made in one chat session is gone in the next. Decisions belong in records, not in chat history.

For: Founder, Solo builder, Team developer

What happened

Yesterday you and the agent agreed on an approach. Today, in a new session, it proposes the opposite as if the conversation never happened.

Why it happens

A chat session is the agent's only memory. When the session ends, what was agreed there ends with it, unless it was written somewhere the next session reads.

What Corpole does

  • Keeps decisions, requirements and constraints as records, so they outlive the session they were made in.
  • Gives the agent what binds at the start of every session: it reads the agent policy, the standards and what changed since it last looked (get_changes).
  • Hands the agent the work context of the item it works on: the why-chain, criteria, constraints and accepted decisions.

What you do

  1. Ask the agent to record the decision you just made: it proposes it with propose_decision.
  2. Accept the decision in Corpole. From then on it binds for what it governs.
  3. Start the next session and check that the agent cites it (the decision's code, e.g. DEC-4F20A1).

Keep it from happening again

  • When you agree something in chat that should hold tomorrow, ask for it as a record before you close the session.
  • Run /corpole:init in the repository so the agent reads Corpole first in every session.

Ask your agent

"Record what we just agreed as a decision in Corpole, and cite it from now on."