Page actions
field guide / candidate
Outreach rules — related jobs
The distinct related jobs record for Outreach rules. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- field-guide:outreach-rules
- Parent lifecycle
- candidate
- Page lane
- plan
- Lane lifecycle
- proposed
- Owner
- Wick
- 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.
Related Agent job handoffs
Handoff record requirements
The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.
- field-guide:outreach-rules
- job:world-post-research
- job:outreach-dossiers
- job:message-drafts
- job:response-triage
- job:campaign-chronology
- source-reference:agents/index.html#wick
- evidence:source-locator-and-sha256
- outreach-dossier
- message-draft
- response-triage-record
- campaign-chronology-record
- approval-receipt
- deadline-todo
- field-guide:field-guide:outreach-rules
- source-labelled notes
- recipient review records
- message draft records
- approval receipts
- campaign chronology records
- to-do records with dueAt and completion state
Ownership boundary
The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.
- Sparse source scope may be mistaken for a complete outreach policy; unresolved policy questions must remain visible.
- A named Wick owner agent does not prove current execution authority or connected outreach capability.
- Research notes without locators, provenance, or hashes can become unsupported claims.
- Drafted messages can be mistaken for sent messages; final send must remain human-held.
- Response triage can expose or infer private customer information; keep visibility and access state explicit.
- Chronology can conflate planned events with completed events unless lifecycle labels and receipts are preserved.
- Agenda and To-do surfaces may look operational while provider effects remain held.
- Accessibility risk: every checkpoint, hold reason, approval state, and deadline must be available as readable labels and not only color or visual ordering.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:field-guide:outreach-rulesagents/index.html#wickobserved_native_contract:recordsobserved_native_contract:deadlinesobserved_native_contract:pointguardapp_route:/app/notebook/field-guides/app_route:/app/notebook/messages/app_route:/app/notebook/approvals/app_route:/app/notebook/agent-logs/field-guide:outreach-rulesNotebookCollectionKindNotebookTodoPayload/app/pointguard//app/notebook/messages//app/notebook/approvals//app/notebook/to-dos//app/notebook/projects//app/notebook/notes//app/notebook/agent-logs/date-duration-calculatorcountdown-days-until-timer