Source: https://guthlabs.ai/docs/jobs/tilly-instrument-qualification/tools/ job / candidate # Instrument qualification — tools The distinct tools record for Instrument qualification. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: job:tilly:instrument-qualification **Parent lifecycle**: candidate **Page lane**: package **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. ## Authoritative package lane tools and interfaces ### Canonical tools-page assignments - **PointGuard** (interface · required) — Persistent cross-app context surface for the current review room; it does not replace the specialist app as canonical-record owner. - **Instrument catalog** (record · required) — Source-record reference for the instrument identity, exact slug, lifecycle, provenance, and revision. - **Claim examiner** (skill · required) — Compare proposed claims with receipts, expose overstatement, and preserve held wording. - **Citation checks** (skill · required) — Verify that each claim and qualification result has a traceable source or receipt. - **Instrument packets** (guide · required) — Provide the bounded procedure for assembling instrument evidence. - **Qualification records** (record · required) — Canonical record for reproducible checks, results, limitations, and review state. - **Grant dossiers** (guide · optional) — Guide evidence assembly when an instrument review supports a funding proposal. - **Public-claim routes** (guide · optional) — Guide separation of supported wording from held public claims. - **Notebook Approvals** (interface · required) — Local review surface for human disposition and preserved approval receipts. Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved. ## Authoritative lane instrument assignments ### Canonical tools-page assignments No verified instrument is assigned to this tools lane. An instrument listed only for another lane does not become a tools-page assignment. ## Use 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/`