Operator console / Evidence-backed workflow

Run optimization work with a clear approval trail.

Create a seller-authorized run, attach compact scan evidence, and move one verified change through review without giving an Agent permission to edit a storefront.

Restart-safe stateHuman approvalPublic target onlyCompact evidenceREST / MCP

Start a run

Create optimization context

The server keeps only bounded run metadata.

Saved context

Recent runs

No runs loaded.Refresh to read the bounded run list.

Selected run

Choose a run

Waiting

Select a run to inspect its state.Transitions are validated by the server.

One transition

Advance selected run

Server enforced

Create or select a run first.

Workflow boundary

Evidence before promotion.

The console follows the same state machine used by REST, OpenAPI, and MCP. Review-to-verify and promote-to-completed require explicit approval from the server, so a browser action cannot bypass the workflow boundary.

Use public pages and seller-declared authorization only.
Attach a compact scan or proposal reference before baseline, plan, and verify.
Keep one change and one rescan in the same run.
Export the run when handing work to another Agent or operator.

Questions

Agent runtime FAQ

Does the console edit my store?

No. It records an optimization workflow and approvals. You apply changes in your own storefront editor.

Why is approval required?

Verification and promotion are consequential workflow gates, so approval is enforced by the server rather than trusted from the browser.

Can another Agent use the same run?

Yes. The same compact run state is available through REST, OpenAPI, and MCP within the current test-environment authorization boundary.