Practical guide
Overall starts from an expected Outcome, coordinates Work, and retains a reviewed Result. Automations add rhythm; they do not replace the responsible person or their decision.
The Work model
Outcome. The expected real-world state. A Goal can orient several Outcomes, but remains optional.
Work. A coordinated intervention with its own completion definition. It can be one-off and contribute to several Outcomes without duplication.
Result. The immutable, reviewed account of what was produced. Files, messages, and measurements stay in the Result or its evidence; acceptance never automatically achieves an Outcome.
Target model — links between one Work and several Outcomes are not yet available.
The path available today
One-time, daily, and weekly schedules use an explicit time zone. The deterministic review of currently open Work prepares a candidate Result with attributable evidence, without provider writes or external effects.
A separate staging-only path requires a specific, expiring admission for the exact Owner, Workspace, Automation revision, and request. It can prepare a candidate; it neither accepts the Result nor creates external effects.
An organization Owner opens Automations in their Workspace, creates a named schedule, then activates it. This delegation persists after sign-out; active, paused, and archived Automations remain visible. The responsible person can pause, resume, or archive them. The context note describes the review; it is not an arbitrary executable instruction.
Coming next: an event interface, external effects, learned rationales, and an autonomy policy editor. An event can establish eligibility, never authority. The future shared-Outcome model will assess a Result's effect on each Outcome.
Use the schedule
These capabilities are described by the implementation; their availability depends on the environment.
From the current Workspace, start with the recurring need to review open work.
Choose once, daily, or weekly. This grants no new authority.
At the due occurrence, Overall examines up to 25 currently open Work items and prepares a candidate Result, or records that there was no action.
The accountable person explicitly accepts, requests revision, or rejects it; acceptance is never implicit.
Missed occurrences remain ordered. Each batch prepares at most one, the oldest, for each Automation; it reviews current state when it runs, without reconstructing the past. A recoverable failure stays pending. A blocked delegation requires an explicit pause and resume.
The separately admitted agent preparation is never retried automatically after ambiguous dispatch. Explicit recovery is required; it authorizes neither new spend nor a new delegation.
No. In the future shared-Outcome model, the Result effect on each linked Outcome is assessed explicitly. Acceptance never automatically achieves an Outcome.