Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Instrument packets — related jobs

The distinct related jobs 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.

Related Agent job handoffs

source-listed handoffIndependent reviewSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/instrument-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffInstrument qualificationSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/instrument-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffEvidence reconciliationSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/instrument-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffGrant research and draftsSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/instrument-packets/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffWebsite claim reviewSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/instrument-packets/Open the separately admitted canonical job record; this guide does not import its package claims.

Handoff record requirements

The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.

  • 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
  • source-labelled instrument record
  • evidence note
  • file reference or source locator
  • review to-do
  • approval receipt
  • revision history

Ownership boundary

The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.

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