Outreach rules — examples

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

Hypothetical scenarios

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

Filled example fields

Guide identity and ownership fixture

Establish the source-bound guide identity and responsible owner without implying production authority.

title: Example value to be supplied and reviewed
slug: Example value to be supplied and reviewed
record type: Example value to be supplied and reviewed
lane: Example value to be supplied and reviewed
owner agent: Named human or Agent owner required
related jobs: Example value to be supplied and reviewed

Outreach scope fixture

Define which related jobs are in scope and record what remains held.

world-post research scope: Example value to be supplied and reviewed
outreach dossier scope: Example value to be supplied and reviewed
message draft scope: Example value to be supplied and reviewed
response triage scope: Example value to be supplied and reviewed
campaign chronology scope: Example value to be supplied and reviewed
excluded effects: Example value to be supplied and reviewed

Source and evidence fixture

Capture provenance for every research or outreach claim.

source locator: fixture-source-001 (hypothetical; no external claim)
source SHA-256: fixture-source-001 (hypothetical; no external claim)
origin: Example value to be supplied and reviewed
captured-at: Example value to be supplied and reviewed
record ID: Example value to be supplied and reviewed
revision: Example value to be supplied and reviewed

Review questions

A new campaign cannot reach an Approved state without an owner, human reviewer, objective, channel, source boundary, and external-effects-held confirmation.
A dossier displays source locators and distinguishes supplied facts, proposed language, and unresolved claims.
A message draft preserves recipient, channel, body, revision, send-by date, approval state, and linked evidence.
The send control is absent or clearly held, and no route implies that final send occurred.
An approval status change creates a durable receipt linked to the exact draft revision.
A manually recorded response cannot be triaged without a source locator or explicit statement that it was supplied by a human.
Every follow-up has an owner and either dueAt, snooze-until, or an explicit no-action state.
Campaign chronology lists material events in deterministic timestamp order and links each event to a canonical record ID.

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/
field-guide:outreach-rules
NotebookCollectionKind
NotebookTodoPayload
/app/pointguard/
/app/notebook/messages/
/app/notebook/approvals/
/app/notebook/to-dos/
/app/notebook/projects/
/app/notebook/notes/
/app/notebook/agent-logs/
date-duration-calculator
countdown-days-until-timer