Reference

Canonical specifications for matic — the schemas, configs, frontmatter, layouts, enums, commands, and vocabulary that define how an org is shaped on disk and operated at runtime. Use this section to look up exact field names, file locations, and status values rather than to learn concepts. If you're new to matic, start with Core Concepts and circle back here when you need precise contracts.

CLI Commands

Command-by-command reference for the matic CLI, grouped by domain — org setup, agents and actors, work lifecycle, scheduling, governance, knowledge, and infrastructure.

Configuration

YAML files under .matic/ — config.yaml, agent-runtimes.yaml, channels.yaml, plugins.yaml, plus budgets, risk profiles, and notification policy.

Enums & Statuses

Every enumerated value matic recognises — agent, team, and project status; work item and run lifecycles; signal types; collaboration modes; scope and risk class.

Frontmatter

Required and optional frontmatter for each markdown primitive — agent profiles, archetypes, work item specs, tasks, routines, policies, and decision records.

Glossary

Definitions of every term used across matic, organised by domain — venture primitives, actor model, work model, scheduling, governance, knowledge and memory, and infrastructure.

Org Filesystem Layout

The canonical directory tree produced by matic init — org root, agents/, projects/, teams/, archetypes/, and the .matic/ control plane, plus naming conventions.

Schemas

JSON-schema-backed contracts for the runtime objects exchanged between subsystems — signals and payloads, work items, runs, decisions, probes, context envelopes, and agent messages.