Source: https://guthlabs.ai/docs/field-guides/contact-histories/tools/

field guide / candidate

# Contact histories — tools

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

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: field-guide:contact-histories

**Parent lifecycle**: candidate

**Page lane**: tools

**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](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Authoritative tools lane tools and interfaces

### Canonical tools-page assignments

- **Notebook Notes** (interface · required) — Use for source-labelled evidence, quotations, interpretations, tags, pins, and revision inspection. Do not use it as proof of an external contact database or as a substitute for provenance.

- **Notebook Files** (interface · required) — Use for local, source-labelled references to email exports, documents, or other evidence beside the history. Do not treat the surface as hidden upload, protected storage, or provider synchronization.

- **Notebook To-dos** (interface · required) — Use for explicit follow-ups, review deadlines, completion state, priority, recurrence candidates, and held items. Do not use it to imply automatic outreach or external scheduling.

- **Notebook Agenda** (interface · required) — Use to inspect and draft internal time blocks for review work and conflict checking. Do not use it for external calendar writes or provider-backed appointments.

- **Notebook Messages** (interface · required) — Use to prepare and inspect message drafts, recipients, and source context. Do not use it to send messages or claim delivery, response, or provider connection.

- **Notebook Approvals** (interface · required) — Use for human review of proposed messages, classifications, or campaign decisions and preserve receipts. Do not use local approval as evidence that an external action occurred.

- **Notebook Search** (interface · required) — Use to find local indexed history records, notes, and linked evidence while respecting visibility. Do not treat local search as customer indexing, exhaustive discovery, or production database authority.

- **PointGuard** (interface · required) — Use as the persistent contextual room for the current history, linked Notebook records, and bounded handoffs. Do not treat it as the canonical owner of specialist records or as a connected web feature.

- **Notebook Agent Logs** (interface · required) — Use to inspect Wick's work, authority boundaries, receipts, and current state. Do not infer completion, sending, qualification, or publication from an agent-log entry alone.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

## Authoritative lane instrument assignments

### Canonical tools-page assignments

No verified instrument is assigned to this tools lane.

An instrument listed only for another lane does not become a tools-page assignment.

## Use boundary

- Confusing a local note or message draft with a sent communication or authoritative customer record.

- Inventing dates, participants, intent, response, or campaign outcomes from incomplete evidence.

- Over-collecting personal or sensitive contact information without a stated bounded purpose.

- Treating search results as exhaustive when only local indexed records are available.

- Losing provenance when paraphrasing source material or merging duplicate events.

- Allowing stale or overdue follow-ups to disappear from current work.

- Making accessibility or workflow state depend only on color, hover, or agent assumptions.

- Using a named native surface as evidence that a connected web feature exists.

## 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`

- `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/`