Agent policy & rules
What an agent may do alone, the rules it follows, notices.
Two things shape an agent in CorPole: what it is allowed to do, and how it should behave. The agent policy answers the first: for each kind of action — migrations, dependencies, CI/CD, security code, merging, production data and CorPole's own actions — it is allowed, ask first, or forbidden. CorPole enforces it before the action, not after.
Agent rules answer the second. They flow down from the platform through account, tenant and solution to each person, and every agent receives them in order with every policy read. Locked platform rules keep the basics in place for everyone: act within the person's permissions, put Authority first, propose instead of decide, stop at conflicts, keep secrets out.
This section also covers what the agent reads at the start of a session, the notices CorPole sends to people directly rather than through the agent, the “your agent is waiting” signal, and a reference list of what an agent can never do, whatever the policy or the prompt.
If an agent surprised you by doing too much, or by stopping too often, the answer is usually in the policy or the rules, and the articles here show where to change it.
Articles in Agent policy & rules
- GuideGovernance previewBefore a work gate, an agent permission in CorPole or a code rule changes, see what it would do — which solutions it reaches, what the last 30 days would have looked like, what it would stop or free today. Nothing is changed.
- GuideSolution settingsHow this solution is built and how agents work in it: its components and repositories, record language and kickoff, authority handover and agent policy. Open it from ⚙ › Solution in the top bar. People who manage the solution's integrations can change it.
- GuideAgent rulesThe behavioural rules every AI agent connected to CorPole follows, and how each level adds to them.
- GuideWaiting for youEvery card that waits for you in the solution — agent drafts, change proposals, proposed decisions, open questions, proposed solution rules — gone through in one pass, with your agent's preparation.
- GuideNoticesMessages from CorPole to you: drafts waiting for your approval, a solution your agent created, changes proposed to records you own, drift signals and emergencies.
- GuideMy sessionsYour coding-agent sessions: when each started, when the agent worked, waited for you or sat idle, and what it touched in CorPole. Only you see it in full.
- ConceptThe agent policy: allowed, ask first, forbiddenPer action, decide what an agent may do alone. CorPole enforces it before the action.
- How-toWrite your own agent ruleRules shape how an agent behaves. Yours apply to the agent that acts for you, on top of the solution's.
- ConceptWhat your agent reads at the start of a sessionBefore it writes code, the agent reads its policy and rules, the standards and what changed.
- ReferenceWhat an agent can never do in CorPoleSome decisions always belong to a person, whatever the policy or the prompt.