Platform

The platform layer is the operational infrastructure that makes matic a delivered system rather than a set of abstractions. It provides user-facing surfaces (CLI, terminal chat, external messaging channels), a persistent coordination backbone (daemon), integration adapters for agent runtimes and git, and extension points for custom capabilities. Each component normalizes external interfaces into canonical internal contracts, enabling matic to operate as a single coherent runtime despite orchestrating across dozens of external tools and services.

Agent Runtimes

Agent Runtimes adapts external agentic AI systems — Claude Code, Codex CLI, Gemini CLI, and others — to a uniform execution interface so matic can coordinate work without locking you into any single runtime.

Channels

Channels normalizes inbound and outbound communication across Slack, Telegram, WhatsApp, Discord, email, webhooks, and the built-in terminal, converting platform-native events into a canonical signal envelope.

CLI

The CLI is the matic command surface for operators and power users, with read-only commands that work directly against the filesystem and execution commands that route through the daemon via IPC.

Daemon

The Daemon is a persistent background process that coordinates all active org operations: signal ingestion, routine scheduling, channel monitoring, status propagation, and budget window management.

Git Integration

Git Integration manages worktrees, branch conventions, commit guardrails, and PR workflows so that agent contributions to shared surfaces follow the same review process as human code.

MCP

MCP is a dual-role Model Context Protocol integration — matic exposes itself as an MCP server for external consumers and manages external MCP servers as scoped tool providers for agents.

Plugins

Plugins are an extension mechanism for adding custom CLI commands, agent runtimes, channels, skills, tools, routines, policies, and org templates, with subprocess isolation for third-party code.