Charter

A charter is the governing contract of an org — it defines scope, strategic intent, admissibility criteria, and constraints, and serves as the authority against which every project proposal and agent spawn decision is validated. It is not a mission statement; it is an operational document that matic enforces at runtime. Every org has exactly one charter, and nothing enters the org — no project, no agent — without passing through it.

Overview

What a charter is, how it fits into the org lifecycle, and how matic uses it to gate decisions at runtime.

Charter Fields

A reference for every field in charter.md: scope, strategic intent, admissibility criteria, constraints, max_agents, permitted_archetypes, and excluded_domains.

Charter Validation

How matic validates project proposals and spawn requests against the charter — what checks run, what a failure produces, and how human overrides are recorded.

Admissibility Criteria

The specific standards a project must satisfy to transition from proposed to chartered — how to write them, how they are evaluated, and common patterns.

Amendment Flow

How to change a charter: the PR-based amendment process, why human approval is required, and how in-flight work is affected.

Charter and Agent Onboarding

Why Charter read is the mandatory first step of agent onboarding and what a new agent must demonstrate before it can transition to available.