Citation Style — Reference

Requirements & Deviations

• Always include: Source_Doc, Doc_No, Page, Clause/Note.
• Preferred format (inline): “{Doc Name} ({Doc_No}), p.{Page}, {Note/Clause}”
• Offers: “{Offer_Doc}, p./line {Offer_Page_or_Line}”

Examples

• Datasheet reference: “Project Datasheet (2-MM5173-40-SPE-1907-00), p.2, Note 7”
• Instrumentation spec: “ADNOC Instrumentation Specification (4422-JK-SE-000000180001_00), p.12, Sec 4.3”
• Offer: “Q-32859-1 (Hughes Offer), line 154”
• Evidence Pack in Decision_Notes: “EP-001 Hughes_EMC_Declaration_IEC61000_61326_NAMUR_NE21.pdf — Parked” | “EP-002 Chiller_ATEX_IECEx_CoC_IIB_T4.pdf — Attached”
• Repo-relative path example: “Reference Examples/Q-32705 - Saipem COMP3/Chiller Unit Datasheet Zone-1.md, lines 64–66”
• Section_Title + Page/Line example: “200-51-IN-SPC-00021_00 (Instrumentation), Sec Outdoor Ingress, lines 1721–1725”
• Variant‑available example (generic): “Offer Datasheet (Doc_No), Availability note, lines X–Y: ‘Available as [Variant A] or [Variant B] — please specify preference’.”
• Referenced‑but‑missing declaration example (generic): “Quality Pack (Doc_No), Sec [Title], lines X–Y — declaration/register referenced but not attached (RFI raised).”

Matrix Fields

• Source_Section_or_Note: free text (e.g., Note 7; Sec 4.3)
• Offer_Page_or_Line: number/string (e.g., 154; 2-11)

Guardrails

• Verbatim in Requirement_text; no summaries.
• No claim without a citation; block acceptance if missing.
• Use repo-relative paths; avoid legacy placeholders.
• Prefer precise line ranges (re-locate exact line before external share if approximate).