The public website calls a unit of work a step. The implementation uses the canonical Loop runtime described here and in the repository.
Complete behavior of a discrete cognitive or act step Loop node
A discrete cognitive or act step Loop node is an independently governed instance of the Loop runtime responsible for one clearly defined cognitive step or action. A cognitive step might interpret information, identify a missing requirement, compare alternatives, or evaluate a result. An action might inspect a directory, build software, execute a test, create an artifact, or send an authorized email.
Each discrete cognitive or act step Loop node receives the context, instructions, skills, plugins, tools, and working files relevant to its assignment. Essential information can be supplied directly, while additional information can remain in centralized storage behind authorized, versioned references. It does not automatically need the entire task history or every available tool.
A separately initialized harness process, such as OpenCode, Pi, Codex, or a custom implementation, can perform the assignment. When explicitly permitted, another harness can attempt the same assignment after a failure. The assignment's contracts, permissions, history, and remaining authority persist across those attempts.
Discrete describes the scope of the assignment, not a restriction to one attempt, one model call, or one output. A discrete cognitive or act step Loop node can examine whether an observation matches its expectations, identify a problem, repair or change its approach, and repeat until its declared completion conditions are satisfied.
Alternatively, a discrete cognitive or act step Loop node can publish an initial candidate output and continue working while its continuation conditions and authority permit. It can produce additional alternatives over time, including alternatives that are better, worse, or useful under different circumstances. Consumers must identify exactly which output they used. Publishing an output does not necessarily mean that the producing assignment has finished.
For externally consequential actions, continued operation does not authorize repeated effects. For example, generating alternative email drafts can continue, but sending an email requires its own authorization and protection against duplicate delivery.
