Instrument qualification — field guides

The distinct field guides record for Instrument qualification. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: job:tilly:instrument-qualification
Parent lifecycle: candidate
Page lane: docs_urls
Lane lifecycle: proposed
Owner: Tilly
Owner role: Pointguard and independent reviewer
Owner status: WORKING
Qualification result: NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Related field-guide records

/app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

Create or link the canonical instrument source record and preserve its locator, provenance, revision, and source SHA-256.
Declare the requested use, reviewer independence, conflicts, and decision deadline.
Collect source-labelled notes and local file references; do not imply upload, protected storage, provider access, or database authority.
Run the defined qualification checks against the instrument's stated inputs, outputs, assumptions, and limitations.
Record each expected result, observed result, tolerance, citation, and receipt as a revisioned qualification record.
Compare proposed claims with qualification evidence and citation checks; identify contradictions and claims that outrun receipts.
Separate allowed wording from held wording and document the reason for every held claim.
Assemble a grant dossier or public-claim review dossier when requested, preserving evidence links and unresolved questions.
Route the proposal to Notebook Approvals for human review; Tilly cannot approve her own evidence.
Record the final local review receipt, next review date, and any failure or requalification trigger.

Handoff boundary

Treating a named catalog entry or native surface as proof of a connected production feature.
Approving her own evidence or allowing reviewer identity to substitute for independent approval.
Hiding contradictions, missing citations, failed checks, or unsupported assumptions.
Turning qualification status into a public claim, funding commitment, credential grant, or publication.
Selecting or asserting an instrument that is not identified by an exact allowed slug.
Confusing a local prototype or index with provider, credential, database, customer, or publication authority.
Using educational or simplified instrument outputs as professional, legal, medical, financial, engineering, or operational assurance without appropriate review.
Allowing stale source revisions, missing checksums, or changed inputs to retain an active qualification state.
Deadline automation silently scheduling external actions rather than creating a human-review item.
Inaccessible forms that communicate qualification state only through color or require pointer-only interaction.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

agents/index.html#tilly
source_record:job:tilly:instrument-qualification
Observed native contract: project_and_field_guide_collections
Observed native contract: deadlines
Observed native contract: records
Observed native contract: pointguard
App route: /app/pointguard/
App route: /app/notebook/field-guides/
App route: /app/notebook/agent-logs/
App route: /app/notebook/approvals/
App route: /app/notebook/notes/
App route: /app/notebook/files/
App route: /app/notebook/to-dos/
App route: /app/notebook/projects/
App route: /app/business/home/
source record: job:tilly:instrument-qualification
observed native contract: records preserve IDs, provenance, revisions, lifecycle, tags, links, attachments, and record revisions
observed native contract: PointGuard is a persistent cross-app context surface and 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