Matrix · 04 of 19 · Workload shapes

Any agent workload is one of six shapes, built from two kinds of thing

The platform does not care what the agent does or which framework it uses. A definition is durable and reviewed. A run is a disposable instance of it. A long-running service agent is just the durable half, deployed the way any application is.

Any agent workload is one of six shapes, built from two kinds of thing Matrix of six agent workload shapes, task, session, service, scheduled, event and team, showing for each the trigger, lifetime, the durable git part and the ephemeral AgentRun claim, where a service agent has no ephemeral part because it is an ordinary deployed application. SHAPETRIGGERLIFETIMEDURABLE (GIT)EPHEMERAL (CLAIM)EXAMPLESTask agentkind: taskhuman, API, agentto completionAgent definitionAgentRuncoding, triageSession agentkind: sessionhuman in Towerbounded TTLAgent definitionAgentRun (interactive)pairing, reviewService agentkind: servicealways onuntil removedAgent + Rolloutnone: not a runchat bot, HolmesScheduled agentkind: scheduledcron in definitionper runAgent + scheduleAgentRun per ticknightly reviewEvent agentkind: eventalert or webhookper eventAgent + triggerAgentRun per eventincident triageAgent teamkind: teama parent runinside parentAgent definitionschild AgentRunsplanner + workersLEGENDDurable, in gitEphemeral claimNot a runNarrowing enforced

Principle honored

Definition durable, run ephemeral. Service agents reuse the existing application path, so nothing new is invented for them.

What changes

  • Today: an AgentDefinition YAML in git, schema-validated in CI.
  • Later: an Agent XRD so Tower generates a New Agent form from it, like every other XRD.
  • Triggers are part of the definition; each firing becomes an AgentRun.

Verify live

Run one agent of each shape, and one that should be refused (a delegated agent triggered by cron, which Clearance denies). The refusal is the more useful test.

Hangar · Autopilot