Charters & Matters

What it is

The strategic layer above missions. A Charter is a long-running initiative — a Vision with acceptance criteria and excluded scope. A Matter is a strategic epic under a Charter that groups related missions.

Operator surface

Read-mostly from MCP:

• charter_get — Vision + acceptance criteria.
• matter_get — epic detail with its parent Charter and linked missions.
• matter_progress — total / completed / failed missions + a health ratio.
• matter_register / matter_list — register and list epics.

The dashboard exposes a strategy / roadmap view, and StrategyController serves the read APIs.

How it works

CharterRecord owns a collection of MatterRecords (ordered via ExecutionOrder / SortOrder), and missions reference their MatterId. Charters also carry integration-branch and affected-repository metadata so a whole initiative can land on a target branch. The MatterPipelineService and MatterVerificationService drive epics forward and verify their acceptance criteria, while StrategyRepository is the read/write data accessor. Charters and matters live in the tenant database and are managed by tenant admins.