What CorPole is, and what it is not
CorPole keeps your requirements, decisions and constraints with a state on each, and hands coding agents only what binds today.
For: Solo builder, Team developer, Product owner, Project lead, Tester, Admin, Evaluator, Security & compliance
What it is
A requirements authority for teams that build with AI agents. Every record carries a state (Draft, Approved, Authority, Retired), and agents connect over MCP to read exactly what binds for the work in front of them.
- People decide what binds; agents propose.
- Requests arrive as demands and are handled as initiatives; requirements say what an initiative should change.
- The solution's design (business, functional, quality, technical and architecture records) describes what is built today; it changes when work carrying a design change is Done.
- Work, tests and code trace back to the records they serve.
- An agent policy and agent rules say what an agent may do and how it behaves.
What it is not
- Not a coding agent. The agent you already use writes the code; CorPole governs what it is told.
- Not a pipeline tool. No build orchestration, deployment or infrastructure.
- Not general-purpose work management. Work items exist to bring requirements to life, not to replace them.