Source: https://guthlabs.ai/docs/jobs/tilly-instrument-qualification/forms/ job / candidate # Instrument qualification โ€” forms The distinct forms 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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Review scope Define the instrument, requested decision, owner, and boundaries before evidence review. - instrument name and exact catalog slug - instrument source record ID - requesting agent or owner - review purpose - requested decision type - reviewer identity - independent-review declaration - conflicts or prior involvement - review due date ### Evidence inputs Collect source-labelled evidence without implying hidden uploads or connected providers. - source locator - source SHA-256 - provenance description - source revision - catalog status - instrument inputs and assumptions - expected outputs - known limitations - attached local file references - related notes and records ### Qualification checks Record reproducible checks and whether evidence supports the intended use. - check ID - check description - test input - expected result - observed result - tolerance or pass rule - receipt or citation reference - qualification status - contradiction found - reviewer note ### Claim examination Test each proposed claim against receipts and prevent unsupported public language. - claim text - claim owner - claim scope - supporting receipt IDs - citation status - qualification dependency - overstatement risk - allowed wording - held wording - review outcome ### Decision dossier Assemble a reviewable package for qualification, grants, or public-claim routing. - decision summary - evidence index - open questions - failure conditions - recommended disposition - human approver - approval state - receipt links - revision note - next review date ### Accessible state contract - Every field requires a visible and programmatic label. - Required and optional fields must be stated in text. - Invalid entries require an actionable message linked to the field. - Blocked and Held states remain visible without relying on color alone. ## Supporting documentation fields These fields come from the docs_urls lane and remain separate from the primary operating form. ### Qualification request Identify the instrument, requesting agent, intended use, and review boundary without implying a verified connection. - request ID - instrument name and exact catalog identifier - requesting agent - owner and source-record reference - intended use - requested review scope - review deadline - urgency - known constraints ### Evidence packet Capture traceable evidence and source provenance for the proposed qualification. - evidence item ID - source locator - source SHA-256 when available - evidence type - quoted or measured claim - collection date - collector - linked record ID - attachment or local file reference - revision ### Qualification checks Record reproducible checks and distinguish observed evidence from interpretation. - check ID - check description - method - inputs - expected result - observed result - status: pass/fail/needs-review - reproduction notes - citation check result - contradiction found - reviewer ### Decision and boundaries Make a bounded recommendation while preserving unresolved issues and Tilly's independence. - qualification status: proposed/qualified/held/rejected - decision rationale - open contradictions - unsupported claims - required remediation - principal gate affected - independent reviewer - approval status - receipt ID ### Public-claim route Prevent draft material from becoming a public claim without separate review. - candidate public claim - supporting evidence IDs - claim scope - allowed wording - held wording - publication gate - final reviewer - publication decision - decision timestamp ## Required or proposed record references No record existence is asserted by this documentation page. - Instrument source record with canonical ID, origin, source locator, source SHA-256, provenance, revision, lifecycle, tags, links, and attachments - Qualification record - Claim examination record - Citation-check record - Grant dossier - Public-claim review record - Contradiction or exception record - Review receipt - Human approval record - Instrument packet - Evidence and citation receipt - Contradiction record - Public-claim review - Approval receipt - Agent log entry ## 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`