Source: https://guthlabs.ai/docs/field-guides/current-work-packets/examples/ field guide / candidate # Current-work packets — examples The distinct examples record for Current-work packets. This page is proposal-only. Status: **proposed**Lifecycle: **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. ## Hypothetical scenarios A reviewer opens the Current-work packets guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded. ### 1. Guided inquiry fixture A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review. **Fixture ID**: current-work-packets-example-001 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 2. Source comparison fixture A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied. **Fixture ID**: current-work-packets-example-002 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 3. Uncertainty and pathway fixture A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held. **Fixture ID**: current-work-packets-example-003 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 4. Potentially allowed claim fixture A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact. **Fixture ID**: current-work-packets-example-004 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ### 5. Held claim fixture A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed. **Fixture ID**: current-work-packets-example-005 **Evidence**: Hypothetical source placeholders only **Decision**: HELD · human review required **External effects**: None ## Filled example fields ### Packet identity and scope fixture Define the packet without claiming an external system of record or completed production work. **packet title**: Example value to be supplied and reviewed **owner**: Named human or Agent owner required **related job or workstream**: Example value to be supplied and reviewed **purpose**: Example value to be supplied and reviewed **scope statement**: Held — pending human review **out-of-scope items**: Example value to be supplied and reviewed ### Evidence and references fixture Attach only source-labelled evidence and make its custody and status visible. **evidence description**: fixture-source-001 (hypothetical; no external claim) **linked note IDs**: Example value to be supplied and reviewed **linked file reference IDs**: Example value to be supplied and reviewed **file type**: Example value to be supplied and reviewed **file size**: Example value to be supplied and reviewed **source locator**: fixture-source-001 (hypothetical; no external claim) ### Ordered workback fixture Turn the packet into bounded, reviewable actions with explicit deadlines. **step ID**: Example value to be supplied and reviewed **action**: Example value to be supplied and reviewed **responsible owner**: Named human or Agent owner required **dependency**: Example value to be supplied and reviewed **priority**: Example value to be supplied and reviewed **due date and time**: Not supplied in this hypothetical fixture ## Review questions - A packet can be identified by a canonical record ID, owner, related job, lifecycle, and revision. - Each material claim links to a source-labelled note or file reference, or is explicitly marked unknown or proposed. - Every actionable task has one owner, a due date or documented no-date reason, and a completion state. - The workback exposes dependencies, blockers, overdue items, and review checkpoints without hidden automation. - Provider, credential, database, customer, publication, and production effects remain explicitly held. - Approval state and receipt are preserved for every consequential decision or handoff. - A recipient can identify accepted items, unresolved items, next review date, and the packet revision from the handoff record. - Forms provide labels, keyboard access, non-color status text, readable validation, and clear failure states. ## 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/`