Four parts. One continuous task thread.
Each layer has a clear job. Together they preserve what the user asked for, what the system did, and why the result can be trusted.
Workspace
A desktop surface for active threads, checkpoints, evidence, and handoffs.
Explore the workspace ↗ 02Task contracts
Outcome, acceptance criteria, authority, and limits become explicit before work begins.
Explore contracts ↗ 03Durable execution
The task survives interruptions, waiting periods, retries, and application restarts.
Explore execution ↗ 04Delivery and evidence
Results arrive with checks, sources, execution history, and unresolved questions attached.
Explore delivery ↗The work does not disappear when the session does.
A conventional assistant returns an answer. A fixed workflow repeats a known path. LibreTask maintains a task state that can be resumed, inspected, changed, and accepted over time.
- The contract remains authoritative when the plan changes.
- The execution history explains what happened and why.
- Human review happens inside the workflow, not after it.
- The final deliverable includes the proof required to accept it.