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

field guide / candidate

Contact histories — forms

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

Proposed form sections

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

Scope and ownership

Define the history being assembled and assign human review responsibility.

  • history title
  • subject or organization label
  • owner agent
  • human reviewer
  • related job
  • time window
  • visibility classification
  • status: proposed, needs review, approved, or held

Contact event

Capture one source-bound event without converting an inference into a fact.

  • event date and time
  • source locator
  • source SHA-256 when available
  • event type
  • participants or recipient labels
  • channel as stated by source
  • verbatim or faithful summary
  • explicit source claims
  • uncertainty notes
  • linked file reference
  • record origin
  • revision identifier

Review and interpretation

Separate observed evidence from context, hypotheses, and proposed next actions.

  • confidence label
  • evidence-to-claim mapping
  • conflicting-source note
  • proposed interpretation
  • reviewer decision
  • decision receipt
  • follow-up owner
  • due date
  • hold reason

Chronology and outputs

Assemble the ordered history and identify bounded downstream uses.

  • ordered event list
  • missing-period note
  • response state
  • campaign relation
  • draft-message link
  • triage link
  • public/private boundary note
  • completion decision

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.

History identity

Define ownership and the bounded scope of the chronology.

  • history title
  • contact or entity label
  • owner agent
  • related job
  • visibility
  • status
  • canonical record ID

Evidence intake

Capture only traceable source material and preserve provenance.

  • event date and time
  • date precision
  • source locator
  • source type
  • source SHA-256 when available
  • summary of observed content
  • linked note ID
  • linked file reference
  • confidence label
  • missing-context flag

Chronology entry

Represent one interaction or relevant event without inventing intent or outcome.

  • event type
  • participants as recorded
  • channel as recorded
  • verbatim excerpt or bounded paraphrase
  • observed response state
  • open question
  • next action
  • event owner
  • revision note

Review and workback

Turn unresolved history items into explicit, human-reviewable work.

  • follow-up action
  • priority
  • due date and time
  • recurrence candidate
  • dependency
  • reviewer
  • held reason
  • completion state
  • linked approval ID

Use boundary

Prevent drafts, research summaries, or chronology claims from being treated as sent or published.

  • intended use
  • audience
  • private/public classification
  • human approval required
  • send/export state
  • unsupported-claim check
  • handoff receipt

Required or proposed record references

No record existence is asserted by this documentation page.

  • 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

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/