Execution and event capture have separate responsibilities.
00 / FROM REQUEST TO RESULT
From a request
to a result you can trace.
A skill supplies the workflow. Typed actions carry the request to the engine, where scope, tools and verification govern the work.
Scroll to follow the story. Open a subject to inspect its role.
01 / CHECK THE SCOPE
The right project.
The current contract.
Before an operation runs, the selected sources, current Plan, granted access and required tools must agree. A question and a request to change the Plan follow different paths.
Explore the connected subjects. Drag the scene to see its depth.
02 / FOLLOW THE OPERATION
Selected tools.
Attributed results.
A tool route is specific to an operation. Primary and fallback choices, worker bounds and result readers stay visible through the work.
Explore the connected subjects. Drag the scene to see its depth.
03 / EVENTS AND HOOKS
Events leave a trail.
They do not grant authority.
Supported host events can feed attributed capture when the user enables the hook stages. Capturing an event does not execute a Plan or prove task completion.
Explore the connected subjects. Drag the scene to see its depth.
04 / KEEP THE TRAIL
A result with support.
Context for what comes next.
Receipts, procedural lessons and project context answer different questions. Preserve their origins, inspect their limits and continue from the actual recorded boundary.
Explore the connected subjects. Drag the scene to see its depth.
HOW IT WORKS
Follow the work. Keep the evidence.
Actual work follows the selected project, its current Plan and the owning operation contracts. This illustration explains those relationships; it does not submit work.
Find your workflow ↗