Configuration

Configuration in matic is filesystem-first: every operational lever lives as a YAML file in the org's git repository, scoped from the org root down through projects, teams, and agents. The Daemon reads these files on startup and on change, so configuration is auditable, diffable, and reviewable like code. This section is the reference for every configuration surface — runtime credentials, channel adapters, plugins, budgets, risk classification, and notification routing.

config.yaml

Top-level org configuration in .matic/config.yaml — org identity, defaults, and scope-wide settings.

agent-runtimes.yaml

Agent Runtime definitions and credentials in .matic/agent-runtimes.yaml — assign Claude Code, Codex CLI, Gemini CLI, or other adapter-backed runtimes per agent, per team, or org-wide.

channels.yaml

Org-level channel adapter configuration in .matic/channels.yaml — Slack, email, SMS, terminal, and other inbound/outbound surfaces, plus per-agent subscriptions.

plugins.yaml

Installed plugin manifests in .matic/plugins.yaml — first-party (github, notion, linear, scheduled-reporting, competitive-monitor) and third-party extensions to CLI, runtimes, channels, skills, tools, and routines.

Budgets

Cascading compute allowances (org > project > team > agent) defined per scope with daily, weekly, or monthly windows — the inputs the Budget Gate, Meter, and Bandwidth Probes evaluate against.

Risk Profiles

Risk classification config for Work Items, Tasks, Milestones, and Projects — failure impact, likelihood, required Guardrails, HITL checkpoint placement, and Dry Run requirements that feed the Risk Registry.

Notification Policy

Event-to-recipient routing in .matic/policies/notification-policy.yaml — which events (budget warnings, HITL requests, run failures) reach which roles or handles, via which channels, with what escalation timing.