Instrument packets — qualification

Record status

Record ID

field-guide:instrument-packets

Parent lifecycle

candidate

Page lane

docs_urls

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.

Qualification status

Result

NOT RUN

Disposition

HELD

Reviewer

Not recorded

Receipt

Not recorded

This page defines proposed acceptance criteria for the docs_urls lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

Outcome definitions

Verified

All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.

Failed

One or more deterministic acceptance requirements failed with an inspectable reason.

Needs review

Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.

Held

Authority, required evidence, safe execution conditions, or a principal gate is absent.

The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.

Proposed deterministic acceptance tests

Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded.

• Every documentation route has a distinct purpose and includes content not duplicated from the overview or other routes.
• The overview identifies the owner agent Tilly, related jobs, proposed lifecycle, evidence boundary, and qualification boundary.
• A reviewer can create a packet with an exact allowed instrument slug, source locator, source hash, owner, reviewer, and deadline.
• Inputs preserve values, units, assumptions, source links, and missing-data states.
• The procedure supports match, conflict, unresolved, and Held states without silently converting uncertainty into qualification.
• A packet cannot produce an Approved public claim without a supporting evidence reference and named reviewer decision.
• The guide never states that a provider, credential, database, customer index, publication, or production effect is connected.
• The guide labels educational instruments and results appropriately and routes professional, legal, medical, financial, or engineering decisions to qualified human review where relevant.
• Records retain canonical identity, provenance, revisions, lifecycle, links, and receipts using the observed Notebook contract.
• Keyboard navigation, visible focus, labels, error summaries, non-color status text, and accessible table or list alternatives are present on every proposed form page.
• Related-job pages explain their distinct relationship to instrument packets rather than acting as doorway pages.

Negative and held-state tests

• A named native surface may be mistaken for a connected web feature; all app routes remain local prototypes or indexes unless separately verified.
• A verified-clean instrument status does not prove that the proposed packet has run, that its result is authoritative, or that a provider is connected.
• Instrument entries with errata require explicit review and must not be presented as unqualified evidence.
• Hash or locator checks can support reconciliation but do not establish authorship, authority, recency, or publication.
• Incomplete inputs, unit mismatches, copied outputs, and stale revisions can produce false agreement.
• Public claims may overstate local prototypes, qualification, customer indexing, database authority, or deployment.
• Sensitive source files or personal data may be exposed through notes or file references; minimize data and keep protected storage held.
• Deadlines can create pressure to approve unresolved evidence; missed or unresolved work must remain Held.

Qualification claim boundary

Potentially allowed only after the stated evidence

• Instrument packets are proposed source-backed records for organizing inputs, evidence, review decisions, and revisions.
• The procedure distinguishes source evidence, instrument output, qualification status, and public claim review.
• Notebook surfaces can be used as local prototype or indexed review surfaces where their route state says so.
• The listed instruments may be referenced by exact allowed slug and displayed directory status, subject to the stated educational or errata limitations.

Still held

• Any claim that an instrument is connected to a live provider or production web feature.
• Any claim of deployment, publication, customer indexing, database authority, credential verification, or external write.
• Any claim that a packet result is professional medical, legal, financial, engineering, or grant-authoritative advice.
• Any claim that qualification has occurred before a reviewer records evidence, criteria, decision, and receipt.
• Any claim that a local route is a customer-facing public service.

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