Source: https://guthlabs.ai/docs/field-guides/instrument-packets/
field guide / candidate
# Instrument packets
Proposal-only procedure for Tilly to assemble, review, reconcile, and hold source-bound instrument packets for independent review, instrument qualification, evidence reconciliation, grant research and drafts, and website claim review. The guide records provenance and verification state without asserting deployment, provider connection, publication, customer indexing, or qualification.
Status: **candidate**Lifecycle: **candidate**
## Record status
**Record ID**: field-guide:instrument-packets
**Parent lifecycle**: candidate
**Page lane**: catalog overview
**Lane lifecycle**: candidate
**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.
## Purpose and audience
Proposal-only procedure for Tilly to assemble, review, reconcile, and hold source-bound instrument packets for independent review, instrument qualification, evidence reconciliation, grant research and drafts, and website claim review. The guide records provenance and verification state without asserting deployment, provider connection, publication, customer indexing, or qualification.
- Tilly
- independent reviewers
- instrument qualification reviewers
- evidence reconciliation reviewers
- grant research and drafting teams
- website claim reviewers
## Required or proposed record references
The list defines expected record classes. It does not assert that any instance exists.
- source record for the instrument packet
- instrument record with exact allowed slug
- source locator and source SHA-256
- provenance and revision record
- evidence receipt
- review decision record
- linked job or field-guide membership record
- deadline or follow-up to-do where review remains open
## Route contract
The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.
[01**overview**/docs/field-guides/instrument-packets/]()[02**prerequisites**/docs/field-guides/instrument-packets/prerequisites/]()[03**steps**/docs/field-guides/instrument-packets/steps/]()[04**tools**/docs/field-guides/instrument-packets/tools/]()[05**forms**/docs/field-guides/instrument-packets/forms/]()[06**examples**/docs/field-guides/instrument-packets/examples/]()[07**related jobs**/docs/field-guides/instrument-packets/related-jobs/]()[08**qualification**/docs/field-guides/instrument-packets/qualification/]()
### Held source-proposed extensions
- /docs/field-guides/instrument-packets/overview/
These extension paths are not generated by this record and must not be treated as resolving routes.
## Public claim boundary
Allowed items below are source-lane proposals, not verified current-state claims.
### Candidate claims allowed after source review
- The packet is a proposal for source-bound review.
- The packet records supplied source references, provenance fields, review states, and bounded local workflow.
- An exact instrument slug and its supplied directory status may be named when copied from ALLOWED_INSTRUMENTS.
- A local prototype or index route may be described only according to its observed route summary and capabilities.
- A result may be described as an educational estimate when the selected directory entry explicitly labels it that way.
### Claims held
- Deployment or production availability.
- Provider, credential, database, customer, or external service connection.
- Publication, indexing, ranking, or qualification.
- A local Approved decision as production approval or instrument qualification.
- Completeness, authority, accuracy beyond the supplied source and instrument status.
- Professional, medical, legal, tax, investment, structural, electrical, or other domain advice.
- Successful upload, protected Vault custody, external message send, calendar write, or automation.
- Any claim derived only from a named native surface, route, interface label, or directory presence.
## 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.`
- `Observed native contract: project_and_field_guide_collections`
- `Observed native contract: deadlines`
- `Observed native contract: records`
- `Observed native contract: pointguard`
- `/app/notebook/field-guides/`
- `/app/notebook/notes/`
- `/app/notebook/files/`
- `/app/notebook/approvals/`
- `/app/notebook/search/`
- `/app/notebook/agent-logs/`
- `ALLOWED_INSTRUMENTS:checksum-verifier`
- `ALLOWED_INSTRUMENTS:url-query-string-parser`