Platform Overview
The platform is the control plane for Agirunner.
It owns the public surfaces that define, launch, route, observe, and govern work:
- the dashboard
- the platform API
- workflow and task records
- playbooks, workspaces, roles, skills, and tools
- community catalog import and provenance for shared playbooks, specialists, and skills
- provider configuration and integration state
- operator-visible logs, artifacts, approvals, and settings
If you think of Agirunner as “the system that decides what should happen next,” you are mostly thinking about the platform.
What The Platform Does
Section titled “What The Platform Does”At a high level, the platform turns an authored process and a launch request into explicit execution contracts.
That means it is responsible for:
- creating workflows and work items
- activating the orchestrator when work changes
- importing selected community playbooks from agirunner-playbooks and materializing tenant-local copies
- resolving model, role, tool, and environment policy
- exposing logs, artifacts, and review surfaces back to operators
- deciding what the runtime is allowed and expected to do
The platform does not just store records. It is the system that transforms playbooks, roles, and current workflow state into the contracts the runtime will later execute.
What It Does Not Do
Section titled “What It Does Not Do”The platform does not execute the task loop itself. That work belongs to the runtime.
The platform decides:
- what should happen
- who should do it
- what contract applies
The runtime then:
- claims the task
- prepares execution
- runs the loop
- reports the result
Why The Platform Is A Product Surface
Section titled “Why The Platform Is A Product Surface”The platform is not just a backend for the dashboard. It is the durable, operator-facing system of record for workflows, approvals, work items, artifacts, policies, and integrations. The dashboard and API are two ways into the same control plane, not two separate products.