First Org

An org is the root of everything in matic: a git repository that contains your charter, agents, projects, policies, and runtime state. This section covers the work required to stand up that org from scratch, from creating the repository and defining its governing contract to understanding its directory layout and execution model. It also introduces the daemon, runtime configuration, and multi-org patterns that keep a running org operational over time.

Init Org Repo

Init Org Repo — Create a new org repository with matic orgs init, scaffolding the canonical directory structure, spawning Auto Matic, and transitioning the org to active state.

Write Your Charter

Write Your Charter — Define the org's governing contract: scope, strategic intent, admissibility criteria, and constraints that every agent and project must align with.

Org Directory Structure

Org Directory Structure — Understand the filesystem layout that matic init creates: agents/, projects/, teams/, archetypes/, .matic/, and where each primitive lives.

Org Scopes & Handles

Org Scopes & Handles — Learn how matic's four hierarchical scopes (org, project, team, agent) control visibility and inheritance, and how kebab-case handles identify every entity.

Configure Daemon

Configure Daemon — Start and configure the daemon, the persistent background process that monitors channels, fires routines, enforces budgets, and coordinates all continuous operations.

Configure Agent Runtimes

Configure Agent Runtimes — Connect agent runtimes like Claude Code, Codex CLI, or Gemini CLI through .matic/agent-runtimes.yaml so agents have execution environments for their work.

Multi-Org Setup

Multi-Org Setup — Run multiple orgs on a single machine with independent daemons, shared credentials, and org-scoped CLI commands.