Outreach rules — prerequisites

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.

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.

• 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

Intended operators and ownership

• Wick
• Agents preparing outreach dossiers
• Human reviewers
• Operators reviewing response triage and campaign chronology

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

Conditions that hold the guide before entry

• 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-rules
• agents/index.html#wick
• observed_native_contract:records
• observed_native_contract:deadlines
• observed_native_contract:pointguard
• app_route:/app/notebook/field-guides/
• app_route:/app/notebook/messages/
• app_route:/app/notebook/approvals/
• app_route:/app/notebook/agent-logs/