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

job / candidate

Fleet operations — field guides

The distinct field guides record for Fleet operations. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
job:stan:fleet-operations
Parent lifecycle
candidate
Page lane
docs_urls
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.

Related field-guide records

  • /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

  1. Capture the request as a canonical, source-bound job record and preserve its origin, locator, provenance, revision, and lifecycle metadata.
  2. Run Assurance preflight and record assumptions, missing evidence, access concerns, and any failure state before operational work is proposed.
  3. Create a current-work packet that separates included work, excluded work, dependencies, owners, deadlines, and human-review points.
  4. Use Source-bound recall to inspect only supplied records, linked notes, and referenced files; mark unavailable or unverified information as held.
  5. Use Terminal courier only for bounded courier or handoff preparation; record the intended command or transfer, recipient, scope, and receipt without claiming execution.
  6. Use the Receipt ledger to create a receipt for each material proposal, handoff, verification result, or blocked action.
  7. Build a deadline workback from the requested completion date, including intake, evidence collection, review, contingency, and closeout checkpoints.
  8. Route any destructive remediation, money or purchasing, credential change, public deployment, or legal filing to Approvals with status Needs review or Held.
  9. Preserve incident and continuity evidence, identify the last known good reference, and escalate when containment or authority is unclear.
  10. Verify the proposed result against source records and acceptance tests; record contradictions, missing evidence, and unresolved risks.
  11. Close the job only when the evidence packet, receipts, open loops, and next decision are recorded; otherwise retain the job as active or held.

Handoff boundary

  • Confusing Stan's verified owner status with permission to perform a gated effect.
  • Manufacturing Antonio's authority or attributing approval to an unnamed person.
  • Treating confidence, urgency, or an incident label as permission.
  • Converting a proposal, courier plan, or receipt into execution.
  • Destructive remediation without a rollback, containment, or human approval record.
  • Credential changes or public deployment without explicit gate review.
  • Purchasing or money movement hidden inside a fleet work item.
  • Source drift, stale evidence, missing provenance, or untraceable file references.
  • Over-broad recall that introduces unsupported operational claims.
  • Silent deadline slippage or recurring work that becomes unattended automation.
  • Exposure of sensitive security or continuity material through an inappropriate public surface.

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:fleet-operations
  • Observed native contract: PointGuard is a persistent cross-app context surface and specialist apps remain execution and canonical-record owners.
  • Observed native contract: Notebook records preserve canonical IDs, origin, source locators, source SHA-256, provenance, revision, lifecycle, tags, links, attachments, and record revisions.
  • Observed native contract: NotebookTodoPayload supports dueAt, priority, recurrenceCandidate, completion state, tags, revisions, and scheduled/deadline views.
  • Observed app route: /app/notebook/field-guides/
  • Observed app route: /app/notebook/agent-logs/
  • Observed app route: /app/notebook/approvals/
  • Observed app route: /app/notebook/to-dos/
  • Observed app route: /app/pointguard/
  • source record: job:stan:fleet-operations
  • observed native contract: project_and_field_guide_collections
  • observed native contract: deadlines
  • observed native contract: records
  • observed native contract: pointguard
  • observed native contract: web_boundary