Instrument packets — tools

The distinct tools 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: tools
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.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

Notebook Field Guides (interface · required) — Compose and browse the procedure, prerequisites, bounded steps, and linked instruments; it is an indexed local prototype, not proof of publication or connected web behavior.
Notebook Notes (interface · required) — Capture source-labelled evidence, review observations, claim wording, and reconciliation notes with tags and revisions.
Notebook Files (interface · required) — Keep local file references beside evidence and inspect type and size without implying hidden upload or protected-storage completion.
Notebook Approvals (interface · required) — Record local review decisions as Needs review, Approved, or Held and preserve receipts; approval is not qualification or publication.
Notebook To-dos (interface · required) — Track evidence, review, reconciliation, and approval deadlines with completion state, priority, tags, and human-review signals.
Notebook Search (interface · required) — Find packet records, evidence, and revisions within the local indexed boundary while respecting private and held visibility.
Notebook Agent Logs (interface · required) — Inspect agent authority, current work, and receipts before relying on a packet or accepting a local decision.
PointGuard (interface · required) — Carry the current packet context across Notebook surfaces; it does not replace the specialist app as canonical-record owner or execute external effects.
Checksum Verifier (provider · optional) — Use only to verify a supplied checksum or file-integrity value when a source record provides the relevant input; never treat a matching checksum as evidence of instrument correctness, qualification, or publication.
SHA-256 / Hash Function Demo (provider · optional) — Use to produce a locally recorded digest for an evidence artifact when needed for provenance; never use it to establish source authority, customer indexing, or production custody.
Date & Duration Calculator (provider · optional) — Use for deterministic deadline intervals and workback dates; do not use it as a calendar provider or to imply scheduled external writes.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

checksum-verifieroptional · Verify supplied artifact checksums during evidence reconciliation; record inputs and outputs in the packet.sha-256-hash-function-demooptional · Create a provenance digest for a locally referenced evidence artifact; retain the digest as metadata, not as substantive evidence.date-duration-calculatoroptional · Calculate review and reconciliation intervals from explicitly entered dates.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

A verified-clean catalog status does not prove a particular packet is qualified for a use case.
A native route or named surface does not prove a connected web feature or external provider effect.
Checksums and hashes establish artifact identity or integrity only; they do not establish truth, safety, authority, or qualification.
Grant drafts and website claims may overstate evidence if held claims are copied without their status and caveats.
Errata, stale source material, malformed inputs, and ambiguous units can produce misleading outputs.
Local approval is not external publication, customer indexing, or production deployment.
Private, held, and source-sensitive records must not be exposed through broad search or public documentation.
Medical, financial, engineering, legal, or safety-related instruments require domain review beyond this guide and must retain catalog caveats.

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: 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.