01 · UNDERSTAND
Map the site, content model, deployment boundary, and the exact operations the Operator may prepare.
PRODUCT · WEBSITE OPERATOR
A controlled path from request to production.
The Website Operator is in development. It is being designed to understand one authorized site, prepare changes as drafts, and stop at a named-human approval gate before production.
Site-specific by default
Permissions belong to the site and task in scope. Access to one site does not imply access to another, and future systems are not included automatically. Each integration requires its own boundary, credentials, permitted actions, and approval path.
- Explicitly scoped site permissions
- Drafts instead of silent edits
- Staging before production
- A named human approves production
- Logged actions and decisions
- Rollback designed into the change path
Operator character, state: idleIDLE
CONCEPT DEMO · SEQUENCE IS ILLUSTRATIVE
The operating sequence
02 · PREPARE
Turn an authorized request into a reviewable draft. The working change remains separate from production.
03 · PREVIEW
Build the proposed change in a staged environment so the named approver can inspect behavior and content.
04 · APPROVE
Wait for an explicit decision from the person assigned to the production gate. Silence is not approval.
05 · APPLY + RECORD
Apply only the approved change, record what happened, and preserve the information needed to reverse it.
What it does not mean
It does not mean uncontrolled autonomy, universal access, or a production-complete catalogue of integrations. The Operator prepares and coordinates work inside a defined lane; authority remains with the assigned human.