Current-work packets — forms

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

Proposed form sections

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

Packet identity and scope

Define the packet without claiming an external system of record or completed production work.

packet title
owner
related job or workstream
purpose
scope statement
out-of-scope items
source record ID
origin
source locator
source SHA-256
provenance
revision
lifecycle
tags

Evidence and references

Attach only source-labelled evidence and make its custody and status visible.

evidence description
linked note IDs
linked file reference IDs
file type
file size
source locator
evidence status
known gaps
attachment custody note

Ordered workback

Turn the packet into bounded, reviewable actions with explicit deadlines.

step ID
action
responsible owner
dependency
priority
due date and time
recurrence candidate
completion state
review signal
failure branch
next fallback action

Review and handoff

Preserve human review, authority limits, and a receipt-backed transfer.

reviewer
review status
decision rationale
approval or hold reason
receipt reference
handoff recipient
handoff timestamp
open loops
follow-up due 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 tools lane and remain separate from the primary operating form.

Packet identity

Define the packet and its accountable owner.

packet title
packet type
owner agent
contributing agents
related job
created date
target handoff date
visibility

Current state

Capture what is known now without overstating implementation or production status.

current state summary
completed work
work in progress
blocked work
unknowns
source locators
source SHA-256 where available
record revision

Evidence and links

Attach traceable supporting records and distinguish observations from proposals.

linked note IDs
linked file-reference IDs
evidence description
provenance label
evidence freshness date
missing evidence
attachment review status

Workback and ownership

Turn the handoff target into dated, reviewable actions.

handoff deadline
milestone name
milestone due date
task owner
priority
dependency
recurrence candidate
completion state
review signal

Risks and authority boundary

Expose failure conditions and prevent unsupported external effects.

risk statement
impact
likelihood
mitigation owner
failure trigger
rollback or containment note
required approval
held external effect
customer or production impact: not established

Receipt-backed handoff

Make acceptance deterministic and preserve the handoff receipt.

recipient agent
handoff summary
open decisions
accepted records
rejected or held items
receipt timestamp
recipient acknowledgement
next review date

Required or proposed record references

No record existence is asserted by this documentation page.

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

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/