Page actions
job / candidate
SRE and incident command
Proposal-only reusable job package for Stan to prepare bounded reliability, security, continuity, and incident-command work while preserving human approval for destructive remediation, purchasing, credential changes, legal filings, and public deployment.
Record status
- Record ID
- job:stan:sre-and-incident-command
- Parent lifecycle
- candidate
- Page lane
- catalog overview
- Lane lifecycle
- candidate
- Owner
- Stan
- Owner role
- Chief Security and Engineering Officer
- Owner status
- VERIFIED
- Qualification result
- NOT RUN · held for evidence and human review
Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.
Purpose and audience
Proposal-only reusable job package for Stan to prepare bounded reliability, security, continuity, and incident-command work while preserving human approval for destructive remediation, purchasing, credential changes, legal filings, and public deployment.
- Stan
- Chief Security and Engineering Officer
- engineering operators
- incident commanders
- security reviewers
- human approvers
Required or proposed record references
The list defines expected record classes. It does not assert that any instance exists.
- job:stan-sre-and-incident-command
- incident record with canonical ID, severity, timeline, owner, status, and source provenance
- current-work packet
- source-labelled notes and evidence references
- incident todo/deadline records
- approval record for gated actions
- agent log and receipt ledger entry
- continuity or recovery plan record
- post-incident review record
Route contract
The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.
Held source-proposed extensions
- /docs/jobs/stan-sre-and-incident-command/overview
- /docs/jobs/stan-sre-and-incident-command/incident-runbook
- /docs/jobs/stan-sre-and-incident-command/authority-and-approval
- /docs/jobs/stan-sre-and-incident-command/incident-command/
- /docs/jobs/stan-sre-and-incident-command/security-and-architecture/
- /docs/jobs/stan-sre-and-incident-command/continuity-and-recovery/
- /docs/jobs/stan-sre-and-incident-command/evidence-and-receipts/
- /docs/jobs/stan-sre-and-incident-command/authority-gates/
- /docs/jobs/stan-sre-and-incident-command/failure-states/
These extension paths are not generated by this record and must not be treated as resolving routes.
Public claim boundary
Allowed items below are source-lane proposals, not verified current-state claims.
Candidate claims allowed after source review
- This is a proposal-only reusable job package for SRE and incident-command work.
- The package organizes source-bound observations, deadlines, workbacks, evidence, approvals, receipts, and continuity follow-up.
- The listed Guth routes are native prototype or indexed surfaces with the capabilities stated in the supplied route contract.
- The listed instruments are exact-slug verified instruments and are limited to the described bounded uses.
- The package preserves explicit human-review boundaries for gated actions.
Claims held
- Deployment, production readiness, provider connection, live availability, or active monitoring.
- Database authority, Supabase writes, Cloudflare changes, credential access, customer indexing, or protected-storage guarantees.
- Incident resolution, containment success, security qualification, compliance, legal filing, or customer notification.
- Any claim that an agent executed destructive remediation, changed credentials, purchased services, sent external communications, or deployed publicly.
- Authenticity, completeness, or legal admissibility of supplied evidence based only on hashes or receipts.
- Any unsupported claim about current outage scope, customer impact, SLA performance, or business metrics.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
agents/index.html#stansource_record:job:stan:sre-and-incident-commandsource_record.owner_agent=Stansource_record.owner_role=Chief Security and Engineering Officersource_record.existing_tools=Assurance preflight; Terminal courier; Receipt ledger; Source-bound recallsource_record.existing_guides=Security field guides; Supabase field guide; Cloudflare operations; Current-work packetssource_record.principal_gates=Destructive remediation; Money or purchasing; Credential changes; Public deployment; Legal filingsource_record.never_rules=Manufacture Antonio's authority; Treat confidence as permission; Convert a proposal into an effectobserved_native_contract.recordsobserved_native_contract.deadlinesobserved_native_contract.pointguardobserved_native_contract.web_boundaryapp_routes:/app/pointguard/app_routes:/app/notebook/approvals/app_routes:/app/notebook/agent-logs/app_routes:/app/notebook/to-dos/app_routes:/app/notebook/messages/app_routes:/app/business/home/app_routes:/app/business/vault/job:stan:sre-and-incident-commandObserved native contract: project_and_field_guide_collectionsObserved native contract: deadlinesObserved native contract: recordsObserved native contract: pointguardObserved native contract: web_boundary/app/pointguard//app/notebook/approvals//app/notebook/agent-logs//app/notebook/field-guides//app/notebook/projects//app/notebook/search/App route: /app/pointguard/App route: /app/notebook/approvals/App route: /app/notebook/agent-logs/App route: /app/notebook/search/App route: /app/business/home/