Orbitr field guide
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 a queued task and sends supported writes through the shared publishing layer. Publishing captures a pre-change snapshot when the adapter supports both mutation and restoration.
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
Verification and later measurements are different records. Verification checks whether the expected public change is present. Longer-window impact requires a correctly linked provider plus an exact site, task, and observation identity. Orbitr reports impact as unavailable when those observations do not exist; it does not infer a result from task completion.
Rollback
Supported mutations can retain an operation or snapshot identity. When rollback is available, it restores through the controlled publishing path and the public result must be checked again. Not every adapter or task has a reversible operation.