Evaluator

You are deciding whether Corpole belongs in your team's toolchain.

You are deciding whether Corpole belongs in your team's toolchain. The fair question is what it does that a ticket tracker plus a CLAUDE.md does not.

The short answer is state and control. A file cannot say whether it still applies; a Corpole record can, and only Authority records reach the agent. A ticket tracker lets an agent write anything; in Corpole an agent can only propose, a person decides what binds, and the agent stops at conflicts and before sensitive actions. Everything traces from requirement to test to code, with a history of who decided what and why.

This page gathers the articles for a thirty-minute evaluation, what Corpole is and is not, how agents connect, what they can and cannot do, and how data and access are handled.

Start here

  1. See what a record carries and why only Authority binds.
  2. Walk through the screens a team uses every day.
  3. Check what an agent can and cannot do.
  4. Read how data and access are handled.
  5. Compare plans, then request access.

Getting started

Connect your agent

Agent policy & rules

Team & accounts

Security & data

Reference