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

field guide / candidate

Outreach rules — forms

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

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Guide identity and ownership

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

  • title
  • slug
  • record type
  • lane
  • owner agent
  • related jobs
  • source references
  • proposal lifecycle

Outreach scope

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

  • world-post research scope
  • outreach dossier scope
  • message draft scope
  • response triage scope
  • campaign chronology scope
  • excluded effects
  • visibility

Source and evidence

Capture provenance for every research or outreach claim.

  • source locator
  • source SHA-256
  • origin
  • captured-at
  • record ID
  • revision
  • evidence summary
  • uncertainty or missing context
  • linked attachment or file reference

Review and workback

Make review ownership, deadlines, and dependencies explicit.

  • reviewer
  • decision state
  • review deadline
  • send deadline if applicable
  • priority
  • dependency records
  • hold reason
  • next action

Completion record

Document what was completed locally and what remains unexecuted.

  • completed steps
  • evidence links
  • approval receipt
  • unresolved risks
  • final local status
  • external action status
  • follow-up date

Accessible state contract

  • Every field requires a visible and programmatic label.
  • Required and optional fields must be stated in text.
  • Invalid entries require an actionable message linked to the field.
  • Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the tools lane and remain separate from the primary operating form.

Scope and ownership

Define the campaign, responsible owner, authority boundary, and source context before any draft is prepared.

  • campaign name
  • campaign objective
  • owner agent
  • human reviewer
  • related job IDs
  • source references
  • visibility
  • allowed outreach channel
  • external effects held confirmation

World-post research

Capture only source-labelled findings needed for an outreach dossier, with provenance and revision information.

  • research question
  • source locator
  • source SHA-256 when available
  • finding
  • confidence or review state
  • date observed
  • relevance to recipient
  • open verification questions

Outreach dossier

Assemble recipient context and proposed talking points without asserting unsupported customer, provider, or relationship state.

  • recipient name or organization
  • recipient identifier as supplied
  • known context
  • reason for contact
  • proposed value or question
  • evidence links
  • sensitive information check
  • claims requiring review
  • do-not-contact or exclusion note

Message draft

Prepare a bounded message for review while preventing implicit sending or external side effects.

  • channel
  • recipient
  • subject or opening
  • message body
  • attachments or linked records
  • requested response
  • tone
  • sender identity
  • send-by date
  • fallback date
  • human approval status

Response triage

Classify an incoming or manually recorded response and create the next human-owned action.

  • response source
  • receivedAt
  • response text or source locator
  • classification
  • urgency
  • requested action
  • owner
  • dueAt
  • snooze-until date
  • escalation reason
  • privacy review state

Campaign chronology

Maintain an auditable sequence of research, drafts, reviews, responses, and held actions.

  • event timestamp
  • event type
  • related record ID
  • actor
  • summary
  • status transition
  • receipt or revision ID
  • next checkpoint

Required or proposed record references

No record existence is asserted by this documentation page.

  • 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

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