Orbitr field guide
Strategy and tasks
Understand who can create tasks, what approval means, and how Orbitr proves task output.
Strategy is the task authority
Auditors and specialist agents emit evidence and recommendations. Only the Strategy Agent creates a customer-facing task. This prevents multiple agents from creating conflicting work from the same finding.
Task states
Typical task states include:
- awaiting approval: ready for customer review
- pending: scheduled for future execution
- queued: approved and waiting for a worker
- in progress: execution is underway
- cancelling: a safe stop was requested during execution
- completed: execution finished
- failed: execution did not finish successfully
- cancelled: the task was rejected or cancelled
- paused: execution is intentionally paused
The task detail and timeline are the source of truth. A completed state records worker completion, not proof of the customer-visible result.
Review before approval
Confirm that the title, description, affected count, URLs, and proposed action agree. Reject a task if its evidence belongs to a different site, is stale, or does not support the proposed scope.
Verification after execution
For a publishing task, inspect the persisted result and public URL. Do not treat a completion badge as proof that the published output is correct.
Rollback
When a supported publishing operation has a retained snapshot or provider operation, Orbitr can expose a rollback operation. Rollback is a new controlled operation and should be publicly verified. Not every completed task is reversible.