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

field guide / candidate

Citation rules — forms

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

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Scope and ownership

Define what is being cited, who owns the record, and what work is allowed.

  • record title
  • claim or question
  • owner agent
  • related job
  • audience
  • visibility
  • source record ID
  • source refs
  • allowed action boundary

Source identity

Capture enough source identity to distinguish evidence without asserting unverified access or publication.

  • source locator
  • source title or label
  • source type
  • source SHA-256 if available
  • origin
  • provenance statement
  • captured or reviewed date
  • revision identifier
  • lifecycle

Claim mapping

Connect each claim to a precise source location and explicitly mark support quality.

  • claim text
  • claim scope
  • locator detail
  • support status
  • direct quote or paraphrase marker
  • interpretation notes
  • uncertainty level
  • contradictory evidence link
  • unsupported-claim reason

Review and completion

Record checks, unresolved gaps, deadlines, and human review status.

  • reviewer
  • review date
  • checkpoint results
  • open questions
  • dueAt
  • priority
  • completion state
  • approval state
  • receipt or evidence link
  • revision notes

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.

Citation scope

Define what is being cited and why before drafting.

  • claim or passage to support
  • intended audience
  • citation purpose: evidence, comparison, lesson, or uncertainty
  • related job or study pathway
  • record owner

Source identity

Capture the source identity and locator without assuming external connectivity.

  • source title
  • creator or issuing body
  • source type
  • canonical source locator
  • specific locator: page, section, timestamp, figure, or anchor
  • access or observation date
  • source record ID if already indexed

Provenance and integrity

Preserve traceability and distinguish observed material from interpretation.

  • source SHA-256 when available
  • origin
  • provenance note
  • quoted text or faithful paraphrase
  • translation or transformation note
  • source revision or edition
  • attachment or local file reference

Claim and uncertainty review

Separate supported claims from interpretation and mark limits explicitly.

  • claim status: supported, partially supported, disputed, or held
  • supporting excerpt
  • inference label
  • uncertainty statement
  • contradictory source references
  • reviewer or reviewing agent
  • review decision

Citation receipt

Create a durable review artifact for later inspection.

  • citation receipt ID
  • linked record IDs
  • citation format used
  • verification steps completed
  • open follow-up
  • next review date
  • visibility: private, held, or reviewable

Required or proposed record references

No record existence is asserted by this documentation page.

  • 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

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