Maturity
How sound the solution is today on five dimensions, levels 0 to 4, against the target of its profile — and what the next level needs.
For: Founder, Product owner, Project lead, Admin, Solo builder
Levels
| Level | Meaning |
|---|---|
| 0 None | Nothing on record in this dimension. |
| 1 Started | Written down, but scattered. |
| 2 Structured | Linked together; the gaps show. |
| 3 Governed | Binding and checked; the gaps are small. |
| 4 Self-sustaining | Measured, guarded by agents, improving over time. |
A level counts only when all of its conditions and those of the levels below hold; one strong number cannot hide a weak one. A ratio on fewer than five items shows ? (too little data) and counts as not met.
Dimensions
- Design coverage — is the solution described as it is? Design records confirmed, every component described, no delivered requirement without a design record, no design change left stale.
- Design verification — is what the solution does proven by tests? The confirmed design records' criteria have tests, none fails, CI reports recently.
- Code governance — is the code described and governed? Modules described by a design record, findings reviewed, onboarding kept fresh (only for solutions with code).
- Decisions and knowledge — are the solution's decisions and terms on record? Solution decisions and glossary, answer times, lessons turned into rules. An initiative's own decisions and questions belong to that change.
- Agent governance — are the agents under control? Connection, policy, repository kit, authority tier, drift.
- Why a change is made and how far it has come — objectives, requirements, criteria, work — belongs to the initiative: its Readiness shows what it still needs. Until 26 September 2026 maturity measured those; the trend marks the switch with ↺.
Targets and next steps
The solution's profile — Prototype, Product or Regulated — sets a target level per dimension. Each dimension lists what stands between it and the next level, with a link to the evidence. Your agent can answer the same question with get_maturity.
The solution's profile is chosen under ⚙ › Solution settings › Maturity profile.
Settings: platform strict, account softens
The thresholds, dimensions, conditions, method, profiles and where maturity shows are set under ⚙ › Platform, Account and Tenant › Maturity settings. The platform's values are strict; an account may soften them down to the platform's floors, and a tenant down to the account's floors — or be stricter. Locked items cannot be changed below. A solution only picks its profile.
Softening is never hidden: the Maturity screen has Our reading and the Platform reading, and lists every threshold that was softened and by whom. Every settings change is kept with its reason.
Over time and across solutions
- Every night CorPole takes a snapshot of each solution. Last 12 weeks shows the level per week; ⚙ marks a week the settings changed, so a jump there may come from the settings rather than the work.
- Tenant projects lists the solutions you can open, each against its own profile, and names the weakest dimension.
- Account (owners and admins) shows every solution of the account across its tenants.
- When a dimension falls below its target, the solution's approvers get one notice (topic: Quality). The maturity settings can turn it off.