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

field guide / candidate

World packets — examples

The distinct examples 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.

Hypothetical scenarios

A reviewer opens the World packets 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
world-packets-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
world-packets-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
world-packets-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
world-packets-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
world-packets-example-005
Evidence
Hypothetical source placeholders only
Decision
HELD · human review required
External effects
None

Filled example fields

Packet scope fixture

Define the world, campaign, operator, boundaries, and intended packet outcome before research begins.

packet title
Example value to be supplied and reviewed
world or topic identifier
Example value to be supplied and reviewed
owner agent
Named human or Agent owner required
related job
Example value to be supplied and reviewed
purpose
Example value to be supplied and reviewed
audience
Example value to be supplied and reviewed

Source register fixture

Capture source-labelled evidence without treating an app route or named surface as proof of connected web behavior.

source locator
fixture-source-001 (hypothetical; no external claim)
source title
fixture-source-001 (hypothetical; no external claim)
source type
fixture-source-001 (hypothetical; no external claim)
source date if supplied
Not supplied in this hypothetical fixture
source SHA-256 if available
fixture-source-001 (hypothetical; no external claim)
provenance note
Example value to be supplied and reviewed

World-post research fixture

Record bounded findings and unresolved questions that support the packet.

research question
Example value to be supplied and reviewed
observation
Example value to be supplied and reviewed
quoted or paraphrased evidence
fixture-source-001 (hypothetical; no external claim)
source record link
fixture-source-001 (hypothetical; no external claim)
unknowns
Example value to be supplied and reviewed
follow-up task
Example value to be supplied and reviewed

Review questions

  • A new packet has a canonical ID, Wick ownership, lifecycle state, visibility, and linked related job.
  • Every finding links to one or more source-labelled records or is visibly marked as an open question.
  • Missing source metadata blocks readiness or produces a Held state rather than an unsupported claim.
  • A dossier can be reviewed without exposing private records outside their declared visibility.
  • A message draft displays recipient, body, source context, attachments, draft expiry, and Held send status.
  • An approval receipt records reviewer, decision, timestamp, proposal revision, and unresolved concerns.
  • A response can be entered manually with source, timestamp, triage category, owner, and next-action due date.
  • Chronology events preserve ordering, linked records, and revisions.

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