One loop from intent to acceptance.
Each stage creates an execution event and leaves enough context for the next stage to continue.
Frame
Resolve intent, output, constraints and acceptance criteria before spending resources.
Plan
Retrieve capabilities, enforce policy and build an explainable task graph.
Execute
Invoke idempotent activities, normalize results and evaluate progress.
Checkpoint
Pause durably for review, scope changes, budget decisions or takeover.
Deliver
Assemble the outcome with evidence, unresolved issues and acceptance checks.
Time is part of the workflow.
LibreTask uses a durable execution runtime rather than building crash recovery, replay and idempotency from scratch.
Workflow for the task. Activities for the tools.
The workflow persists its position while activities call search, PDF extraction, model summaries and local notes. A human signal can arrive seconds or days later.
Crash recovery
The thread resumes from durable history after an application or worker failure.
Exact retries
Capability activities use a key built from task, plan node and attempt.
Long waits
Human checkpoints suspend the workflow without keeping a live process open.
Budget checks
Deadline and cost limits are checked before resource use and at defined thresholds.
Correction is a visible state.
A failed call does not trigger an invisible loop. The system changes state, records the reason and chooses a bounded recovery path.
| Signal | System response |
|---|---|
| Capability unavailable | Retry within policy, switch to an approved alternative, then ask for a decision. |
| Progress is off track | Split the task, change capabilities or request missing information through an explicit correction event. |
| Budget exhausted | Pause, generate a budget report and ask whether to increase scope or adjust the contract. |
| Acceptance is ambiguous | Return to clarification before further execution or delivery. |
Continue, pause or take the wheel.
Intervention is a first-class product action. The system knows what changed and what should happen next.
Pause
Freeze the thread at a safe boundary without losing progress or context.
Revise
Change the contract through versioning, not hidden prompt drift.
Roll back
Return to a recorded checkpoint when a correction path is no longer safe.
Take over
Lead the task yourself while preserving its evidence and resumable state.