Source: https://guthlabs.ai/docs/field-guides/campaign-packets/steps/ field guide / candidate # Campaign packets โ€” steps The distinct steps record for Campaign packets. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:campaign-packets **Parent lifecycle**: candidate **Page lane**: plan **Lane lifecycle**: proposed **Owner**: Rebecca **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. ## Ordered procedure - Confirm the source record, owner agent Rebecca, related jobs, and campaign-packets slug. Create or link a Campaign packet project record and preserve the source reference, origin, locator, revision, lifecycle, and visibility metadata. - Write a bounded campaign brief in Notebook Notes. Record the internal objective, intended audience, proposed surfaces, formats, constraints, dependencies, and explicit out-of-scope effects. Do not state that a customer, provider, database, or publication surface is connected. - Create a workback in Notebook To-dos. Set internal draft, asset, review, approval, and post-performance-record deadlines relative to the target internal completion date. Use dueAt, priority, tags, completion state, and revision history where supported. - Collect source-labelled file references in Notebook Files. Record type, size, local reference, custody, linked packet record, provenance, and evidence gaps. Do not imply upload, protected storage, or external asset availability. - Prepare draft copy and supporting notes as separate revision-aware records. Link each draft to its brief, source evidence, intended placement, and responsible job. Mark assumptions and unresolved claims visibly. - Coordinate assets by linking only reviewed local references. For missing, contradictory, inaccessible, or unverified assets, create a blocking note and a replacement or clarification to-do rather than substituting an unverified asset. - Run an internal consistency review: compare copy, assets, dates, audience, constraints, links, and evidence. Check that every material claim has a source or is labelled as a proposal or open question. - Assemble the campaign packet index with links to the project, brief, drafts, asset references, deadlines, evidence notes, open questions, and receipts. Preserve record revisions and canonical IDs. - Route the packet through Notebook Approvals. Set Needs review until a human reviewer records a decision. Preserve the decision scope, required changes, reviewer, timestamp, and receipt. Approval is local and does not authorize external send or publication. - Prepare a human-held message draft in Notebook Messages if communication is needed. Inspect recipients and source context, attach the reviewed packet links, and leave final send held. - At the target internal completion checkpoint, verify that blocking items are resolved or explicitly held, all required records are linked, deadlines are visible, and the packet remains proposal-only. If any required condition fails, keep the packet in Held or Needs review. - After performance, create a post-performance record only from supplied evidence. Link measures to their source and period; record unavailable data as unavailable rather than estimating or claiming live results. ## Deadline and chronology rules - Set a target internal completion date before drafting begins; if absent, keep the packet in Needs review. - Create separate deadlines for draft completion, asset readiness, approval, and post-performance recording; do not collapse them into one implicit deadline. - Use the observed dueAt and priority fields for each deadline and preserve revisions when dates change. - Schedule a review buffer before the approval deadline; if the buffer is unavailable, mark the schedule risk explicitly. - If a deadline passes without completion, mark the to-do incomplete or held, create a recovery to-do, and do not represent the packet as ready. - External publication, provider writes, customer communication, credential use, and final send have no authorized deadline and remain held. ## Failure branches during execution - A named route may be only a local prototype or index, not a connected campaign system. - Draft copy may contain unsupported claims, stale dates, or audience assumptions. - Unverified or inaccessible assets may be mistaken for approved campaign materials. - Approval may be confused with publication authorization or final send. - Deadline fields may be treated as automation or external scheduling when provider effects remain held. - Private packet records may be exposed through incorrect visibility, links, or search filters. - Post-performance records may imply live metrics when no verified source is supplied. - Agent work may exceed authority if it sends, publishes, contacts customers, changes a provider, or writes to a database. - Accessibility issues may arise from unlabeled controls, unclear status text, poor keyboard order, or color-only review 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:campaign-packets` - `agents/index.html#rebecca` - `field-guide:campaign-packets` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `/app/notebook/field-guides/` - `/app/notebook/projects/` - `/app/notebook/notes/` - `/app/notebook/files/` - `/app/notebook/to-dos/` - `/app/notebook/approvals/` - `/app/notebook/messages/` - `/app/notebook/agent-logs/`