Seneschal / task coordination

Watch a task wait and continue

What the parts mean: carrier = task result · rear tokens = finished prerequisites · barrier = selected access policy · platform = review.

Fig 03 / SeneschalTasks wait, then pass their results

Select a part to see what it does.First prerequisite is running

Example: completed prerequisites and the selected access policy let a task result reach review. These controls do not run agents.

Step through the example

A labelled handoff

The bright ticket travels with its result. Completed prerequisite output becomes context for a dependent session.

.controls,.choices{display:none}

The four mechanisms

Dependencies: the rear tokens represent prerequisite results. A downstream task waits for all selected dependencies.
Access: the lifting barrier represents the selected access policy. Plan is read-only; Build asks by default. Policies and integrations vary.
Handoff: the carrier keeps a completed result attached to its dependent session as labelled context.
Review: a configured supervisor owns final acceptance; a visible correction can request another bounded pass.

Illustrative scenarios

All ready lets the carrier reach review. Dependency waits leaves the second signal closed. Access waits holds the carrier at the chosen boundary. Correction pass returns the carrier once. These examples operate no real agents.