Infrastructure

Infrastructure commands manage the process boundaries that make matic operable as a running product: the long-lived daemon that routes signals and supervises work, the watchers that turn filesystem and channel events into routable input, and the extension surfaces (MCP servers, plugins) that attach external capabilities to a workspace. Use this section when you are bootstrapping a host, diagnosing a stalled runtime, or wiring matic into the surrounding tooling on an operator's machine.

daemon-start

Bring up the org daemon and run its bootstrap sequence so watchers, IPC, and supervised subsystems become ready to accept work.

daemon-status

Report the daemon's readiness, health, and supervision state for the current workspace.

daemon-stop

Signal an orderly shutdown of the daemon, draining in-flight work and releasing the process boundary.

mcp-server-attach

Register an external MCP server with the MCP manager so its tools become available to runtime adapters.

plugin-install

Load a plugin from its manifest into the installed-plugin registry under the isolation boundary.

watcher-list

Enumerate active channel, filesystem, and system-event watchers feeding the daemon's intake path.

workspace-init

Scaffold the filesystem topology for a new org or scope, including the .matic/ control plane and workspace layout.