Primary-source packets — examples

The distinct examples record for Primary-source packets. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: field-guide:primary-source-packets
Parent lifecycle: candidate
Page lane: plan
Lane lifecycle: proposed
Owner: Socrates
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 Primary-source 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: primary-source-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: primary-source-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: primary-source-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: primary-source-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: primary-source-packets-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Scope and ownership fixture

Define the inquiry before collecting or comparing material.

packet title: Example value to be supplied and reviewed
inquiry question: Example value to be supplied and reviewed
intended use: guided inquiry, source comparison, lesson pathway, or study record: fixture-source-001 (hypothetical; no external claim)
owner agent: Named human or Agent owner required
human reviewer: Named human or Agent owner required
audience: Example value to be supplied and reviewed

Source inventory fixture

Record each source without substituting unsupported material.

source title: fixture-source-001 (hypothetical; no external claim)
source type: fixture-source-001 (hypothetical; no external claim)
source locator: fixture-source-001 (hypothetical; no external claim)
provided artifact reference: Example value to be supplied and reviewed
source SHA-256 if available: fixture-source-001 (hypothetical; no external claim)
origin: Example value to be supplied and reviewed

Evidence extraction fixture

Capture bounded excerpts and claims with traceable locators.

source record ID: fixture-source-001 (hypothetical; no external claim)
excerpt or observation: Example value to be supplied and reviewed
locator: fixture-source-001 (hypothetical; no external claim)
claim supported: Example value to be supplied and reviewed
context needed: Example value to be supplied and reviewed
direct quotation or paraphrase: Example value to be supplied and reviewed

Review questions

A new packet can be created with a bounded inquiry question, owner, audience, learning objective, and target date.
Each source record requires a title, source locator or explicit missing-locator state, provenance note, and source type before review submission.
A locally available source can retain a SHA-256 value and a revision receipt; unavailable bytes produce a clear Not available state rather than an invented hash.
Comparison notes visibly distinguish evidence, interpretation, agreement, conflict, and uncertainty.
The workback shows owners and due dates for inventory, comparison, accessibility review, and human approval.
A missing source, conflicting claim, or uncertain attribution routes to Held or Needs review and cannot silently become Approved.
Keyboard navigation, visible focus, labelled fields, readable contrast, text alternatives for captured media, and non-colour-only status indicators are present.
Search returns only records permitted by visibility and shows source labels and lifecycle state.

Sources and evidence

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

source_record:field-guide:primary-source-packets
agents/index.html#socrates
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/approvals/
app_route:/app/notebook/agent-logs/
/app/notebook/field-guides/
/app/notebook/notes/
/app/notebook/files/
/app/notebook/approvals/
/app/notebook/agent-logs/