Source: https://guthlabs.ai/docs/field-guides/contact-histories/steps/ field guide / candidate # Contact histories โ€” steps The distinct steps 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**: 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. ## Ordered procedure - 1. Open the Contact histories field guide from Notebook Field Guides and confirm the source record, owner agent Wick, related jobs, and proposal-only lifecycle. Checkpoint: if the source record or owner cannot be identified, stop and mark the guide Needs review. - 2. Create or select a local project or field-guide-linked working record. Assign a human reviewer, visibility classification, review deadline, and status. Do not represent the record as a customer index, published history, or authoritative external database. - 3. Define the subject, time window, and inclusion rule. Record whether the task covers World-post research, outreach dossiers, message drafts, response triage, campaign chronology, or a bounded combination. Checkpoint: reject scope that lacks a subject, period, owner, or reviewer. - 4. Gather only supplied or locally available source-labelled notes and file references. For each item, preserve canonical ID, origin, source locator, source SHA-256 when available, provenance, revision, lifecycle, tags, links, and attachments. Do not imply that a file reference is an uploaded or protected asset. - 5. Enter one contact event per record using the event fields. Preserve dates, participants, channel, wording, and source location as observed. Mark unknown values as unknown rather than filling gaps from assumption. - 6. Separate direct evidence, faithful summary, interpretation, and proposed action. Add an uncertainty note whenever identity, chronology, intent, response state, or campaign relationship is ambiguous. - 7. Order events by the source-supported date and time. Where dates conflict or are missing, retain both source claims, document the conflict, and create a review todo with an explicit due date. Checkpoint: no event may be placed solely by inferred chronology without a visible uncertainty label. - 8. Link supporting notes and file references to the relevant event. Use Notebook Notes for source-labelled notes and Notebook Files for local references; keep upload, protected storage, and external retrieval held. - 9. Draft any downstream message only in Notebook Messages. Include the reviewed source context and intended recipient label, but keep final send human-held. Do not claim that a message was sent, received, delivered, or connected to a provider. - 10. Submit ambiguous interpretations, sensitive decisions, or consequential outreach proposals to Notebook Approvals. Preserve the local decision receipt and retain Needs review or Held when approval is absent. - 11. Create bounded follow-up todos in Notebook To-dos with owner, priority, dueAt, completion state, tags, and revisions. Use Agenda only to inspect or draft local schedule changes; hold external calendar writes. - 12. Review the assembled chronology in Search and Agent Logs. Confirm visibility partitioning, provenance, revisions, authority boundaries, and receipts. Checkpoint: if any event lacks a source locator, ownership, or uncertainty treatment, return it to Needs review. - 13. Mark the history complete only when all acceptance tests pass, unresolved conflicts have owners and deadlines, required approvals are recorded or explicitly held, and the human reviewer records completion. Keep lifecycle proposal-only unless a separately verified process changes it. ## Deadline and chronology rules - Set a review deadline when the history is opened. - Every unresolved date, identity, source conflict, or interpretation must have a named owner and explicit dueAt. - Draft-message review must occur before any proposed send date. - Overdue items remain visible and require human review; no automatic external escalation is implied. - Do not infer a deadline from a source unless the source explicitly states one. ## Failure branches during execution - 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/`