Coverage status

Purpose

The CoverageStatus domain captures the actual level of domain documentation or insight achieved in an organisational unit, derived through data analysis. It provides a comparison to expectations and highlights maturity gaps.

Usage

Coverage status is generated by Orthogramic after parsing documents and evaluating their contribution to each business domain. It enables data-driven measurement of architectural maturity and supports reporting, recommendations, and strategic decision-making. Gaps between expected and actual coverage can trigger recommendations or highlight areas for investment.

Core concepts

Score vs level: A numeric score (0.0–1.0) is translated into a categorical coverage level.
Gap analysis: Automatically compares actual level to target from CoverageExpectation.
Update frequency: Typically updated as documents are added or analysed.

Example implementation

{
  "id": "cstat-100",
  "orgUnit": "OU-Finance",
  "domain": "Capability",
  "coverageScore": 0.67,
  "coverageLevelAchieved": "Documented",
  "expectedCoverageLevel": "Analysed",
  "coverageGap": 1,
  "lastEvaluatedAt": "2025-07-02T09:00:00Z",
  "notes": "Good initial coverage, but process-level granularity missing"
}

Attributes

Property	Description	Example

Property	Description	Example
`id`	Unique identifier	`cstat-100`
`orgUnit`	Unit assessed	`OU-Finance`
`domain`	Domain assessed	`Capability`
`coverageScore`	Numeric coverage score (0–1)	`0.67`
`coverageLevelAchieved`	Derived level from score	`Documented`
`expectedCoverageLevel`	Desired level from `CoverageExpectation`	`Analysed`
`coverageGap`	Gap between expected and achieved (in level steps)	`1`
`lastEvaluatedAt`	Timestamp when last evaluated	`2025-07-02T09:00:00Z`
`notes`	Optional commentary on current status	`Process-level granularity missing`

Enumerations

`coverageLevelAchieved`, `expectedCoverageLevel`

Value	Meaning

Value	Meaning
`None`	No coverage evident in documentation
`Minimal`	Sparse references or placeholders
`Documented`	Structured data exists, but analysis is shallow
`Analysed`	Relationships and impacts are assessed
`Governed`	The domain is actively monitored or controlled
`Optimised`	Used systematically in performance improvement or innovation

Schema
coverageStatus.schema.json on GitHub