Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Public-claim routes — tools

The distinct tools 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
tools
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.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

  • PointGuard (interface · required) — Provides the contextual room for the current claim review while leaving Notebook as the canonical record owner; it must not be treated as a publication or provider-connected surface.
  • Notebook Notes (interface · required) — Owns the intake claim, source labels, tags, links, and revision history.
  • Notebook Files (interface · required) — Stores local file references beside evidence records while upload and protected storage remain held.
  • Notebook Search (interface · required) — Finds local indexed claims, evidence, reviews, and conflicts without implying customer or web indexing.
  • Notebook To-dos (interface · required) — Tracks reviewer deadlines, workbacks, completion state, priority, and human-review signals.
  • Notebook Approvals (interface · required) — Records Needs review, Approved, or Held decisions and preserves local receipts.
  • Notebook Paper (interface · required) — Prepares source-linked public copy and revisions while export and publication remain held.
  • Notebook Agent Logs (interface · required) — Shows Agent work, authority boundaries, receipts, and current state for auditability.
  • WCAG Contrast Ratio Checker (provider · optional) — Checks foreground/background contrast for a draft's visual presentation when colors are specified; it must not certify overall accessibility, publication readiness, or compliance beyond the checked values.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

  • A named route may be only a local prototype or index and must not be presented as a connected web feature.
  • A calculator result can support a bounded calculation but cannot validate a public claim, source authority, or production state.
  • Instrument slugs with errata require explicit caution; prefer VERIFIED_CLEAN instruments when the supplied catalog supports the need.
  • Checksum verification does not prove that an artifact is authentic, complete, current, or authoritative.
  • Unresolved conflicts, missing provenance, or unsupported extrapolation can turn a draft into a misleading public claim.
  • Public-facing drafts may expose private or held evidence if visibility partitioning is not checked.
  • Accessibility checks limited to contrast do not cover keyboard access, semantics, language, captions, or assistive-technology behavior.
  • Deadlines and approvals can be mistaken for external commitments unless publication and send effects remain explicitly held.

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
  • /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.