Instrument packets — prerequisites

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.

Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

• 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

Intended operators and ownership

• Tilly
• independent reviewers
• instrument qualification reviewers
• evidence reconciliation reviewers
• grant research and drafting teams
• website claim reviewers

Being listed as an intended operator does not grant execution or publication authority.

Conditions that hold the guide before entry

• A directory name or native route may be mistaken for a connected production feature.
• Selecting a slug by approximate name can create an invalid or unverified instrument reference.
• VERIFIED_WITH_ERRATA instruments may be used without recording their limitations.
• Checksum or similarity results may be overstated as proof of source authority or publication.
• Duplicate evidence may be reconciled by deletion, destroying provenance and review history.
• A local Approved state may be misrepresented as production qualification or external authorization.
• Unresolved grant, website, customer, provider, credential, database, or publication claims may leak into public copy.
• Hidden uploads, protected storage, external sends, and provider writes may be implied by interface labels.
• Accessibility review may be reduced to contrast alone and incorrectly treated as complete conformance.
• Medical, financial, engineering, or other domain instruments may be presented as individualized advice or professional certification.

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