Frontmatter

Every matic primitive lives as a markdown file whose YAML frontmatter is the machine-readable contract the runtime parses, validates, and acts on. This section documents the frontmatter schema for each markdown primitive — the field names, required vs. optional keys, enumerated values, and cross-references that wire primitives together. Use these pages when authoring or auditing files under an org's filesystem, or when writing tools that read and write them.

Agent Profile

Frontmatter for an agent's profile file — identity, archetype binding, runtime selection, permissions, team memberships, and lifecycle status. Read more

Archetype

Frontmatter for archetype definitions — versioned role templates that agents instantiate, with skills, tools, policies, and default runtime. Read more

Decision Record

Frontmatter for Decision files — scope, status, options, chosen option, stakeholders, and the boolean flags that drive machine-readable decision state. Read more

Policy

Frontmatter for policy files — scope (org, team, project), enforcement mode, applicable archetypes or actions, and review cadence. Read more

Routine

Frontmatter for routine files — cron or event schedule, owner, target handle, and the trigger conditions that activate the routine. Read more

Task

Frontmatter for Task files — title, acceptance criteria, context references, baselines at risk, skill tags, and outcome links. Read more

Work Item Spec

Frontmatter for Work Items — the embedded Work Contract, pile-ordering fields, HITL checkpoints, assigned actors, and run linkage. Read more