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

field guide / candidate

# Qualification records — prerequisites

The distinct prerequisites 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**: 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](<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.

## Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

- Source-labelled qualification note

- Qualification evidence record

- Instrument reference record, if an instrument is used

- Evidence reconciliation record

- Review or approval record

- Deadline todo with owner and dueAt

- Revision and provenance receipt

## Intended operators and ownership

- Tilly

- Independent reviewers

- Evidence reconciliators

- Grant researchers and drafters

- Website claim reviewers

Being listed as an intended operator does not grant execution or publication authority.

## Conditions that hold the guide before entry

- A named native surface may be only a local prototype or index and does not prove a connected web feature.

- A checksum result can verify supplied data integrity but cannot prove source authority, truth, qualification, or publication status.

- Instrument outputs may be mistaken for evidence; inputs, assumptions, units, and limitations must remain attached.

- Conflicting revisions may be silently overwritten unless every material change preserves revision history.

- Local approval may be misrepresented as external approval or production authorization.

- Private, held, and public contexts may be conflated during search or linking.

- Missing source locators or hashes can lead to unsupported claims.

- Deadline todos can be mistaken for automation or completed external work.

- Accessibility failures can exclude reviewers if focus order, labels, status text, and keyboard operation are not preserved.

## 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`

- `OBSERVED_NATIVE_CONTRACT.records`

- `OBSERVED_NATIVE_CONTRACT.deadlines`

- `OBSERVED_NATIVE_CONTRACT.pointguard`

- `APP_ROUTES:/app/notebook/field-guides/`

- `APP_ROUTES:/app/notebook/notes/`

- `APP_ROUTES:/app/notebook/files/`

- `APP_ROUTES:/app/notebook/to-dos/`

- `APP_ROUTES:/app/notebook/approvals/`

- `APP_ROUTES:/app/notebook/search/`

- `APP_ROUTES:/app/notebook/agent-logs/`

- `ALLOWED_INSTRUMENTS:checksum-verifier`

- `ALLOWED_INSTRUMENTS:date-duration-calculator`