Instrument packets — examples

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

Status: proposedLifecycle: candidate

Record status

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

Filled example fields

Packet identity fixture

Define the packet and its bounded purpose.

packet title: Example value to be supplied and reviewed
packet record ID: Example value to be supplied and reviewed
owner agent: Named human or Agent owner required
related job: Example value to be supplied and reviewed
intended audience: Example value to be supplied and reviewed
purpose statement: Held — pending human review

Source and provenance fixture

Bind every claim and instrument selection to supplied evidence.

source record ID: fixture-source-001 (hypothetical; no external claim)
source locator: fixture-source-001 (hypothetical; no external claim)
source SHA-256: fixture-source-001 (hypothetical; no external claim)
origin: Example value to be supplied and reviewed
capture or review date: Not supplied in this hypothetical fixture
provenance note: Example value to be supplied and reviewed

Instrument selection fixture

Select only an exact verified instrument slug and document why it is relevant.

exact instrument slug: Example value to be supplied and reviewed
instrument name: Example value to be supplied and reviewed
directory status: Held — pending human review
area: Example value to be supplied and reviewed
selection rationale: Example value to be supplied and reviewed
status caveat: Held — pending human review

Review questions

A packet contains an exact allowed instrument slug and matching catalog name; disposed or invented slugs are rejected.
The packet distinguishes catalog verification status from local review status and never labels an instrument qualified without supported evidence.
Every public claim marked allowed links to at least one source-labelled evidence record and includes any required caveat.
Every held claim is visibly marked Held and cannot be represented as an approved public claim.
Evidence records preserve canonical ID, source locator, provenance, revision, and hash fields when supplied or generated locally.
A reviewer can reproduce the recorded calculation or inspection from the stated inputs without hidden provider calls.
Conflicting evidence produces a recorded discrepancy and a Needs review or Held state.
Missing files, unavailable sources, checksum mismatch, malformed inputs, and inaccessible records produce visible failure states with an assigned owner.

Sources and evidence

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

source_record:field-guide:instrument-packets
agents/index.html#tilly
field-guide:instrument-packets
OBSERVED_NATIVE_CONTRACT
ALLOWED_INSTRUMENTS
Observed native contract: records preserve canonical IDs, source locators, source SHA-256, provenance, revision, 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.
Allowed instrument directory entries: checksum-verifier; sha-256-hash-function-demo; date-duration-calculator.