Product owner
You write the requirements and decide what binds.
You decide what the product must do. With agents in the loop, that decision now has two audiences: the people on the team, and the agents that read every word literally, every run. A vague requirement used to cost a clarifying question; now it costs a wrong implementation.
Corpole puts you in control of what binds. Agents draft records and changes, but nothing is binding until you approve it; when an agent thinks a requirement should change, you see the difference and decide. Open questions come to you instead of being guessed away, and every Authority change keeps its reason.
This page gathers the articles you will use most: the record types, writing requirements an agent can follow, reviewing proposals and changes, answering questions, and giving every requirement criteria that a test can prove.
Start here
- Learn the record types: objectives, requirements, constraints.
- Review AI proposals from the Overview: edit, approve or delete each Draft.
- Accept or reject change proposals on the record page, where the difference is shown.
- Answer the questions agents open instead of guessing.
- Give every requirement acceptance criteria, so its proof can be tracked.
Getting started
Connect your agent
Records & authority
- GuideObjectives
- GuideBusiness Requirements
- GuideStakeholder Requirements
- GuideFunctional Requirements
- GuideNon-functional Requirements
- GuideTechnical Requirements
- GuideProject Requirements
- GuideProduct Constraints
- GuideBusiness Constraints
- GuideProject Constraints
- GuideExplorer
- GuideNew record
- GuideRecord detail
- GuideEdit record
- GuideChanges
- How-toWrite a requirement an agent can follow
- How-toReview an AI proposal
- How-toAccept or reject a change proposal
- How-toRetire or replace a record
Relations & conflicts
Work & boards
Knowledge
Agent policy & rules
Traceability & quality
When things go wrong
- CaseMy agent followed a decision we had dropped
- CaseMy agent changed a requirement to fit its code
- CaseThe requirement changed while the agent was working
- CaseThe agent says "done" but a criterion is not met
- CaseAn agent is flooding the review queue
- CaseThe client asks why we built it this way
- CaseMy agent insists on something Authority forbids