boq-audit

Inputs

• boq-file — Path to the BOQ file (CSV, XLSX, or PDF). Must include item description, unit, quantity, rate, amount columns.
• project-context — One-line project description (sector, scope, region) — sharpens flag prioritisation.
• drawings-ref — Path or summary of architectural drawings (RCP, plans) used to cross-reference geometry.
• notebook-alias — NotebookLM alias for the matter — must contain the client's spec book, accepted brand list, regional price list, contract, and any prior-project BOQ history. Per `provenance-standard.md`, grounding is required, not optional. If no alias exists, stop and ask before proceeding.
• bid-files — Comma-separated paths to 2+ contractor bid files (CSV/XLSX/PDF).
• sov-template — Optional path to a custom SOV category map; defaults to the bundled SOV template.
• notebook-alias — NotebookLM alias for the matter — must contain the tender package, contractor bid documents, and reference price list. Per `provenance-standard.md`, grounding is required. If no alias exists, stop and ask before proceeding.
• audit-report — Path to a prior audit report from the audit-boq route.
• boq-file — Path to the BOQ; volatile items are auto-detected (steel, cement, copper, tariff-exposed imports).
• index-source — Index reference (default — local statistics agency CPI for construction materials).
• project-context — Project description — sector, scope, regions, scale.