Source: https://guthlabs.ai/docs/jobs/wick-outreach-dossiers/field-guides/

job / candidate

# Outreach dossiers — field guides

The distinct field guides record for Outreach dossiers. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: job:wick:outreach-dossiers

**Parent lifecycle**: candidate

**Page lane**: docs_urls

**Lane lifecycle**: proposed

**Owner**: Wick

**Owner role**: World posts and outreach agent

**Owner status**: HELD

**Qualification result**: NOT RUN · held for evidence and human review

**Working browser surface:** [Agent jobs — builder overview](<https://guthlabs.ai/guth.html#builder>) — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Related field-guide records

- /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

## Operating sequence

- Create the outreach brief and assign Wick as preparing owner.

- Create or link the account dossier and contact history; record only source-supported facts.

- Add source locators, excerpts, provenance, and source-lock status for each proposed factual claim.

- Assemble a world packet or outreach queue item with destination, audience, channel, and review deadline.

- Draft the communication in the appropriate message or document surface; label it as draft and proposal-only.

- Run bounded checks for impersonation, unverified send route, invented relationship history, unsupported pricing, and unsupported commitments.

- Classify any supplied response without sending a reply or changing account state.

- Create an approval record with the exact draft, sources, reviewer, scope, and held conditions.

- Record the final local state in Agent Logs and create or update the next human-owned to-do.

- If required evidence, recipient identity, route, or approval is missing, hold the item and log the failure state.

## Handoff boundary

- Impersonation or ambiguous author identity

- Sending from an unverified route

- Invented or conflated relationship history

- Unsupported pricing or commercial commitments

- Accidental publication or external send

- Unauthorized account access or credential handling

- Treating local prototypes or indexes as connected external systems

- Source drift, stale account context, or unverifiable claims

- Response misclassification causing an inappropriate follow-up

- Deadline ambiguity causing missed human review

- Sensitive contact information exposed in broad search or shared context

- Accessibility failures that hide held states or approval requirements

## Sources and evidence

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

- `agents/index.html#wick`

- `source_record:job:wick:outreach-dossiers`

- `Observed native contract: project_and_field_guide_collections`

- `Observed native contract: deadlines`

- `Observed native contract: records`

- `Observed native contract: pointguard`

- `App route: /app/notebook/messages/`

- `App route: /app/notebook/approvals/`

- `App route: /app/notebook/agent-logs/`

- `App route: /app/pointguard/`

- `job:wick:outreach-dossiers`

- `Observed native contract: records preserve canonical IDs, provenance, source locators, revisions, lifecycle, tags, links, attachments, and record revisions.`

- `Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.`

- `Observed native contract: current GuthHub app routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects are held.`