Coordinate workflows, schedules and assignments

An assignment defines who owns or reviews a member scope. A workflow definition connects activities, assignments and evidence requirements. An occurrence is a particular run with its own identity and activity state. A schedule defines when a separately authorized target runs.

Bind the exact versions and authority

1. Assign work through execute_v2_application_assignment. Verify the scoped principals, member selection and effective window. Read the saved digest before publishing the assignment version.
2. Define a workflow using the exact published assignment and rule identities. Check the selected activities, dependencies and evidence requirements. Saving and publishing a definition are separate from starting an occurrence.
3. Inspect an occurrence by its exact ID after an authorized start. In the sample, prepare is Ready, review is Blocked, and OccurrenceStarted records the start.
4. Schedule an authorized program through execute_v2_application_schedule. Pin the target publication, bindings, recurrence and schedule-bound delegation. After publishing the schedule, verify its recurrence and future first due time. Inspect the resulting occurrence when it runs.

On a stale revision, changed target or missing delegation, reread the current state and recheck authority before attempting publication. For a failed occurrence, inspect its activity state and task evidence before deciding how to recover.

Workflow prompt templates · Workflow and schedule tools