Account dossiers — prerequisites

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.

Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

• 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

Intended operators and ownership

• Wick
• researchers
• outreach operators
• message reviewers
• response triage reviewers
• campaign chronology reviewers
• human approvers

Being listed as an intended operator does not grant execution or publication authority.

Conditions that hold the guide before entry

• 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