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

field guide / candidate

Citation rules — related jobs

The distinct related jobs record for Citation rules. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
field-guide:citation-rules
Parent lifecycle
candidate
Page lane
plan
Lane lifecycle
proposed
Owner
Socrates
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 handoffGuided inquirySource-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/citation-rules/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffSource comparisonSource-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/citation-rules/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffLesson pathwaysSource-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/citation-rules/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffStudy recordsSource-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/citation-rules/
Open the separately admitted canonical job record; this guide does not import its package claims.
source-listed handoffUncertainty markingSource-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/citation-rules/
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.

  • A source-labelled note for each claim or claim group
  • A source-labelled file reference when evidence is a file
  • A field-guide record containing ordered steps and checkpoints
  • A to-do record for unresolved citation or review work
  • An approval record for any proposed decision about citation quality
  • An agent-log record preserving authority, work state, and receipts
  • field guide record
  • source-labelled note
  • source file reference when applicable
  • citation receipt
  • revision record
  • approval or held-review record

Ownership boundary

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

  • A source locator may be too broad to support the claim; narrow the locator or hold the claim.
  • A source title or label may be mistaken for evidence; require a locator and provenance instead.
  • A source hash may be absent or unverifiable; never invent one and mark verification held.
  • A later revision may invalidate a prior citation; preserve revisions and reopen review.
  • Paraphrase may introduce interpretation; label interpretation separately from source-supported text.
  • Conflicting sources may be falsely harmonized; retain disagreement and scope differences.
  • A local approval may be mistaken for publication or qualification; state that external effects remain held.
  • A named route may be mistaken for a connected backend; treat routes as prototypes or indexes according to the observed contract.
  • Sensitive source material may be exposed through visibility or attachments; respect local/private partitioning and do not imply protected storage.
  • Instrument output may be treated as authoritative; use the checksum verifier only for supplied digest comparison and preserve its educational or verification scope.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • source_record:field-guide:citation-rules
  • agents/index.html#socrates
  • field-guide:citation-rules:plan
  • Observed native contract: records preserve canonical IDs, origin, 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 app route: /app/notebook/field-guides/
  • Observed app route: /app/notebook/notes/
  • Observed app route: /app/notebook/files/
  • Observed app route: /app/notebook/to-dos/
  • Observed app route: /app/notebook/approvals/
  • Observed app route: /app/notebook/agent-logs/
  • Allowed instrument: checksum-verifier
  • field-guide:citation-rules:tools
  • OBSERVED_NATIVE_CONTRACT.records
  • OBSERVED_NATIVE_CONTRACT.pointguard
  • /app/notebook/field-guides/
  • /app/notebook/notes/
  • /app/notebook/files/
  • /app/notebook/approvals/
  • /app/notebook/agent-logs/
  • /app/notebook/search/
  • checksum-verifier
  • sha-256-hash-function-demo