Source: https://guthlabs.ai/docs/field-guides/campaign-packets/prerequisites/

field guide / candidate

# Campaign packets — prerequisites

The distinct prerequisites 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](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

- Source record for field-guide:campaign-packets

- Campaign packet project record

- Campaign brief or planning note

- Draft content records

- Asset reference records

- Approval record

- Deadline to-dos

- Message drafts

- Post-performance record, if supplied

- Agent receipts and revision records

## Intended operators and ownership

- Rebecca

- Social planning agents

- Draft preparation agents

- Asset coordination agents

- Approval routing agents

- Post-performance records agents

- Human reviewers

Being listed as an intended operator does not grant execution or publication authority.

## Conditions that hold the guide before entry

- 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/`