Account dossiers — steps

Record status

Record ID

field-guide:account-dossiers

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. 1. Open PointGuard or Notebook Field Guides and create a proposed local account dossier record owned by Wick; label it as proposal-only and do not represent it as a connected account, customer record, or production object.
2. 2. Record the dossier identity, selected related jobs, research question, date scope, visibility, and human reviewer. If the scope or owner is missing, stop and create a clarification to-do rather than filling the gap by inference.
3. 3. Create source-labelled notes for each observed fact. For every note, preserve the source locator, source date, observation date, provenance, revision, and source SHA-256 when available; link each note to the dossier.
4. 4. Add local file references beside the notes when supporting files are available. Record type and size and link the reference to the relevant evidence item; do not imply upload, protected storage, or remote custody.
5. 5. Build an evidence register that separates direct evidence, summarized evidence, open questions, and hypotheses. Mark any claim without a source locator as held and exclude it from outreach personalization.
6. 6. Assemble a campaign chronology from dated evidence only. Mark missing intervals and conflicting dates explicitly; do not infer delivery, response, provider state, customer indexing, or publication.
7. 7. Draft the outreach dossier and any message in Notebook Messages. Include only evidence-backed personalization, identify recipients from supplied records only, attach or link reviewed context, and leave final send human-held.
8. 8. Create response-triage entries for known or observed responses. Classify the local working state as unresolved, needs review, approved, or held only when supported by a recorded evidence item; do not claim an external response was received unless the source record states it.
9. 9. Create To-do records for unresolved evidence, human review, approvals, and follow-up. Use explicit dueAt values, priority, completion state, tags, revisions, and deadline views; derive due dates only from an explicitly supplied date or human-entered workback.
10. 10. Review the dossier in Search and Agent Logs for source labels, linked records, authority boundaries, revisions, and receipts. Correct orphaned records, missing provenance, duplicate evidence, and inaccessible labels before handoff.
11. 11. Submit proposed messages and decisions through Approvals. Preserve the approval receipt and keep all final send, provider, database, customer, publication, and production effects held.
12. 12. Hand off the dossier to the named human reviewer with a completion summary, evidence register, open questions, deadlines, linked drafts, approval state, and explicit list of held effects. Revise the dossier when new evidence arrives rather than overwriting prior revisions.

Deadline and chronology rules

• Every open evidence gap, human review, approval, and follow-up must have an owner and an explicit dueAt or be marked undated and held.
• Do not invent dates from relative language. If a date is ambiguous, create a clarification task instead of scheduling it.
• Use priority and tags to distinguish evidence work, review, approval, and follow-up; retain revisions when deadlines change.
• Review the dossier before any deadline that controls a proposed message or decision, with sufficient human-review time left in the workback.
• If a deadline passes, mark the task overdue or held and preserve the prior state; do not imply escalation, delivery, or completion outside the local record.
• Recurring work is only a recurrence candidate until a human confirms the recurrence and its dates.

Failure branches during execution

• A named native surface may be only a local prototype or index; do not treat its presence as proof of a connected web feature.
• Unverified or stale evidence can create false account context or inappropriate personalization; preserve source dates, locators, provenance, and revisions.
• Mixing facts, hypotheses, and recommendations can turn speculation into an operational claim; keep separate fields and held states.
• Recipient ambiguity can cause an unsafe draft; stop when recipient identity or source context is not explicit.
• Chronology gaps and conflicting dates can produce false campaign narratives; record uncertainty rather than repairing it by inference.
• A local approval can be mistaken for permission to send or publish; keep all external effects human-held.
• Sensitive account material may be exposed by incorrect visibility or attachments; inspect visibility and local custody before handoff.
• Overdue work can silently become an implied commitment; preserve overdue or held state and obtain a human decision.
• Instrument calculations can validate date arithmetic only; they do not validate evidence, recipients, provider state, or customer status.

Sources and evidence

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

• source_record:field-guide:account-dossiers
• agents/index.html#wick
• Observed native contract: project_and_field_guide_collections
• Observed native contract: deadlines
• Observed native contract: records
• Observed native contract: pointguard
• App route: /app/pointguard/
• App route: /app/notebook/field-guides/
• App route: /app/notebook/notes/
• App route: /app/notebook/files/
• App route: /app/notebook/projects/
• App route: /app/notebook/to-dos/
• App route: /app/notebook/messages/
• App route: /app/notebook/approvals/
• App route: /app/notebook/search/
• App route: /app/notebook/agent-logs/
• Allowed instrument: date-duration-calculator
• Allowed instrument: countdown-days-until-timer