How the workflow works
Follow evidence from collection through Strategy, approval, execution, verification, impact, and rollback.
Evidence
Audits, site crawling, connected providers, and public checks produce site-scoped evidence. Evidence records what was observed, where it was observed, and which site it belongs to.
Strategy
The Strategy Agent is the only authority that creates customer-facing tasks. It evaluates evidence, chooses a supported action, and keeps the task scope aligned with the affected URLs.
Approval
Publishing and other material changes wait for approval unless an eligible site autonomy policy explicitly permits the task. Approval does not bypass quality, tenant, budget, or provider checks.
Execution
The worker claims the task and sends supported writes through the shared publishing layer. Publishing captures a pre-change snapshot when the adapter supports mutation.
Public verification
After execution, Orbitr checks the public result. A worker status of completed is not sufficient evidence that the customer-visible site changed correctly.
Impact and rating
Verification and later measurements can be correlated to the task. Measurements require an exact site and observation identity. You can also rate the completed task in the app.
Rollback
Supported mutations retain an operation or snapshot identity. A rollback restores through the same controlled publishing path and is verified again.