Source: https://guthlabs.ai/docs/field-guides/public-claim-routes/prerequisites/

field guide / candidate

# Public-claim routes — prerequisites

The distinct prerequisites record for Public-claim routes. This page is proposal-only.

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

## Record status

**Record ID**: field-guide:public-claim-routes

**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 claim record with canonical ID, origin, locator, source SHA-256, provenance, revision, lifecycle, tags, links, and attachments

- Evidence record linked to each claim

- Claim-review to-do with dueAt, priority, completion state, tags, and revisions

- Approval record marked Needs review, Approved, or Held

- Draft message or document record for any proposed outward communication

- Agent log receipt recording authority boundaries and current state

## Intended operators and ownership

- Tilly

- Independent reviewers

- Instrument qualification owners

- Evidence reconciliation owners

- Grant research and drafts owners

- Website claim reviewers

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

## Conditions that hold the guide before entry

- A source locator, hash, provenance value, or revision may be absent or stale.

- A claim may exceed what its evidence supports or conflate a named native surface with a connected web feature.

- Conflicting evidence may be hidden by premature wording or unrecorded reconciliation.

- An instrument may be incorrectly treated as an approval, qualification, live lookup, or production dependency.

- Prototype or indexed routes may be mistaken for deployed capabilities or authoritative customer records.

- Draft messages, exports, uploads, and publication actions may create unintended external effects.

- Private evidence may be exposed through public-facing wording or search.

- Missing deadlines, owners, or receipts may make a review appear complete when it is not.

- Accessibility omissions may prevent reviewers from detecting Held or Needs review states.

## Sources and evidence

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

- `source_record:field-guide:public-claim-routes`

- `agents/index.html#tilly`

- `Observed native contract: project_and_field_guide_collections`

- `Observed native contract: deadlines`

- `Observed native contract: records`

- `Observed native contract: pointguard`

- `App route: /app/notebook/field-guides/`

- `App route: /app/notebook/notes/`

- `App route: /app/notebook/files/`

- `App route: /app/notebook/to-dos/`

- `App route: /app/notebook/approvals/`

- `App route: /app/notebook/agent-logs/`

- `App route: /app/pointguard/`