Project settings

Project settings for agents

Record language: agents write this project's records, criteria, questions and work items in it, whatever language you talk to them in. When it is not set, the agent asks during the kickoff.

Go ahead without the kickoff: in a new project without any Authority record, someone who can make records Authority may let work start before the kickoff interview, with a reason. Agents stop offering the interview and the code gate stops asking until the first Authority record; the choice is kept in the history and can be withdrawn. If the tenant's gate for new projects is enforced, it still applies.

Authority handover

Projects created with existing code start in Shadow; everything else is Full. Only people who manage the project's integrations declare the tier; every change is kept in the history. Re-apply the repository kit afterwards so CLAUDE.md says the same.

Inventory lists what governs the project outside Corpole — agent rule files, requirement documents, ADRs, glossaries, tickets — with its size and status: To move, Moved, Historical or Stays outside. Agents record it during the handover; you settle what stays outside.

Readiness shows the share of settled sources, Authority records, drafts waiting for review and open questions, and whether the next tier is due: Shared needs an inventory, half of it settled and at least one Authority record; Full needs every source settled, no draft waiting and no open question.

Agent policy

Per action — migrations, dependencies, CI/CD, security code, tests, public contracts, merging — choose Allowed, Ask first or Forbidden. The project inherits the tenant's policy and can only make it stricter. Forbidden Corpole actions are refused by the server; code actions become Claude Code permission rules through the repository kit.

Guarded areas: for security code, tests, public contracts, CI/CD and production access you can list the files that belong to them (e.g. src/auth/**). An agent may change those files only at that action's level: Claude Code asks or refuses before the edit, even without re-applying the repository kit, and the PR check flags them for any client. Areas add up from account to tenant to project.

When you allow an agent to change a guarded area or ungoverned code in Claude Code, the plugin tells Corpole and the approval is kept in the history: who allowed which agent to do what.

GitHub and CI

Name the repository (owner/name) and add the webhook; pull requests and commits that mention a story, task or defect code link themselves and move the work. CI can report test results with a service token from Agents → Agent tokens.