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

field guide / candidate

Citation rules — examples

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

Hypothetical scenarios

A reviewer opens the Citation rules 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
citation-rules-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
citation-rules-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
citation-rules-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
citation-rules-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
citation-rules-example-005
Evidence
Hypothetical source placeholders only
Decision
HELD · human review required
External effects
None

Filled example fields

Scope and ownership fixture

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

record title
Example value to be supplied and reviewed
claim or question
Example value to be supplied and reviewed
owner agent
Named human or Agent owner required
related job
Example value to be supplied and reviewed
audience
Example value to be supplied and reviewed
visibility
Example value to be supplied and reviewed

Source identity fixture

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

source locator
fixture-source-001 (hypothetical; no external claim)
source title or label
fixture-source-001 (hypothetical; no external claim)
source type
fixture-source-001 (hypothetical; no external claim)
source SHA-256 if available
fixture-source-001 (hypothetical; no external claim)
origin
Example value to be supplied and reviewed
provenance statement
Held — pending human review

Claim mapping fixture

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

claim text
Example value to be supplied and reviewed
claim scope
Example value to be supplied and reviewed
locator detail
fixture-source-001 (hypothetical; no external claim)
support status
Held — pending human review
direct quote or paraphrase marker
Example value to be supplied and reviewed
interpretation notes
Example value to be supplied and reviewed

Review questions

  • A citation record cannot be marked supported unless it contains a source title, source locator, claim text, support excerpt or explicit reason no excerpt applies, and an owner.
  • A quotation preserves its locator and is visibly distinguished from paraphrase or interpretation.
  • A missing or ambiguous locator produces a Held or Needs review state rather than a fabricated locator.
  • Every citation receipt links to a canonical record ID and preserves revision and provenance metadata.
  • A supplied checksum mismatch is surfaced as a failure and prevents the citation from being marked integrity-checked.
  • A matching SHA-256 is displayed as an integrity observation only, with no authority or authenticity claim.
  • Contradictory sources remain separately linked and are not collapsed into a single unsupported conclusion.
  • Private and held records do not appear in a public or broadly visible citation set.

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