Cloudflare operations — prerequisites

The distinct prerequisites record for Cloudflare operations. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:cloudflare-operations
Parent lifecycle: candidate
Page lane: plan
Lane lifecycle: proposed
Owner: Stan
Owner role: Not separately recorded
Owner status: Not separately recorded
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Field guides — documentation — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

Source record for field-guide:cloudflare-operations with canonical ID and source locator
Operational scope note identifying the requested Cloudflare-related task
Source-labelled evidence or file-reference records for supplied artefacts
Notebook to-dos for review, verification, and handoff deadlines
Approval record for any proposed decision or external effect
Receipt-backed handoff record owned by the responsible specialist app or agent
Agent log recording authority boundaries, current state, and unresolved failures

Intended operators and ownership

Stan
Security engineering
Architecture and implementation
SRE and incident command
Fleet operations
Receipt-backed handoffs

Being listed as an intended operator does not grant execution or publication authority.

Conditions that hold the guide before entry

Treating the name Cloudflare as proof of a connected provider feature or live account.
Applying credentials, changing DNS, routing, security policy, access rules, deployment settings, or production configuration without verified authority and human approval.
Confusing a local prototype or index route with a canonical provider, database, customer, or production system.
Using stale, conflicting, unsigned, or incomplete evidence as operational truth.
Exposing private operational notes, credentials, customer references, or protected assets through public documentation or search.
Creating hidden automation from recurrence, deadlines, approvals, or PointGuard context.
Losing provenance, source hashes, revisions, or receipt links during handoff.
Declaring incident resolution, security qualification, deployment success, or rollback success without supplied evidence.
Relying on inaccessible files, unlabelled screenshots, or doorway documentation URLs as evidence.
Failing to provide keyboard-accessible labels, readable status distinctions, clear error text, and non-color-only indications for Held or Needs review states.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

source_record:field-guide:cloudflare-operations
field-guide:cloudflare-operations
agents/index.html#stan
Observed native contract: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
/app/notebook/field-guides/
/app/notebook/notes/
/app/notebook/files/
/app/notebook/to-dos/
/app/notebook/approvals/
/app/notebook/agent-logs/
/app/pointguard/