Guide

Maturity

Where the project stands on seven 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

LevelMeaning
0 NoneNothing on record in this dimension.
1 StartedWritten down, but scattered.
2 StructuredLinked together; the gaps show.
3 GovernedBinding and checked; the gaps are small.
4 Self-sustainingMeasured, 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

  • Intent — is it clear why we build this? Objectives broken down, measurable, nothing orphaned.
  • Requirements — is what to build binding and clear? Criteria, constraints, conflicts, open questions.
  • Verification — is what we built proven right? Work on requirements, tests on binding criteria, traced pull requests.
  • Delivery — does the work flow well? Linked work, triaged defects, rework, long blocks.
  • Agent governance — are the agents under control? Connection, policy, repository kit, authority tier, drift.
  • Codebase — is the code tied to requirements? Module coverage and onboarding (only for projects with code).
  • Decisions and knowledge — are decisions and lessons on record? Decisions, glossary, answer times, lessons turned into rules.

Targets and next steps

The project'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 project's profile is chosen under ⚙ › Project 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 project 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 projects

  • Every night Corpole takes a snapshot of each project. 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 projects you can open, each against its own profile, and names the weakest dimension.
  • Account (owners and admins) shows every project of the account across its tenants.
  • When a dimension falls below its target, the project's approvers get one notice (topic: Quality). The maturity settings can turn it off.