Project lead

You plan the work and own how disciplined the delivery is.

You plan the work and you are accountable for how disciplined delivery is. Agents make the team faster, and they also make it easier to lose control: work starts that nobody released, a migration runs that nobody approved, and problems surface only in review.

Corpole gives you the levers. The agent policy decides what agents may do alone, what needs asking and what is forbidden. Agents start only on work you have moved to Ready. Agent health shows drift signals — agents that loop on a failing test, skip the rules or push to Done — and you resolve them with a root cause that can become a lesson for everyone.

When something breaks in production, you are also the person who can declare an emergency: a time-boxed window where the fix goes first and the paperwork follows, on the record. This page gathers what a lead needs, in the order you are likely to need it.

Start here

  1. Set the agent policy: what is allowed, what needs asking first, what is forbidden.
  2. Write the project's agent rules.
  3. Move the agent's proposed work from Backlog to Ready when it is worth doing.
  4. Keep an eye on Agent health and resolve drift signals.
  5. Know the emergency path before you need it.

Getting started

Connect your agent

Records & authority

Relations & conflicts

Work & boards

Knowledge

Agent policy & rules

Traceability & quality

Existing codebases

When things go wrong

Team & accounts

Security & data

Troubleshooting

Reference