Source: https://guthlabs.ai/docs/field-guides/world-packets/forms/ field guide / candidate # World packets โ€” forms The distinct forms record for World packets. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:world-packets **Parent lifecycle**: candidate **Page lane**: plan **Lane lifecycle**: proposed **Owner**: Wick **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 scope Define the world, campaign, operator, boundaries, and intended packet outcome before research begins. - packet title - world or topic identifier - owner agent - related job - purpose - audience - visibility - start date - target completion date - known exclusions - human reviewer ### Source register Capture source-labelled evidence without treating an app route or named surface as proof of connected web behavior. - source locator - source title - source type - source date if supplied - source SHA-256 if available - provenance note - relevance statement - confidence or review state - linked file reference - access limitations ### World-post research Record bounded findings and unresolved questions that support the packet. - research question - observation - quoted or paraphrased evidence - source record link - unknowns - follow-up task - review status ### Outreach dossier Prepare recipient context and proposed approach while keeping external contact human-held. - recipient label - relationship or context - objective - relevant evidence links - proposed channel - personalization notes - sensitivity notes - do-not-claim constraints - reviewer ### Message draft Draft communication with explicit claims, recipients, attachments, and approval state. - recipient - subject or opening - body - claim-to-source mapping - attachments or file references - requested action - send-by deadline - approval state - held-effect note ### Response triage Classify incoming or reported responses without implying provider ingestion or delivery. - response reference - received or observed time - source of observation - response category - urgency - requested follow-up - owner - dueAt - escalation condition - triage state ### Campaign chronology Maintain a dated, source-linked sequence of research, drafts, reviews, and observed responses. - event date or time - event type - description - record link - source locator - actor - state transition - next deadline - uncertainty note ### Completion review Confirm evidence, links, accessibility, unresolved risks, and held external effects before marking the packet complete. - required records present - source links valid - claims reviewed - deadlines assigned - failure branches resolved or documented - accessibility check - approval receipt - completion decision - remaining open loops ### 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 ownership, scope, and the world or campaign being documented. - packet title - world or campaign name - owner agent - related job - audience - purpose - status - canonical record ID ### Source register Preserve traceability for every research assertion and attached reference. - source title - source locator - source type - source SHA-256 if available - captured date - relevance note - provenance label - revision ### Research findings Capture bounded findings while separating observation, interpretation, uncertainty, and open questions. - finding - supporting source IDs - confidence label - known limitations - contradictions - open questions - last reviewed date ### Outreach dossier Prepare recipient-specific context without claiming customer or provider data access. - recipient name as locally supplied - organization or context - reason for contact - relevant packet findings - relationship status - permitted contact channel - sensitivity notes - human reviewer ### Message draft Draft communication for review while keeping final send human-held. - recipient - subject - message body - source context links - attachments or file-reference IDs - requested response - draft expiry - send status ### Response triage and chronology Record incoming or manually supplied responses and maintain an auditable campaign timeline. - response record ID - response date and time - response source - triage category - next action - owner - due date - chronology event - receipt or approval ID ### Review boundaries Make authority, visibility, and failure handling explicit. - visibility - approval state - external-effect state - data handling note - failure state - accessibility check - reviewer sign-off ## Required or proposed record references No record existence is asserted by this documentation page. - source-labelled world packet record - world-post research notes - outreach dossier - message draft - response-triage record - campaign chronology - linked file references where source material exists - to-dos with dueAt, priority, tags, and completion state - approval receipt for any proposed external communication - canonical world-packet record - source-labelled research notes - local file references where applicable - approval receipt ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:field-guide:world-packets` - `agents/index.html#wick` - `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/notes/` - `app_route:/app/notebook/files/` - `app_route:/app/notebook/to-dos/` - `app_route:/app/notebook/messages/` - `app_route:/app/notebook/approvals/` - `app_route:/app/notebook/agent-logs/` - `app_route:/app/notebook/projects/` - `app_route:/app/pointguard/` - `OBSERVED_NATIVE_CONTRACT` - `APP_ROUTES`