Outreach campaign — field guides

Record status

Record ID

project:outreach-campaign

Parent lifecycle

candidate

Page lane

app_features

Lane lifecycle

proposed

Owner

Not separately recorded

Owner role

Not separately recorded

Owner status

Not separately recorded

Qualification result

NOT RUN · held for evidence and human review

Working browser surface: Project templates & workflows — overview — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Related field-guide records

• /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create the project intake and assign one project owner.
2. Define scope, qualification rules, exclusions, evidence threshold, and no-send boundary.
3. Set the target outcome date and generate a dated workback with buffers and review time.
4. Create milestones, dependencies, owners, stop conditions, and fallback plans.
5. Create one account dossier record per in-scope account using source-labelled evidence.
6. Review dossiers for unsupported claims, missing provenance, privacy concerns, and accessibility needs.
7. Draft outreach messages linked to dossiers and evidence; do not send them.
8. Submit scope, claims, dossiers, and drafts to Notebook Approvals.
9. Resolve Needs review and Held items, preserving revisions and decision receipts.
10. Run acceptance checks for deadlines, ownership, evidence, recipient fields, and held external effects.
11. Record closure, including unfinished work, unresolved risks, held drafts, and the explicit no-send state.

Handoff boundary

• Unsupported or stale account claims may create misleading personalization.
• A manually entered recipient may be wrong or unauthorized.
• Private or sensitive information may be copied into dossiers without a documented need.
• A named route may be mistaken for a connected production capability.
• Draft approval may be mistaken for permission to send.
• Missing source locators or revisions may make evidence irreproducible.
• Deadline conflicts or omitted buffers may cause avoidable review failure.
• Attachments or file references may be unavailable, oversized, inaccessible, or unsafe to share.
• Low-confidence research may be presented as qualification.
• Agent activity may exceed its declared authority if receipts and held states are not reviewed.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• source_record:project:outreach-campaign
• NotebookCollectionKind.project
• NotebookTodoPayload.dueAt
• Notebook Agenda deadlines/workbacks
• PointGuard
• Notebook records provenance and revisions
• /app/notebook/projects/
• /app/notebook/to-dos/
• /app/notebook/agenda/
• /app/notebook/messages/
• /app/notebook/approvals/
• /app/notebook/files/
• /app/notebook/agent-logs/
• Notebook records provenance and revision contract
• PointGuard persistent cross-app context surface
• Web boundary: provider, credential, database, customer, publication, and production effects held