Test cases per criterion
Unit, integration, end-to-end, manual and UAT tests, with Given/When/Then steps and an automation reference, each verifying named criteria.
Traceability and quality
Every criterion, its test, its work and its code, in one row.
When an agent writes most of the code, "is this requirement actually met?" needs an answer that does not depend on anyone's memory. Corpole keeps the chain from requirement to acceptance criterion to test to story to pull request, and shows where it breaks.
- Criteria Met or Not met from tests
- Gaps flagged, coverage measured
- Pull requests linked by code
TRACEABILITY CHAIN
- 01RequirementAuthority
- 02CriterionAC2 · met
- 03Testpassed in CI
- 04CodePR merged
COVERAGEGaps flaggedno test · no work · no code
The chain
A claim, its proof, and the moment it stops holding.
A criterion is not met because someone ticked it. It is met because its tests pass — and it stops being met the moment one fails.
Results from CI and agents
CI posts results to one endpoint; the agent reports its own. People record manual and UAT runs with one click.
Criteria that update themselves
One failing active test makes a criterion Not met; all passing makes it Met, with the tests as evidence.
No Done over a failing test
A story or task whose covered criteria have a failing test cannot be moved to Done. The message lists the tests and criteria.
Code linked by itself
Connect the GitHub repository and pull requests and commits that mention a code are linked. Opening a PR moves the story to review, merging it to verification.
Gaps you can filter
The traceability view shows one row per criterion and flags no criteria, no test, no work, no code and failing — with coverage percentages.
When something goes wrong
Defects and risks sit on the same records.
A defect is a requirement that is not being met. A risk is a requirement that might not be. Both belong next to the requirement, not in another tool.
Defects against requirements
Reported by a person or an agent, triaged by severity, tied to the requirement or criterion they break, fixed like a story and proven by a test.
A risk register
Probability × impact on a 5 × 5 matrix, with a planned response — avoid, mitigate, transfer or accept — and the work that carries it out.
Change history for audits
An append-only log of every change to records, criteria, relations, work, tests and code links, filterable by period, type and actor.
For delivery that has to answer to someone
Show which requirements are met, and by what.
Start with one project. The traceability view tells you on day one where criteria have no tests and where tests have no code.