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

field guide / candidate

Contact histories — related jobs

The distinct related jobs record for Contact histories. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
field-guide:contact-histories
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

source-listed handoffWorld-post researchSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/contact-histories/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffOutreach dossiersSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/contact-histories/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffMessage draftsSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/contact-histories/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffResponse triageSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/contact-histories/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffCampaign chronologySource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/contact-histories/Open the separately admitted canonical job record; this guide does not import its package claims.

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:contact-histories
  • source-labelled note records for each observed contact event
  • source-labelled file references for supporting material
  • draft message records when communication is proposed
  • approval records for consequential or ambiguous interpretations
  • todo records for unresolved follow-up and review deadlines
  • canonical contact-history record
  • source-labelled note for each evidence item
  • linked file reference where source material is local
  • draft message record when communication is proposed
  • to-do record for follow-up or review
  • approval record for any externally consequential decision
  • agent-log receipt for research and triage work

Ownership boundary

The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.

  • Treating a named person, organization, or channel as verified when the source does not establish it.
  • Collapsing multiple contacts into one event and losing provenance or chronology.
  • Filling missing dates, identities, intent, or response states through inference.
  • Converting a draft into a claim of sent, received, delivered, or provider-connected communication.
  • Exposing private contact history through public documentation or unrestricted search.
  • Treating a local prototype or indexed route as proof of a connected production feature.
  • Using unreviewed interpretations in outreach or campaign decisions.
  • Failing to preserve conflicting revisions or source hashes.
  • Allowing an overdue or unresolved item to disappear from the working record.

Sources and evidence

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

  • source_record:field-guide:contact-histories
  • agents/index.html#wick
  • field-guide:contact-histories
  • OBSERVED_NATIVE_CONTRACT.project_and_field_guide_collections
  • OBSERVED_NATIVE_CONTRACT.deadlines
  • OBSERVED_NATIVE_CONTRACT.records
  • OBSERVED_NATIVE_CONTRACT.pointguard
  • APP_ROUTES:/app/notebook/field-guides/
  • APP_ROUTES:/app/notebook/notes/
  • APP_ROUTES:/app/notebook/files/
  • APP_ROUTES:/app/notebook/messages/
  • APP_ROUTES:/app/notebook/approvals/
  • APP_ROUTES:/app/notebook/search/
  • APP_ROUTES:/app/notebook/agent-logs/
  • APP_ROUTES:/app/notebook/to-dos/
  • APP_ROUTES:/app/notebook/agenda/
  • APP_ROUTES:/app/pointguard/
  • Observed native contract: Notebook collections, deadlines, records, PointGuard, and held web boundary
  • App routes: /app/pointguard/, /app/notebook/notes/, /app/notebook/files/, /app/notebook/to-dos/, /app/notebook/agenda/, /app/notebook/messages/, /app/notebook/approvals/, /app/notebook/search/, /app/notebook/agent-logs/