Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

job / candidate

Security engineering

Proposal-only reusable job package for Stan, Guth's persistent engineering agent, covering security, architecture, incident command, and continuity across bounded engineering work. The package prepares evidence-backed plans, reviews, receipts, and escalation records without claiming production authority or executing held effects.

Status: candidateLifecycle: candidate

Record status

Record ID
job:stan:security-engineering
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, Guth's persistent engineering agent, covering security, architecture, incident command, and continuity across bounded engineering work. The package prepares evidence-backed plans, reviews, receipts, and escalation records without claiming production authority or executing held effects.

  • Stan
  • Guth engineering operators
  • Security reviewers
  • Incident commanders
  • Human approvers
  • Architecture reviewers

Required or proposed record references

The list defines expected record classes. It does not assert that any instance exists.

  • Source-bound job record for job:stan:security-engineering
  • Current-work packet
  • Security or architecture assessment
  • Incident record, when applicable
  • Evidence and source-locator records
  • Risk register
  • Decision or approval record
  • Todo and deadline records
  • Receipt ledger entry
  • Agent log with authority and outcome state
  • Continuity and handoff record
  • Linked file references for reviewed artifacts

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/security-engineering/
  • /docs/jobs/security-engineering/responsibilities/
  • /docs/jobs/security-engineering/incident-command/
  • /docs/jobs/security-engineering/continuity/
  • /docs/jobs/security-engineering/evidence-and-receipts/
  • /docs/jobs/security-engineering/approval-gates/
  • /docs/jobs/security-engineering/failure-states/
  • /docs/jobs/security-engineering/accessibility/

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

  • Guth has a proposal-only security engineering job package for bounded assessment, architecture review, incident coordination, and continuity work.
  • The package uses source-bound evidence, explicit authority gates, review states, deadlines, receipts, and handoffs.
  • Named GuthHub, Notebook, PointGuard, Business, and guide surfaces are documented as local prototype or indexed surfaces according to the observed contract.
  • Verified instruments are not required for this security engineering package.

Claims held

  • Deployment, provider connection, credential access, database authority, customer indexing, publication, production operation, or qualification.
  • That Stan can independently approve or execute destructive remediation, purchasing, credential changes, public deployment, or legal filing.
  • That an incident has occurred, been contained, resolved, or communicated externally without source evidence and recorded approval.
  • That Supabase, Cloudflare, Terminal courier, or any other named surface has live external access.
  • That any proposed security control is certified, complete, or effective in production.
  • That a local prototype route constitutes a connected web feature or canonical production backend.

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:security-engineering
  • 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/field-guides/
  • App route: /app/notebook/agent-logs/
  • App route: /app/notebook/approvals/
  • App route: /app/notebook/projects/
  • App route: /app/notebook/to-dos/
  • App route: /app/notebook/messages/
  • App route: /app/notebook/files/
  • App route: /app/notebook/search/
  • App route: /app/business/messages/
  • App route: /app/business/vault/
  • source record job:stan:security-engineering
  • Observed native contract: web_boundary
  • App route /app/pointguard/
  • App route /app/notebook/approvals/
  • App route /app/notebook/agent-logs/
  • App route /app/notebook/projects/
  • App route /app/notebook/field-guides/
  • source record: job:stan:security-engineering
  • observed native contract: project_and_field_guide_collections
  • observed native contract: deadlines
  • observed native contract: records
  • observed native contract: pointguard
  • app route: /app/notebook/approvals/
  • app route: /app/notebook/agent-logs/
  • app route: /app/notebook/search/
  • app route: /app/notebook/files/
  • app route: /app/pointguard/
  • allowed instrument: checksum-verifier
  • allowed instrument: sha-256-hash-function-demo
  • allowed instrument: uptime-sla-availability-calculator