Agents

What agents receive

Agents read the Authority records, their acceptance criteria, the constraints and accepted decisions around them and the standards that apply. Approved records are informative; Retired ones never drive new work. Asked about a story, an agent gets its whole context slice (get_work_context): the chain up to the objective, criteria to meet, tests, conflicts and recent changes.

Ways to connect

Tokens and connected apps

• Personal tokens: everyone creates their own, one per machine or tool, with an expiry. An agent using one acts as you: your permissions, and everything it does is recorded under your name. Shown once; revoke it any time.
• Service tokens are for CI (the GitHub check, test results). Only people with the Integrations permission create them; they act for their creator. The single project token of earlier versions is now listed as a service token.
• Tick Allow proposing to let the agent propose records, changes, work items and tests and report results.
• People with the Integrations permission see every token in the project and can revoke any of them; the owner is notified. Creating and revoking tokens is written to the project history.
• Sign-in connections appear under Connected apps; disconnect them there and the next call is refused.
• An agent never has more permissions than the person it acts for.
• Corpole masks secret-looking values (tokens, keys, passwords, card and national ID numbers) in everything an agent sends, and tells you when it did — rotate the secret if it was real.

Keep in mind Do not share a personal token: whoever holds it acts as you. Never paste it into a chat, a record or a file in the repository; revoke it if it may have leaked.

Production emergency

When production is broken and a fix cannot wait for its requirements, a person allowed to declare an emergency opens a window (default 4 hours) here or through their agent. Everyone in the project is told. The code gates then advise instead of refusing, a critical defect tracks it (already Ready, so the agent can start it) and a red Emergency label shows in the top bar. Actions the policy forbids stay forbidden. When it ends, a Make good task is opened for the governing requirement and its test, and the requirement owners are asked to complete it.

If the fix needs longer, Extend once adds hours with a reason, up to 12 hours after the declaration in total. Everyone in the project is told; the extension is kept in the history.

Agent health

Signs that an agent is going the wrong way, caught before the work piles up. L1 the agent was told, L2 you were told, L3 flagged here for the integration managers, L4 the server refused.

Resolve a signal once it is handled: pick the root cause (agent, requirement, configuration, process or false positive) and note what was done. Tick Keep it as a lesson and the note becomes an accepted lesson that agents read in their context.

Corpole closes a signal itself when its condition is gone: the test passes, the stalled item moves or gets a code link, the work reaches Done. Stalled work is checked every day, even if nobody opens this page. Trend shows the last 30 days by signal, signals per active agent-day and the root causes. Thresholds are set on the Account page and can be overridden per tenant in Settings.

Agent metrics

Ten measures of how agents and people work together over the last 30 days: traceable pull requests, accepted proposals, criteria met the first time, time to answer a question, time agents wait, rework, drift density, the learning loop, agent calls per story and flow time. Each shows its target; it turns green or amber once there is enough data.

Label a trivial pull request no-requirement so it counts as a deliberate exception, not ungoverned code.

Agent activity

Agents → Activity keeps every call a coding agent made to Corpole: what it sent, what Corpole did inside — records changed, notices sent, drift signals raised, actions refused, secrets masked — what it gave back and how long it took. Filter by tool, agent, result, record code or date, and export the list as CSV.

Secrets are masked before anything is stored. The full answer is kept for 30 days; its beginning and a SHA-256 fingerprint stay, so you can later show what an agent was given. People who manage the project's integrations, tenant owners, admins and auditors see every call; others see the calls made for them.

GitHub, repository kit and activity

Connect the repository on Project settings → GitHub and CI so pull requests and commits that mention a code link themselves and move stories. The Repository kit makes the repository treat Corpole as its requirements authority; its CLAUDE.md block carries a stamp, and the Claude Code plugin tells you at session start when the agent policy or the authority tier changed and the kit should be re-applied (/corpole:init). Agent activity lists the last 50 reads and proposals.

PR check: the repository kit's GitHub Action sends the files each pull request changes. Corpole answers in the check: ungoverned code (fails under the enforced gate), a module whose findings are under review, files outside the modules of the cited work, other open pull requests changing the same files, and emergency rules. Corpole needs no GitHub credentials for this; re-apply the repository kit to get it.