Fleet operations — forms

The distinct forms 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: 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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Fleet work request

Define the bounded engineering work and its source context.

request title
requesting agent or person
business or engineering objective
scope included
scope excluded
source record IDs or locators
urgency
requested completion date
known dependencies
sensitivity classification

Operating plan

Turn the request into explicit, reviewable work without implying authority.

ordered work steps
owner for each step
required tools
required records
verification method
failure state
rollback or containment note
human-review points
proposed status

Security and continuity controls

Record security posture, continuity needs, and bounded response handling.

assurance preflight result
credential or access concern
incident indicators
continuity risk
last known good reference
handoff contact
evidence to preserve
containment recommendation
escalation trigger

Principal gates

Identify actions that cannot proceed without explicit approval.

destructive remediation requested
money or purchasing involved
credential change requested
public deployment requested
legal filing requested
approval owner
approval state
approval receipt reference

Verification and closeout

Capture evidence, unresolved risks, and the next human decision.

completed checks
source-bound evidence references
receipt IDs
open loops
unresolved failure state
recommended next step
reviewer
closeout date

Accessible state contract

Every field requires a visible and programmatic label.
Required and optional fields must be stated in text.
Invalid entries require an actionable message linked to the field.
Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the docs_urls lane and remain separate from the primary operating form.

Request and operating context

Capture the bounded fleet-operations request without implying authority or production effect.

request title
requester identity and role
operational objective
fleet or system scope
known affected records or source locators
incident or continuity context
requested outcome
out-of-scope items

Risk and authority review

Identify actions that require human review before proceeding.

security impact
architecture impact
continuity impact
destructive remediation involved
money or purchasing involved
credential changes involved
public deployment involved
legal filing involved
proposed decision owner
approval status

Deadline and workback

Make timing explicit while requiring supplied dates rather than inventing them.

requested completion date
incident start or detection time
hard deadline indicator
time zone
review deadline
workback milestones
dependency owners
conflict notes

Evidence and receipts

Preserve source-bound evidence and a reviewable account of work.

source references
source SHA-256 when available
record IDs
commands or actions proposed
receipt references
revision note
unresolved questions
final disposition

Required or proposed record references

No record existence is asserted by this documentation page.

Canonical job record for job:stan:fleet-operations
Current-work packet
Source-bound notes and file references
Agent activity log
Receipt ledger entries
Approval records for gated actions
Deadline and workback to-dos
Incident or continuity record when applicable
Revision and provenance metadata for every derived record
job:stan:fleet-operations
fleet-operations intake record
current-work packet
deadline to-do record
approval record for gated actions
receipt ledger entry
agent-log entry

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