Campaign packets — examples

The distinct examples record for Campaign packets. This page is proposal-only.

Status: proposedLifecycle: 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.

Hypothetical scenarios

A reviewer opens the Campaign 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: campaign-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: campaign-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: campaign-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: campaign-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: campaign-packets-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Packet identity fixture

Define the packet without implying an external campaign exists.

Packet title: Example value to be supplied and reviewed
Packet owner: Named human or Agent owner required
Related job: Example value to be supplied and reviewed
Internal objective: Example value to be supplied and reviewed
Intended audience: Example value to be supplied and reviewed
Working status: Held — pending human review

Scope and inputs fixture

Capture the bounded work needed for planning and preparation.

Channels or surfaces under consideration: Example value to be supplied and reviewed
Content formats: Example value to be supplied and reviewed
Required copy components: Example value to be supplied and reviewed
Required asset components: Example value to be supplied and reviewed
Known constraints: Example value to be supplied and reviewed
Dependencies: Example value to be supplied and reviewed

Schedule and workback fixture

Create explicit internal deadlines and review windows.

Target internal completion date: Not supplied in this hypothetical fixture
Draft deadline: Not supplied in this hypothetical fixture
Asset readiness deadline: Not supplied in this hypothetical fixture
Approval deadline: Held — pending human review
Review buffer: Example value to be supplied and reviewed
Post-performance record deadline: Not supplied in this hypothetical fixture

Review questions

A packet opens from Projects and links to a brief, drafts, assets, approval, deadlines, and post-performance note.
Every externally relevant claim in the draft has a source locator or is visibly marked as unresolved.
Each milestone displays an owner, due date, timezone, status, and dependency or failure note.
Asset references expose type, size or unavailable state, source locator, accessibility text state, and linked draft variant without hidden upload.
Approval cannot be represented as Approved unless an approver, decision timestamp, chosen variant, and receipt are recorded.
A held or missed approval leaves final send and publication unavailable in the procedure and preserves the reason.
Instrument outputs are stored as supporting evidence with inputs and limitations, not as production or audience-performance claims.
Post-performance records distinguish observed source values from unavailable values and do not claim customer indexing, provider connection, publication, or deployment.

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/
Observed native contract: NotebookCollectionKind, NotebookTodoPayload, Notebook records, PointGuard, and web boundary
/app/notebook/capture/
/app/notebook/search/