Source: https://guthlabs.ai/docs/field-guides/citation-rules/qualification/ field guide / candidate # Citation rules โ€” qualification The distinct qualification 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**: docs_urls **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. ## Qualification status **Result**: NOT RUN **Disposition**: HELD **Reviewer**: Not recorded **Receipt**: Not recorded This page defines proposed acceptance criteria for the docs_urls lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect. ### Lane-specific instrument aids No verified instrument is assigned to this qualification lane. ## Outcome definitions **Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect. **Failed**: One or more deterministic acceptance requirements failed with an inspectable reason. **Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer. **Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent. The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only. ## Proposed deterministic acceptance tests Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded. - The overview route explains the guide's purpose, audience, prerequisites, record ownership, and proposal lifecycle without claiming deployment. - Every step route contains actionable ordered work and identifies the record or receipt produced by each major step. - The tools route distinguishes named native surfaces from connected provider or production behavior. - The forms route includes source locator, provenance, revision, uncertainty, owner, and deadline fields. - The examples route contains at least three distinct scenarios: guided inquiry, source comparison, and lesson or study pathway construction; each example links claims to source records and marks uncertainty. - The qualification route states that a citation is not qualified merely because a source exists; the claim, locator, provenance, scope, and uncertainty must be inspectable. - The related-jobs route links Guided inquiry, Source comparison, Lesson pathways, Study records, and Uncertainty marking with distinct descriptions rather than duplicate doorway text. - A citation record can be traced through canonical ID, origin, source locator, provenance, revision, and lifecycle fields when those values are available. - A disputed or consequential conclusion can be placed in Needs review or Held state with a preserved receipt. - A user can complete the core form using keyboard navigation, visible labels, text alternatives for status, and non-color-only uncertainty states. - Invalid or incomplete submissions identify the missing field and preserve the draft rather than presenting it as qualified. - No route claims provider connection, database authority, customer indexing, publication, external send, or production qualification. ## Negative and held-state tests - A source title without a locator can create an unverifiable citation. - Paraphrase may be mistaken for quotation unless the distinction is explicit. - Multiple sources may appear to agree while relying on the same unsupported premise. - A citation can support a narrow claim but not the broader conclusion drawn from it. - Stale, revised, inaccessible, or conflicting source material can make an apparently precise citation misleading. - Agent-generated summaries may be mistaken for source evidence or human approval. - A local prototype route may be mistaken for a connected web feature or published documentation. - Medical, legal, financial, safety, or other consequential conclusions require qualified human review outside this guide. - Private notes, attachments, and held records must not be exposed through a public documentation route. - Missing deadlines or owners can leave uncertainty unresolved and make stale work appear current. ## Qualification claim boundary ### Potentially allowed only after the stated evidence - This is a proposed field guide for source-backed inquiry and uncertainty marking. - The source record identifies Socrates as the owner agent and lists Guided inquiry, Source comparison, Lesson pathways, Study records, and Uncertainty marking as related jobs. - The observed contract describes canonical IDs, source locators, provenance, revisions, lifecycle, tags, links, and attachments as record concepts. - The observed native contract describes local Notebook, PointGuard, approval, search, and agent-log surfaces with the stated prototype or indexed labels. - The guide can specify forms, workbacks, accessibility expectations, and acceptance tests for future implementation. ### Still held - That this guide is deployed or publicly published. - That Socrates is connected as a production provider or has authority to act externally. - That any app route is a connected web feature rather than a local prototype or index. - That a citation, conclusion, source comparison, lesson pathway, or study record is qualified merely because it was entered into a form. - That any database, customer index, publication workflow, external send, upload, protected storage, or provider effect is active. - That the listed related jobs or source reference contain more detail than supplied in the source 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` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: records` - `Observed native contract: deadlines` - `Observed native contract: pointguard` - `App route: /app/notebook/field-guides/` - `App route: /app/notebook/notes/` - `App route: /app/notebook/files/` - `App route: /app/notebook/projects/` - `App route: /app/notebook/approvals/` - `App route: /app/notebook/agent-logs/` - `App route: /app/notebook/search/` - `App route: /app/pointguard/`