Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Campaign packets — tools

The distinct tools 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
tools
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.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

  • Notebook Projects (interface · required) — Owns the campaign packet grouping and links the brief, drafts, assets, approvals, deadlines, and post-performance records.
  • Notebook Notes (interface · required) — Stores the source-labelled brief, claim evidence, assumptions, and post-performance observations.
  • Notebook To-dos (interface · required) — Tracks explicit workback milestones, due dates, priority, completion state, tags, and human-review signals.
  • Notebook Files (interface · required) — Keeps source-labelled asset references beside records without implying hidden upload or protected storage.
  • Notebook Messages (interface · required) — Prepares communication drafts, recipients, source context, and review state while final send remains human-held.
  • Notebook Approvals (interface · required) — Preserves proposed decisions as Needs review, Approved, or Held with receipts and conditions.
  • Notebook Capture (interface · optional) — Prepares local photo, video, scan, or import records for asset review before any protected-storage copy.
  • Notebook Agent Logs (interface · required) — Makes Rebecca's bounded work, authority boundaries, receipts, and current state inspectable.
  • PointGuard (interface · optional) — Provides a persistent contextual room for the current packet while specialist apps remain execution and canonical-record owners.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

  • A named campaign channel may be only a local prototype or index; do not infer provider connection or publication capability.
  • Draft metrics, audience response, customer records, and performance values must not be invented when no source is available.
  • Asset references are not uploads, protected storage, rights clearance, or delivery confirmation.
  • Instrument estimates can be misread as platform guarantees, accessibility certification, or campaign performance.
  • Approval routing can fail through missing approvers, stale revisions, conflicting variants, or expired deadlines; preserve holds and receipts.
  • Sensitive private or customer information may be exposed if visibility and source labels are omitted.
  • Long copy, low contrast, missing alt text, uncaptioned media, and inaccessible controls can block review or exclude audiences.
  • Do not use live currency, live tide, or other unverifiable provider-dependent instruments for this guide.

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
  • Observed native contract: NotebookCollectionKind, NotebookTodoPayload, Notebook records, PointGuard, and web boundary
  • /app/notebook/field-guides/
  • /app/notebook/projects/
  • /app/notebook/to-dos/
  • /app/notebook/approvals/
  • /app/notebook/messages/
  • /app/notebook/files/
  • /app/notebook/capture/
  • /app/notebook/agent-logs/
  • /app/notebook/search/