Source: https://guthlabs.ai/docs/field-guides/public-claim-routes/ field guide / candidate # Public-claim routes A source-bound procedure for Tilly to review, reconcile, and route public-facing claims through evidence, ownership, approvals, and held-state checks without implying publication, provider connection, customer indexing, or production effect. Status: **candidate**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:public-claim-routes **Parent lifecycle**: candidate **Page lane**: catalog overview **Lane lifecycle**: candidate **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]() — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held. ## Purpose and audience A source-bound procedure for Tilly to review, reconcile, and route public-facing claims through evidence, ownership, approvals, and held-state checks without implying publication, provider connection, customer indexing, or production effect. - Tilly - Independent reviewers - Instrument qualification owners - Evidence reconciliation owners - Grant research and drafts owners - Website claim reviewers ## Required or proposed record references The list defines expected record classes. It does not assert that any instance exists. - 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 ## Route contract The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted. [01**overview**/docs/field-guides/public-claim-routes/]()[02**prerequisites**/docs/field-guides/public-claim-routes/prerequisites/]()[03**steps**/docs/field-guides/public-claim-routes/steps/]()[04**tools**/docs/field-guides/public-claim-routes/tools/]()[05**forms**/docs/field-guides/public-claim-routes/forms/]()[06**examples**/docs/field-guides/public-claim-routes/examples/]()[07**related jobs**/docs/field-guides/public-claim-routes/related-jobs/]()[08**qualification**/docs/field-guides/public-claim-routes/qualification/]() ### Held source-proposed extensions - /docs/field-guides/public-claim-routes/overview/ - /docs/field-guides/public-claim-routes/related-jobs/independent-review/ - /docs/field-guides/public-claim-routes/related-jobs/instrument-qualification/ - /docs/field-guides/public-claim-routes/related-jobs/evidence-reconciliation/ - /docs/field-guides/public-claim-routes/related-jobs/grant-research-and-drafts/ - /docs/field-guides/public-claim-routes/related-jobs/website-claim-review/ These extension paths are not generated by this record and must not be treated as resolving routes. ## Public claim boundary Allowed items below are source-lane proposals, not verified current-state claims. ### Candidate claims allowed after source review - A proposal exists for a source-bound public-claim review procedure. - A local prototype or indexed route is available to inspect where the supplied route contract says so. - A claim can be drafted, linked to evidence, reviewed, approved locally, or held within the described Notebook surfaces. - A verified instrument directory contains exact listed slugs, when an exact slug is recorded and its limitations are stated. ### Claims held - Deployment, publication, launch, or production readiness. - Provider, credential, database, customer, or external-system connection. - Customer indexing, authoritative records, or live data effects. - Automatic sending, exporting, uploading, or publishing. - Instrument qualification, live instrument availability, or correctness beyond the supplied verified status. - Evidence sufficiency when source integrity, provenance, revision, or reviewer receipt is missing. - Completion of any related job based only on its name in the source record. - Any claim that a named native surface proves a connected web feature. ## 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/` - `/app/notebook/field-guides/` - `/app/notebook/approvals/` - `/app/notebook/search/` - `/app/notebook/agent-logs/` - `Observed native contract: records preserve canonical IDs, source locators, source SHA-256, provenance, revision, lifecycle, tags, links, attachments, and record revisions.` - `Observed native contract: PointGuard is a persistent cross-app context surface while specialist apps remain execution and canonical-record owners.` - `Observed native contract: current GuthHub routes are local prototypes or indexes and provider, credential, database, customer, publication, and production effects are held.` - `field-guide:public-claim-routes:docs_urls`