Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

World packets — related jobs

The distinct related jobs record for World packets. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
field-guide:world-packets
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.

Related Agent job handoffs

source-listed handoffWorld-post researchSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/world-packets/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffOutreach dossiersSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/world-packets/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffMessage draftsSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/world-packets/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffResponse triageSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/world-packets/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffCampaign chronologySource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/world-packets/
Open the separately admitted canonical job record; this guide does not import its package claims.

Handoff record requirements

The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.

  • source-labelled world packet record
  • world-post research notes
  • outreach dossier
  • message draft
  • response-triage record
  • campaign chronology
  • linked file references where source material exists
  • to-dos with dueAt, priority, tags, and completion state
  • approval receipt for any proposed external communication
  • canonical world-packet record
  • source-labelled research notes
  • local file references where applicable
  • approval receipt

Ownership boundary

The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.

  • A named agent or route may be mistaken for an active connected service; label all surfaces as local prototypes or indexes where applicable.
  • Research may drift into unsupported world or recipient claims; require source mapping and explicit unknowns.
  • Draft approval may be mistaken for message delivery; preserve the human-held boundary.
  • A response reference may be incomplete or second-hand; record observation provenance and route ambiguity to review.
  • Stale, conflicting, or revised sources can invalidate a dossier; preserve revisions and reopen affected claims.
  • Sensitive recipient context may be over-collected; capture only fields necessary for the stated outreach purpose and respect visibility partitions.
  • Deadline automation may be inferred from recurrenceCandidate or scheduled views; use them only as local review signals.
  • Distinct documentation pages must contain useful procedure content; do not create doorway or keyword-spam pages.
  • Instrument selection is intentionally empty because the supplied packet workflow has no verified calculation requirement.

Sources and evidence

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

  • source_record:field-guide:world-packets
  • 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/notebook/field-guides/
  • app_route:/app/notebook/notes/
  • app_route:/app/notebook/files/
  • app_route:/app/notebook/to-dos/
  • app_route:/app/notebook/messages/
  • app_route:/app/notebook/approvals/
  • app_route:/app/notebook/agent-logs/
  • app_route:/app/notebook/projects/
  • app_route:/app/pointguard/
  • OBSERVED_NATIVE_CONTRACT
  • APP_ROUTES