Account dossiers — examples

The distinct examples record for Account dossiers. This page is proposal-only.

Status: proposedLifecycle: 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.

Hypothetical scenarios

A reviewer opens the Account dossiers guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded.

1. Guided inquiry fixture

A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review.

Fixture ID: account-dossiers-example-001
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

2. Source comparison fixture

A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied.

Fixture ID: account-dossiers-example-002
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

3. Uncertainty and pathway fixture

A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held.

Fixture ID: account-dossiers-example-003
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

4. Potentially allowed claim fixture

A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact.

Fixture ID: account-dossiers-example-004
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

5. Held claim fixture

A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed.

Fixture ID: account-dossiers-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Dossier identity fixture

Define the account dossier and its ownership without implying a connected customer or production system.

dossier title: Example value to be supplied and reviewed
account label or alias: Example value to be supplied and reviewed
canonical local record ID: Example value to be supplied and reviewed
owner agent: Named human or Agent owner required
human reviewer: Named human or Agent owner required
lifecycle: Example value to be supplied and reviewed

Scope and related jobs fixture

Bind the dossier to the supplied source record and its related jobs.

selected related jobs: Example value to be supplied and reviewed
research question: Example value to be supplied and reviewed
outreach objective: Example value to be supplied and reviewed
response-triage scope: Example value to be supplied and reviewed
campaign-chronology scope: Example value to be supplied and reviewed
in-scope date range: Not supplied in this hypothetical fixture

Evidence register fixture

Capture source-labelled facts and preserve traceability.

evidence item title: fixture-source-001 (hypothetical; no external claim)
source locator: fixture-source-001 (hypothetical; no external claim)
source type: fixture-source-001 (hypothetical; no external claim)
source date: Not supplied in this hypothetical fixture
retrieval or observation date: Not supplied in this hypothetical fixture
source SHA-256 if available: fixture-source-001 (hypothetical; no external claim)

Review questions

A dossier can be opened from PointGuard and its canonical owner and lifecycle are visible.
Every material claim links to a source-labelled note or file reference with provenance and, when available, a source SHA-256.
The dossier visibly distinguishes observed evidence, interpretation, missing evidence, and held claims.
All five related jobs are linkable without duplicate records or hidden automation.
A message draft shows recipient, source context, draft status, and human-held send state.
An approval record preserves reviewer, decision, rationale, timestamp or revision, and receipt.
Overdue or unresolved items expose an owner, due date, and escalation path.
Keyboard navigation, visible focus, labels, error summaries, and non-color-only status indicators are present for all form sections.

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/