Source: https://guthlabs.ai/docs/field-guides/current-work-packets/ field guide / candidate # Current-work packets Proposal-only procedure for preparing, reviewing, and handing off current-work packets using source-labelled Notebook records, explicit deadlines, bounded Agent authority, and receipt-backed review. The guide does not imply deployment, provider connection, database authority, customer indexing, publication, or qualification. Status: **candidate**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:current-work-packets **Parent lifecycle**: candidate **Page lane**: catalog overview **Lane lifecycle**: candidate **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. ## Purpose and audience Proposal-only procedure for preparing, reviewing, and handing off current-work packets using source-labelled Notebook records, explicit deadlines, bounded Agent authority, and receipt-backed review. The guide does not imply deployment, provider connection, database authority, customer indexing, publication, or qualification. - Stan - Security engineering - Architecture and implementation - SRE and incident command - Fleet operations - Receipt-backed handoffs ## Required or proposed record references The list defines expected record classes. It does not assert that any instance exists. - 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. ## Route contract The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted. [01**overview**/docs/field-guides/current-work-packets/]()[02**prerequisites**/docs/field-guides/current-work-packets/prerequisites/]()[03**steps**/docs/field-guides/current-work-packets/steps/]()[04**tools**/docs/field-guides/current-work-packets/tools/]()[05**forms**/docs/field-guides/current-work-packets/forms/]()[06**examples**/docs/field-guides/current-work-packets/examples/]()[07**related jobs**/docs/field-guides/current-work-packets/related-jobs/]()[08**qualification**/docs/field-guides/current-work-packets/qualification/]() ### Held source-proposed extensions - /docs/field-guides/current-work-packets/overview/ - /docs/field-guides/current-work-packets/related-jobs/security-engineering/ - /docs/field-guides/current-work-packets/related-jobs/architecture-and-implementation/ - /docs/field-guides/current-work-packets/related-jobs/sre-and-incident-command/ - /docs/field-guides/current-work-packets/related-jobs/fleet-operations/ - /docs/field-guides/current-work-packets/related-jobs/receipt-backed-handoffs/ These extension paths are not generated by this record and must not be treated as resolving routes. ## Public claim boundary Allowed items below are source-lane proposals, not verified current-state claims. ### Candidate claims allowed after source review - A proposal exists for source-labelled current-work packets. - The observed contract includes Notebook collections, deadlines and to-dos, provenance-preserving records, PointGuard context, and local prototype or index routes. - The procedure requires explicit ownership, deadlines, evidence, review states, failure branches, and receipt-backed handoffs. - The allowed directory contains verified-clean instruments, although this guide requires none. ### Claims held - Deployment or production readiness. - Connected provider, credential, database, customer, publication, or external messaging effects. - Database authority, customer indexing, or qualification. - Successful execution of any packet, handoff, approval, schedule write, upload, or protected-storage copy. - Any claim that Stan or the related jobs have completed the described work. ## 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/` - `field-guide:current-work-packets` - `OBSERVED_NATIVE_CONTRACT.project_and_field_guide_collections` - `OBSERVED_NATIVE_CONTRACT.deadlines` - `OBSERVED_NATIVE_CONTRACT.records` - `OBSERVED_NATIVE_CONTRACT.pointguard` - `APP_ROUTES:/app/notebook/field-guides/` - `APP_ROUTES:/app/notebook/today/` - `APP_ROUTES:/app/notebook/notes/` - `APP_ROUTES:/app/notebook/files/` - `APP_ROUTES:/app/notebook/to-dos/` - `APP_ROUTES:/app/notebook/approvals/` - `APP_ROUTES:/app/notebook/agent-logs/` - `APP_ROUTES:/app/notebook/search/` - `APP_ROUTES:/app/pointguard/`