# Organizing projects, playbooks and automation

Availability: Planned API.
Last reviewed: 2026-08-28.

Organize approved intent into plans, tasks, playbooks and explicit recurring policies. The planned outcome coordinates work without confusing a saved plan with execution.

## Define the work

Provide the account/workspace, objective, source opportunity or campaign, owners, task dependencies and approval points. A promoted opportunity can create draft planning artifacts; it does not launch the underlying business work.

Playbooks should be versioned so each run records the instructions and scope it used.

## Plan time honestly

Calendars and occurrences can represent tentative work. They are not bookings with an operator, provider or customer until the relevant authority accepts them.

For example, a weekly research plan can remain saved while recurrence is disabled and no provider work has been authorized.

## Make automation explicit

An enabled-looking response is not proof that a scheduler is running. Recurring work needs a defined trigger, ownership, limits, permissions, failure policy and, where paid, explicit financial authority. Changes must not silently widen historical scope.

## Read the outcome

Retain plan/run identity, progress, approvals, result references and honest partial or blocked states. Cross-account agency delivery preserves delegated access rather than sharing ownership or funds.

## Availability

Business APIs are planned. Generic worker dispatch, infrastructure scale-out, reset and command-palette internals are not public automation procedures.