Public-claim routes — examples

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

Status: proposedLifecycle: 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.

Hypothetical scenarios

A reviewer opens the Public-claim routes guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded.

1. Guided inquiry fixture

A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review.

Fixture ID: public-claim-routes-example-001
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

2. Source comparison fixture

A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied.

Fixture ID: public-claim-routes-example-002
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

3. Uncertainty and pathway fixture

A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held.

Fixture ID: public-claim-routes-example-003
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

4. Potentially allowed claim fixture

A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact.

Fixture ID: public-claim-routes-example-004
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

5. Held claim fixture

A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed.

Fixture ID: public-claim-routes-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Claim intake fixture

Capture the claim and its source without strengthening or rewriting it into an unsupported assertion.

claim_text_verbatim: Example value to be supplied and reviewed
claim_type: Example value to be supplied and reviewed
requester: Example value to be supplied and reviewed
owner_agent: Named human or Agent owner required
source_record_id: fixture-source-001 (hypothetical; no external claim)
source_locator: fixture-source-001 (hypothetical; no external claim)

Evidence map fixture

Identify the evidence needed to support, narrow, or hold the claim.

evidence_record_ids: fixture-source-001 (hypothetical; no external claim)
evidence_description: fixture-source-001 (hypothetical; no external claim)
provenance_notes: Example value to be supplied and reviewed
revision_ids: Example value to be supplied and reviewed
known_gaps: Example value to be supplied and reviewed
conflicting_evidence: fixture-source-001 (hypothetical; no external claim)

Route and review fixture

Assign the claim to the appropriate bounded review path and record the decision state.

related_job: Example value to be supplied and reviewed
review_route: Example value to be supplied and reviewed
reviewer: Named human or Agent owner required
review_due_at: Not supplied in this hypothetical fixture
priority: Example value to be supplied and reviewed
decision_state: Held — pending human review

Review questions

A new claim has a canonical ID, named owner, audience, proposed wording, visibility state, and review deadline.
Every supporting evidence item has a source locator, SHA-256 where available, provenance note, and revision reference.
Search results show duplicate and conflicting local records without exposing held private material.
A reviewer can distinguish Needs review, Approved, and Held states and inspect the decision receipt.
An instrument record contains an exact allowed slug, intended use, inputs, result, limitations, and prohibited interpretation.
A missing, conflicting, or stale source prevents approval and produces a visible Held or Needs review state.
Public-copy drafts contain distinct useful content and a claim-to-evidence mapping rather than doorway or keyword-spam text.
Contrast checks record the tested color pairs and result; failure blocks approval of that visual draft.

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.