Solution design
The design records describe the solution as it is today: business design (BDR), functional (FDR), non-functional (NFDR), technical per component (TDR) and architecture decisions (ADR). Requirements belong to initiatives and say what should change; the design belongs to the solution and changes only when the work that carries a change is Done.
For: Product owner, Project lead, Team developer, Solo builder
Kinds
- BDR: processes and business rules.
- FDR: capabilities and screen flows.
- NFDR: quality characteristics in the ISO 25010 set (performance, security, reliability, usability …) and compliance.
- TDR: per component — modules, interfaces, data, integrations, infrastructure.
- ADR: architecture decisions and their reasons.
How a design record changes
An epic, story, task or defect carries design changes: add a record, change one or retire one (on the work page, under Design changes; agents use propose_design_delta). When the work is Done each change becomes a new version, with the work, the requirements it implemented and its initiative as the reason. If two open items change the same record, the first to be Done wins and the other's change is marked to be looked at again.
Drafts come from delivered requirements and from findings in code, documents or tests; a person with the authorize permission confirms each after checking it describes the solution as it is. A requirement counts as delivered when it is Authority and all the work that implements it is closed with some of it Done; when that work is Done, CorPole draws its draft by itself, and Draw drafts catches up the rest.
A requirement realizes the design records that describe what was built for it: the link is made when the work's design change is applied or a draft is drawn from the requirement, and shows on both pages — Realized by design records on the requirement, Realizes requirements on the design record.
Design coverage at the top of the page shows how far the solution is described: the share of confirmed design records, the drafts waiting, delivered requirements without a design record, and code modules without one. In the drafts view, tick drafts and choose Confirm selected, or Confirm all shown.
Solution document: the links at the top give the whole description as Word, as a print page (save it as PDF) or as Markdown — components and repositories, every current design record with its acceptance lines and their state, code modules, accepted decisions, standards, the glossary and open solution risks. Drafts are marked as not yet confirmed. The initiative page gives the same for one change: why (demands), requirements with criteria and tests, design changes, work, acceptance testing and what is still open.