Source: https://guthlabs.ai/docs/field-guides/qualification-records/qualification/

field guide / candidate

# Qualification records — qualification

The distinct qualification record for Qualification records. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: field-guide:qualification-records

**Parent lifecycle**: candidate

**Page lane**: docs_urls

**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](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Qualification status

**Result**: NOT RUN

**Disposition**: HELD

**Reviewer**: Not recorded

**Receipt**: Not recorded

This page defines proposed acceptance criteria for the docs_urls lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

### Lane-specific instrument aids

[checksum-verifieroptional · Check whether supplied file or artifact digests match recorded qualification evidence.](<https://guthlabs.ai/docs/instruments/checksum-verifier/>)[sha-256-hash-function-demooptional · Explain SHA-256 evidence concepts in an educational, non-authoritative example.](<https://guthlabs.ai/docs/instruments/sha-256-hash-function-demo/>)

## Outcome definitions

**Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.

**Failed**: One or more deterministic acceptance requirements failed with an inspectable reason.

**Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.

**Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent.

The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.

## Proposed deterministic acceptance tests

Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded.

- Every proposed documentation route has a distinct purpose and non-duplicative content.

- The overview explains scope, audience, lifecycle, ownership, and held boundaries.

- The steps page presents the ordered workflow and includes failure handling for missing, conflicting, or unverifiable evidence.

- The tools page names only observed app surfaces and exact allowed instrument slugs.

- The forms page includes canonical identity, source provenance, claim scope, review disposition, owner, and due-date fields.

- An example distinguishes an observed verified-clean instrument status from a proposed qualification record and does not claim deployment or connection.

- The admitted canonical qualification page defines evidence completeness, traceability, independent review, limitation disclosure, and held states.

- Related-job pages explain distinct entry points and link back to the same record model without doorway duplication.

- A missing source locator, conflicting revision, unavailable digest, or unsupported public claim produces a held or needs-review state.

- Accessibility checks require labelled fields, keyboard-operable controls, visible focus, plain-language status labels, and non-color-only lifecycle indicators.

- Acceptance does not assert provider connection, database authority, customer indexing, publication, deployment, or production state.

## Negative and held-state tests

- Confusing a verified-clean directory status with qualification of a particular customer use or result.

- Treating a named native app surface as proof that a connected web feature exists.

- Publishing unsupported claims because a local approval was recorded.

- Losing provenance, revision, source locator, or digest metadata during reconciliation.

- Using stale or errata-marked instrument behavior without preserving the observed status and limitation.

- Creating duplicate doorway pages with near-identical qualification language.

- Exposing private notes, attachments, customer information, or held work in proposed public documentation.

- Treating a checksum or hash demonstration as proof of authorship, authenticity, safety, or production integrity.

## Qualification claim boundary

### Potentially allowed only after the stated evidence

- This is a proposed field guide for source-backed qualification records.

- The observed contract includes canonical IDs, provenance, revisions, lifecycle, links, attachments, and record revisions.

- Notebook provides native surfaces for notes, files, to-dos, approvals, field guides, search, and agent logs as described in the supplied contract.

- The allowed directory identifies exact instruments and observed statuses such as VERIFIED_CLEAN or VERIFIED_WITH_ERRATA.

- Qualification records can preserve evidence, limitations, review decisions, and held states.

### Still held

- That the guide is deployed or publicly published.

- That any provider, credential, database, customer, or production connection exists.

- That an instrument is connected to an app or authoritative for a customer decision.

- That local approval qualifies an instrument for regulated, commercial, clinical, financial, legal, or safety-critical use.

- That any source, file, checksum, claim, grant, or website statement has been independently verified unless a specific receipt records that review.

- That public indexing, customer indexing, external writes, exports, uploads, or publication effects occur.

## Sources and evidence

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

- `source_record:field-guide:qualification-records`

- `agents/index.html#tilly`

- `field-guide:qualification-records:docs_urls`

- `Observed native contract: project_and_field_guide_collections`

- `Observed native contract: records`

- `Observed native contract: deadlines`

- `Observed native contract: pointguard`

- `/app/notebook/field-guides/`

- `/app/notebook/notes/`

- `/app/notebook/files/`

- `/app/notebook/to-dos/`

- `/app/notebook/approvals/`

- `/app/notebook/agent-logs/`

- `/app/notebook/search/`

- `/app/pointguard/`

- `ALLOWED_INSTRUMENTS:checksum-verifier`

- `ALLOWED_INSTRUMENTS:sha-256-hash-function-demo`