Current-work packets — related jobs

The distinct related jobs record for Current-work packets. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:current-work-packets
Parent lifecycle: candidate
Page lane: plan
Lane lifecycle: proposed
Owner: Stan
Owner role: Not separately recorded
Owner status: Not separately recorded
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Field guides — documentation — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Related Agent job handoffs

source-listed handoffSecurity engineeringSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/current-work-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffArchitecture and implementationSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/current-work-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffSRE and incident commandSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/current-work-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffFleet operationsSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/current-work-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffReceipt-backed handoffsSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/current-work-packets/Open the separately admitted canonical job record; this guide does not import its package claims.

Handoff record requirements

The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.

A source-labelled current-work note with canonical ID, origin, source locator, source SHA-256, provenance, revision, lifecycle, tags, links, and attachments where applicable.
A bounded to-do record for each actionable next step, including due date, priority, completion state, tags, and revision history where applicable.
Linked file references for supporting material; uploads and protected storage remain held.
A review or approval record marked Needs review, Approved, or Held.
An Agent log entry recording current work, authority boundaries, receipt, and state.
source-labelled notes
linked file references
to-dos with due dates and review state
approval records
agent-log receipt
project or field-guide membership record

Ownership boundary

The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.

A named native route may be mistaken for a connected web feature.
A local approval may be mistaken for authorization to create external effects.
Unlabelled evidence can lose provenance or become detached from the canonical record.
Missing deadlines or owners can turn a workback into hidden automation or an unowned queue.
Conflicting revisions can produce an unsafe handoff if the latest source state is not inspected.
File references may imply upload or protected custody when those effects are held.
Agent context may be mistaken for specialist-app canonical ownership.
Accessibility failures can hide Held, Needs review, or deadline states from keyboard or assistive-technology users.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

source_record:field-guide:current-work-packets
agents/index.html#stan
Observed native contract: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
App route: /app/notebook/field-guides/
App route: /app/notebook/today/
App route: /app/notebook/notes/
App route: /app/notebook/files/
App route: /app/notebook/to-dos/
App route: /app/notebook/agenda/
App route: /app/notebook/approvals/
App route: /app/notebook/agent-logs/
App route: /app/pointguard/
Source record: field-guide:current-work-packets
ALLOWED_INSTRUMENTS directory: no instrument selected
Observed native contract: Notebook collections, deadlines, records, PointGuard, and held web boundary
App route: /app/notebook/projects/