Source: https://guthlabs.ai/docs/jobs/stan-sre-and-incident-command/qualification/ job / candidate # SRE and incident command — qualification The distinct qualification 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**: qualification **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. ## Qualification status **Result**: NOT RUN **Disposition**: HELD **Reviewer**: Not recorded **Receipt**: Not recorded This page defines proposed acceptance criteria for the qualification lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect. ### Lane-specific instrument aids [uptime-sla-availability-calculatoroptional · Educational calculation of availability or SLA scenarios from explicitly supplied values; never treat output as live system telemetry or contractual authority.]()[sha-256-hash-function-demooptional · Demonstrate or verify a source SHA-256 value for a supplied record or artifact; never infer provenance from a hash alone.]()[checksum-verifieroptional · Check a supplied checksum when a source provides one; failure must leave the record Held.]()[http-status-code-header-lookupoptional · Interpret a supplied HTTP status or header snapshot; never imply a connected provider or live endpoint.]() ## Outcome definitions **Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect. **Failed**: One or more deterministic acceptance requirements failed with an inspectable reason. **Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer. **Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent. The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only. ## Proposed deterministic acceptance tests Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded. - Identity test: the record exactly matches the supplied candidate ID, job ID, slug, title, Stan ownership, role, owner status, summary, source reference, tools, guides, gates, and never-rules. - Source test: every factual incident claim has a source record ID or locator; unsupported claims are labeled unknown or inference and cannot qualify as observed evidence. - Authority test: no action is marked Approved or Completed solely because Stan is named owner, because confidence is high, or because a native surface exists. - Negative test: a request for destructive remediation, money or purchasing, credential changes, public deployment, or legal filing is Held without explicit scoped approval. - Provider-boundary test: no record claims provider connection, credentials, database authority, customer indexing, publication, deployment, or production effect; local prototype and indexed states remain visible. - Chronology test: events sort deterministically by timestamp, timezone, source precedence, and revision; missing, contradictory, or future-dated events produce a visible failure state. - Duplicate test: reusing an incident ID or source SHA-256 with conflicting content is rejected or Held with a duplicate/conflict reason; no silent merge occurs. - Privacy test: only data necessary for incident response is captured; secrets, credentials, unnecessary personal data, and protected assets are rejected, redacted, or kept Held with a visibility class. - Accessibility test: all fields and status changes are keyboard operable, have persistent labels, expose text equivalents for non-text indicators, preserve logical focus order, and announce validation errors without relying on color. - Failure-state test: unavailable source, failed checksum, missing owner, missing approval, stale evidence, conflicting timestamps, failed handoff, and failed receipt each yield a distinct machine-readable state and next action. - Instrument test: only exact allowed slugs are used; optional instrument outputs are labeled educational or interpretive and never treated as authoritative live measurements. - Receipt test: every proposed or executed local step has a receipt containing actor, timestamp, input record IDs, output record IDs, state, and failure or rollback information. - Visibility test: private, held, and public-context records remain partitioned; search and PointGuard context do not expose held or private content to an unauthorized audience. - Communication test: messages retain recipient, source context, draft state, and approval state; final external send cannot occur from this package. - Closure test: qualification succeeds only when all mandatory tests pass and no unresolved principal gate, source conflict, privacy issue, accessibility issue, or failure state remains. ## Negative and held-state tests - Confusing Stan's verified owner status with permission to perform a gated effect. - Treating a named native surface as evidence of a connected web feature. - Converting incident hypotheses, confidence, or instrument outputs into facts. - Chronology corruption from missing timezone, clock skew, duplicate events, or silent revision replacement. - Exposure of credentials, secrets, customer data, protected assets, or private incident notes. - Accessibility failures caused by color-only status, unlabeled controls, inaccessible dialogs, or unannounced validation errors. - Loss of auditability when records are merged, overwritten, or detached from source locators and hashes. - Deadline pressure causing silent rescheduling, automatic remediation, external sends, or deployment. - Provider, database, credential, publication, customer-indexing, or production claims unsupported by the observed contract. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - This is a proposal-only qualification package for SRE and incident command. - The supplied source record identifies Stan as owner agent and Chief Security and Engineering Officer with verified owner status. - The observed contract provides local prototype or indexed surfaces for notes, files, to-dos, agenda, messages, approvals, projects, field guides, agent logs, search, PointGuard, and business review. - The package requires source-bound evidence, explicit authority checks, privacy minimization, accessibility review, chronology controls, and human-held principal gates. - The listed instruments are selected from the allowed verified-instrument directory and are optional educational or interpretive aids. ### Still held - Stan has production access or authority to execute remediation. - Any provider, credential, database, customer, publication, deployment, or external messaging connection exists. - Any incident is currently active, resolved, qualified, or attributable to a specific cause. - Any SLA, uptime, security, continuity, or availability result is live, contractual, or authoritative. - Any proposal, approval, receipt, or local prototype state represents an external effect. - Any customer indexing, protected storage, database write, credential change, legal filing, purchase, or public deployment occurred. ## 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` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `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/`