Public-claim routes — related jobs

The distinct related jobs 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.

Related Agent job handoffs

source-listed handoffIndependent reviewSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/public-claim-routes/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffInstrument qualificationSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/public-claim-routes/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffEvidence reconciliationSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/public-claim-routes/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffGrant research and draftsSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/public-claim-routes/Open the separately admitted canonical job record; this guide does not import its package claims.source-listed handoffWebsite claim reviewSource-listed relation only.
Input: reviewed guide checkpoints and source references.
Output: a separately owned job record.
Failure: Held when source, owner, or authority is missing.
Guide: /docs/field-guides/public-claim-routes/Open the separately admitted canonical job record; this guide does not import its package claims.

Handoff record requirements

The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.

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

Ownership boundary

The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.

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