# Source-grounding convention

## Requirements

Every factual claim in a source-grounded deliverable must be supported by the supplied evidence. Preserve quantities, units, qualification, and uncertainty. “Not completed” does not establish “in progress.” Distinguish your inference from a fact stated by the source.

A citation must let a reader locate the actual supporting passage. Identify the source file and a verified heading, entry identifier, exact short quotation, or verified line number. Prefer a clickable Markdown link, but an unambiguous file reference is sufficient; retrievability, not link syntax, is the requirement. By default use a short exact quotation or a source-provided entry identifier. Example: `notes.md — “Seven teams completed onboarding; five have not.”` Use line numbers only after inspecting a numbered source view; never reconstruct positions from memory or count selected excerpts as whole-file lines. With a shell, `nl -ba` or `grep -n` can establish actual positions. Without numbered evidence, use the quotation or identifier option. Do not cite an unrelated passage.

Before claiming fulfillment, check each claim against its cited passage. This is a normal verification step; it does not substitute for independent review when the program requires one. Report missing support or correct the draft within scope.