Source: https://guthlabs.ai/docs/field-guides/account-dossiers/forms/ field guide / candidate # Account dossiers โ€” forms The distinct forms record for Account dossiers. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## 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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Dossier identity Define the account dossier and its ownership without implying a connected customer or production system. - dossier title - account label or alias - canonical local record ID - owner agent - human reviewer - lifecycle - visibility - created date - last reviewed date - next review date ### Scope and related jobs Bind the dossier to the supplied source record and its related jobs. - selected related jobs - research question - outreach objective - response-triage scope - campaign-chronology scope - in-scope date range - out-of-scope items ### Evidence register Capture source-labelled facts and preserve traceability. - evidence item title - source locator - source type - source date - retrieval or observation date - source SHA-256 if available - quoted or summarized evidence - confidence label - linked note or file reference - provenance statement ### Working synthesis Distinguish observed evidence from hypotheses and proposed implications. - account context derived from evidence - open questions - contradictions - hypotheses - recommended next investigation - unsupported claims explicitly held ### Campaign chronology Record dated events and communication state without claiming external delivery. - event date - event label - event source - event summary - related message draft - response state - uncertainty or missing interval - chronology reviewer ### Outreach and message preparation Prepare bounded outreach artifacts for human review. - proposed recipient label - recipient source context - message purpose - draft subject - draft body - attachments or linked records - personalization evidence - send status - human approval status ### Workback and review Make the next actions and review deadlines explicit. - task title - owner - priority - due date and time - recurrence candidate - dependency - completion state - review signal - escalation note ### Completion and handoff Record what is complete, what remains held, and who owns the next decision. - completion checklist - evidence count - open-risk count - handoff recipient - handoff date - approval record - held effects - next action - revision note ### 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. ### Account identity Define the account without asserting unverified customer or provider state. - account name - canonical account ID - known aliases - owner agent - dossier status - internal visibility ### Evidence register Capture traceable source material and separate observation from interpretation. - source locator - source type - retrieved or observed date - source SHA-256 when available - quoted or summarized evidence - provenance note - confidence label - unsupported claims to hold ### Related work Connect the dossier to existing research, outreach, drafts, triage, and chronology records. - related job or record ID - relationship type - record owner - current lifecycle - last reviewed date - next review date ### Outreach preparation Prepare communication context while preserving human control over recipients and sending. - message purpose - proposed recipient identity - source context - draft status - personalization rationale - attachments or linked records - send approval state ### Review and handoff Make unresolved risks, deadlines, and ownership explicit. - reviewer - decision state - decision rationale - open questions - due date - escalation owner - handoff receipt ## Required or proposed record references No record existence is asserted by this documentation page. - Account dossier record with canonical ID, owner Wick, lifecycle, provenance, source locators, source SHA-256 when available, revision, tags, links, and attachments - Source-labelled research notes - Local file references for supporting material - Linked records for World-post research, Outreach dossiers, Message drafts, Response triage, and Campaign chronology - To-do records for research, review, and follow-up deadlines - Draft message records with recipient and source context - Approval record for any proposed decision or external communication - Agent log receipt recording authority, evidence, current state, and held effects - account dossier record with canonical ID, owner, lifecycle, source locators, source SHA-256, provenance, revision, tags, links, and attachments - source-labelled note for every material claim - linked records for World-post research, Outreach dossiers, Message drafts, Response triage, and Campaign chronology - human-review approval record before any qualification, publication, or external send ## 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` - `OBSERVED_NATIVE_CONTRACT.project_and_field_guide_collections` - `OBSERVED_NATIVE_CONTRACT.records` - `OBSERVED_NATIVE_CONTRACT.pointguard` - `APP_ROUTES:/app/pointguard/` - `APP_ROUTES:/app/notebook/notes/` - `APP_ROUTES:/app/notebook/files/` - `APP_ROUTES:/app/notebook/projects/` - `APP_ROUTES:/app/notebook/messages/` - `APP_ROUTES:/app/notebook/approvals/` - `APP_ROUTES:/app/notebook/search/` - `APP_ROUTES:/app/notebook/agent-logs/`