Workflow

Workflow is how matic turns inbound events into coordinated, governed, delivered work. Every piece of work in an org traces the same path — signal to activation to plan to work item to run to delivery — and every step is a file on disk, a git commit, and an auditable record. This section walks each stage of that loop and the scheduling primitives that drive it.

Signals

The atomic input unit—every channel message, webhook, routine, metric crossing, and agent-to-agent message enters as a signal.

Activation

Where a signal is interpreted, triaged, and activated into work or notifications—the gate between conversation and execution.

Planning

How an activation becomes an executable work plan: task decomposition, budget estimation, staffing, and work contracts.

Work Items

The atomic, agent-executable unit produced by planning—specs, context, collab modes, and the work pile.

Runs

A single execution instance of a work item: run modes, context budget, run records, and recovery protocol.

Delivery

Validating artifacts against work contracts, surfacing previews for review, and publishing final delivery actions.

Routines

Scheduled and event-driven emitters that feed the signal pipeline—cron, eval, callbacks, and the observe-hypothesize-evolve loop.