Source: https://guthlabs.ai/docs/field-guides/public-claim-routes/forms/ field guide / candidate # Public-claim routes โ€” forms The distinct forms 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]() โ€” Inspect the guide and persist local checkpoints. 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. ### Claim intake Capture the claim and its source without strengthening or rewriting it into an unsupported assertion. - claim_text_verbatim - claim_type - requester - owner_agent - source_record_id - source_locator - source_sha256 - origin - visibility - requested_review_deadline ### Evidence map Identify the evidence needed to support, narrow, or hold the claim. - evidence_record_ids - evidence_description - provenance_notes - revision_ids - known_gaps - conflicting_evidence - instrument_reference_if_any - evidence_owner ### Route and review Assign the claim to the appropriate bounded review path and record the decision state. - related_job - review_route - reviewer - review_due_at - priority - decision_state - decision_rationale - required_follow_up - approval_receipt_id ### Public draft boundary Prepare wording that is traceable to evidence while explicitly separating proposed copy from any publication effect. - draft_claim_text - qualified_language - source_attribution - limitations - audience - destination_surface - human_send_or_publish_owner - held_effects ### Completion and handoff Confirm records, receipts, accessibility, and unresolved hazards before closing or holding the work. - acceptance_check_results - open_loops - handoff_owner - next_review_due_at - completion_state - closure_note ### 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 tools lane and remain separate from the primary operating form. ### Claim intake Define the proposed public statement and its owner without implying publication. - claim title - proposed claim text - claim owner - audience - intended surface - claim category - related job - visibility state ### Evidence binding Attach source-labelled support and make gaps explicit. - evidence record IDs - source locator - source SHA-256 - provenance note - evidence date - supporting excerpt - known limitations - conflicting evidence - attachment references ### Review and qualification Capture independent review, instrument checks, and boundaries of use. - reviewer - review date - review outcome - instrument slug if applicable - instrument qualification status - allowed interpretation - prohibited interpretation - open questions - required revisions ### Decision and receipt Keep approval, hold, and publication preparation separate. - decision state: Needs review, Approved, or Held - decision owner - decision rationale - receipt ID - next action - deadline - escalation owner ### Public-copy preparation Prepare distinct useful documentation without claiming live publication or deployment. - draft URL path - page purpose - audience need - unique content outline - claim-to-evidence mapping - accessibility checks - review label - publication status: held ## Required or proposed record references No record existence is asserted by this documentation page. - 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 - source-bound claim record - evidence record with source locator and SHA-256 - independent review record - instrument qualification record - approval or hold receipt - draft public copy record - deadline todo ## 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.`