Page actions
field guide / candidate
Citation rules — tools
The distinct tools 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
- tools
- 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.
Authoritative tools lane tools and interfaces
Canonical tools-page assignments
- Notebook Notes (interface · required) — Use /app/notebook/notes/ to create source-labelled notes, pin records, apply tags, and inspect source and revision metadata. Do not treat the interface as proof that an external source was fetched or verified.
- Notebook Files (interface · required) — Use /app/notebook/files/ to keep local, source-labelled file references beside citations and inspect type and size. Do not describe a reference as an uploaded or protected asset; upload and protected storage remain held.
- Notebook Approvals (interface · required) — Use /app/notebook/approvals/ to route disputed, incomplete, or high-impact citations through Needs review, Approved, or Held states. Local approval is not publication or external authorization.
- Notebook Agent Logs (interface · required) — Use /app/notebook/agent-logs/ to inspect agent authority, current work, and receipts. This supports accountability but does not establish that an agent accessed or validated an outside source.
- Notebook Search (interface · optional) — Use /app/notebook/search/ to find local indexed records, filter by type, and inspect source labels before reusing a citation. Respect private and held visibility partitions.
- PointGuard (interface · optional) — Use /app/pointguard/ to keep the active claim, source context, and review state visible across the work session. It is a context surface, not the canonical owner of specialist records.
- Checksum Verifier (provider · optional) — Use the verified checksum instrument to check a supplied digest against a supplied local value when a source record includes both. Do not use it to establish source authenticity, authorship, freshness, or external access.
- SHA-256 / Hash Function Demo (provider · optional) — Use the verified hash demo to illustrate or calculate a SHA-256 value for supplied local text or file content when recording provenance. Do not treat a matching hash as evidence that the content is authoritative or unchanged outside the supplied material.
Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.
Authoritative lane instrument assignments
Canonical tools-page assignments
checksum-verifierrequired · Verify a provided checksum pair for a local citation attachment or supplied source artifact; never infer provenance or authority from the result.sha-256-hash-function-demorequired · Generate or demonstrate SHA-256 for supplied citation content when the record needs an integrity receipt; never claim this proves publication, identity, or external retrieval.
An instrument listed only for another lane does not become a tools-page assignment.
Use boundary
- Invented page numbers, timestamps, URLs, excerpts, authors, or access dates.
- Treating a named source or native surface as proof of connected web access.
- Confusing hash equality with truth, authorship, provenance, freshness, or publication status.
- Citation laundering: presenting an interpretation as a quotation or presenting one source as support for a stronger claim than it makes.
- Overclaiming from local indexes, search results, file references, or agent receipts.
- Silent citation drift after source or record revisions.
- Exposing private, held, or sensitive source material through a public-facing draft.
- Using educational calculators as authoritative evidence without recording assumptions and limitations.
- Declaring a citation approved, published, externally sent, or qualified when the native contract only supports a local proposal or review state.
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-rulesagents/index.html#socratesfield-guide:citation-rules:toolsOBSERVED_NATIVE_CONTRACT.recordsOBSERVED_NATIVE_CONTRACT.pointguard/app/notebook/field-guides//app/notebook/notes//app/notebook/files//app/notebook/approvals//app/notebook/agent-logs//app/notebook/search/checksum-verifiersha-256-hash-function-demo