Source: https://guthlabs.ai/docs/jobs/stan-sre-and-incident-command/tools/ job / candidate # SRE and incident command — tools The distinct tools record for SRE and incident command. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:stan:sre-and-incident-command **Parent lifecycle**: candidate **Page lane**: package **Lane lifecycle**: proposed **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. ## Authoritative package lane tools and interfaces ### Canonical tools-page assignments - **Assurance preflight** (skill · required) — Run a bounded readiness and risk check before proposing operational work; it does not authorize effects. - **Terminal courier** (interface · required) — Prepare or inspect local engineering commands and outputs while execution and external effects remain bounded. - **Receipt ledger** (record · required) — Preserve decisions, proposals, approvals, holds, and failure receipts for auditability. - **Source-bound recall** (skill · required) — Keep incident reasoning tied to supplied records, locators, provenance, and revisions. - **Security field guides** (guide · required) — Provide source-backed security procedures and prerequisites without expanding authority. - **Supabase field guide** (guide · required) — Guide database-related review while database authority, provider connection, and production writes remain held. - **Cloudflare operations** (guide · required) — Guide edge and continuity review while provider changes and public deployment remain held. - **Current-work packets** (guide · required) — Structure focused work, dependencies, ownership, deadlines, and handoffs. - **PointGuard** (interface · required) — Provide persistent cross-app context while Notebook and specialist surfaces remain canonical owners. - **Notebook Approvals** (interface · required) — Collect human decisions and preserve held or approved proposal states. - **Notebook Agent Logs** (interface · required) — Expose agent work, authority boundaries, receipts, and current state. Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved. ## Authoritative lane instrument assignments ### Canonical tools-page assignments [checksum-verifierrequired · Verify recorded evidence checksums when a checksum and corresponding content are supplied; preserve the result as a receipt.]()[sha-256-hash-function-demorequired · Demonstrate or independently record SHA-256 values for supplied local evidence; never treat a hash as proof of authenticity or production custody.]()[uptime-sla-availability-calculatoroptional · Calculate educational availability or downtime targets from explicitly supplied periods; label results as estimates and not live metrics.]()[http-status-code-header-lookupoptional · Interpret supplied HTTP status codes or headers during review; it does not perform a live provider check.]() An instrument listed only for another lane does not become a tools-page assignment. ## Use boundary - Confidence may be mistaken for authorization; all effects require the applicable human gate. - A plausible incident narrative may exceed the supplied evidence; preserve observation and inference separately. - Destructive remediation can worsen outages or destroy evidence; require reversibility, rollback, and approval. - Credential changes and provider operations can create security or continuity risk; keep them held. - Database, customer, publication, and production claims may be inferred from named routes; native surfaces do not prove connected features. - Hashes and receipts establish recorded comparison, not authenticity, ownership, or legal admissibility. - Educational availability calculations can be mistaken for live SLA measurements. - Incident communications can disclose sensitive details or make unsupported public claims; use least disclosure and human review. - Deadline pressure can cause unsafe shortcuts; overdue work must escalate or remain held rather than silently execute. - Incomplete provenance, conflicting revisions, or inaccessible evidence can produce false closure. - Agent ownership by Stan does not manufacture Antonio's authority or authorize actions outside the stated gates. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `agents/index.html#stan` - `source_record:job:stan:sre-and-incident-command` - `source_record.owner_agent=Stan` - `source_record.owner_role=Chief Security and Engineering Officer` - `source_record.existing_tools=Assurance preflight; Terminal courier; Receipt ledger; Source-bound recall` - `source_record.existing_guides=Security field guides; Supabase field guide; Cloudflare operations; Current-work packets` - `source_record.principal_gates=Destructive remediation; Money or purchasing; Credential changes; Public deployment; Legal filing` - `source_record.never_rules=Manufacture Antonio's authority; Treat confidence as permission; Convert a proposal into an effect` - `observed_native_contract.records` - `observed_native_contract.deadlines` - `observed_native_contract.pointguard` - `observed_native_contract.web_boundary` - `app_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/`