Source: https://guthlabs.ai/docs/field-guides/citation-rules/prerequisites/

field guide / candidate

# Citation rules — prerequisites

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

Status: **proposed**Lifecycle: **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](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

- 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

## Intended operators and ownership

- Socrates

- Guided inquiry agents

- Source comparison agents

- Lesson pathway authors

- Study record owners

- Reviewers checking uncertainty and provenance

Being listed as an intended operator does not grant execution or publication authority.

## Conditions that hold the guide before entry

- 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`