Note

// PURPOSE: Lightweight, sequential map for an LLM assistant to track progress across the MVP demo // STYLE: Minimal, checklist-first. Code-like comments for hints. Obsidian links for related assets.

Context (set once)

• Quote_Ref: {Q-XXXXX}
• Customer/EPC: {EPC}
• Client_Profile: {ADNOC|ARAMCO|SONATRACH|NMDC|Other}
• Time_Target_Mins: 90
• Efficiency_Target: ≥70% time reduction
• SEA_Intents: CF01=Streamline; CF02=Enrich; CF03=Enrich; CF04=Accelerate
• Core Files: MR, Datasheet, Instrumentation Spec (or client baseline), Vendor Offer, Datasheets
• Toolkit: Client_Profile_Baselines • Citation_Style • High_Risk_Keywords • Targeted_RFI_Template • TQ_Tracker_Template • Revision_Timeline_Log_Template • CPQ_Mapping_Template • Prequalification_Annex_Template • Quality_Documents_Manifest_Template • Datasheets_CoCs_Manifest_Template • Reference_List_Template • Evidence_Pack_Checklist • Spec_Crosswalk_Template

Progress (check as you go)

• 0.Init
• 1.CF01.AnchorAndMap
• 2.CF01.RFQAtAGlance
• 3.CF01.CompletenessAndRFI
• 4.CF02.Extraction
• 5.CF02.ExportMatrix
• 6.CF03.StatusAndHazardMatrix
• 7.CF03.DeviationsDraftAndWriteBack
• 8.CF03.CPQList
• 9.CF04.Handoff
• 10.CF04.ClientSkeleton
• 11.MetricsAndDecision
• 12.RetroAndLogging

Warning

// RULES: Always cite (filename + doc no + page/section/note). Block acceptance if missing. Use toolkit links.

0) Init

• Set Client_Profile via Client_Profile_Baselines.
• Open: Citation_Style, High_Risk_Keywords.
• Initialize: TQ_Tracker_Template, Revision_Timeline_Log_Template.
• Outcome: State set; trackers opened.
• Assert: profile_set == true

0a) Repo Path Remap (if migrating)

• Validate repo‑relative paths for Offer, Tank DS, Chiller DS, EPC specs/drawings under Reference Examples/<Project>/....
• Update packet links to Trial Runs/<Project>/CF0X/output/....
• Avoid legacy example-documentation-md paths.

1) CF01.AnchorAndMap

• Action: Run “Anchor Hunt & File Map”; propose Top‑3 anchors; confirm primary.
• Assert: anchor_confirmed == true
• Outcome: Primary anchor set; file map captured; revision log started.

2) CF01.RFQAtAGlance

• Action: Build one‑pager including counts, anchors, cross‑refs, Complexity, Missing Docs, Integrity issues, Revisions timeline, TQ tracker, Product groups.
• Assert: all_fields_present true AND all_claims_cited true AND tq_tracker_materialized true AND revision_log_materialized true
• Outcome: One‑pager ready; TQ + revision log updated.

3) CF01.CompletenessAndRFI

• If gaps OR unreadables:
  • Action: Draft RFI via Targeted_RFI_Template (include exact file paths for unreadables).
  • Outcome: RFI_ready == true
• Else: proceed.
• Assert: quantity_reconciliation_present == true

4) CF02.Extraction

• Action: Extract enforceable requirements (verbatim), capture Source_Doc/No/Page/Note; capture Area Class/T‑class; categorize; risk‑flag via High_Risk_Keywords.
• Auto‑trigger: If ingress (IP66/IP67 per IEC 60529) or EMC standards (IEC 61000/IEC 61326/NAMUR) are detected in specs and offer/datasheets lack explicit evidence, pre‑populate RFI‑IP / RFI‑EMC with exact spec lines.
• Auto‑trigger (generic): Detect variant‑available phrasing (e.g., “available as … or …”, “optional”, “non‑… version”), power phrases (voltage/phase/frequency) and regulatory/third‑party declarations (“certificate”, “declaration”, “register”, “test report”) referenced but not attached; pre‑populate targeted RFIs accordingly.
• Curate: Show High‑Risk subset; operator ACCEPT/EDIT/DELETE.
• Assert: high_risk_curated == true
• Outcome: Curated rows with citations.

5) CF02.ExportMatrix

• Action: Populate extended matrix fields (Client_Profile, Required/Offer T‑Class/Area Class/Power Supply, etc.).
• Assert: matrix_traceability_intact true AND matrix_extended_fields_present true AND prefill_done == true
• Outcome: Matrix ready for CF03.

5a) CF02.SpecCrosswalk (new)

• Action: Record exact file path + line ranges (MR/spec/datasheet/offer) for each High‑Risk row using Spec_Crosswalk_Template. Use fields: Section_Title + Page/Line_Range.
• Assert: crosswalk_complete == true (all High‑Risk rows have precise lines; missing sources retained with RFI note)

6) CF03.StatusAndHazardMatrix

• Pre‑step: Stage EP items (datasheets/CoCs) as Parked; mirror EP Item_IDs in Decision_Notes.
• Action: For each row, propose Status_Suggestion with Offer_Evidence_Doc + Page/Line; build per‑component hazardous‑area table; compute weakest_link_class; detect dual_power.
• Variant dependency check: If offer text includes hazardous‑area variants (e.g., flameproof vs non‑flameproof), require explicit BOM selection and protection concept (Ex d/e/tb) per component.
• Power supply alignment: Compare site baseline vs offer supply; propose variant/deviation or transformer if mismatch.
• Assert: each_row_has(status && evidence) true AND haz_component_matrix_present true AND weakest_link_flag true AND variant_locked true AND power_decided true AND environmental_minima_met_with_evidence true AND regulatory_declarations_attached_or_RFI == true
• Outcome: Decision table scaffolded.

7) CF03.DeviationsDraftAndWriteBack

• Action: Draft deviations (what differs, why acceptable, impact, proposed wording, CPQ implication); assign Deviation_ID; link to matrix.
• Pre‑consider: scald valve w/ cooler; flowswitch→proximity; JB Ex e vs chiller Ex d; painting exclusions; heated booth optionality; dual power; AVL.
• Write‑back: Append accepted deviations to Past_Deviations_Library.
• Assert: appendix2_autopopulated true AND cpq_list_present true
• Outcome: Deviation report draft + library updated.

8) CF03.CPQList

• Action: Produce grouped list by subsystem via CPQ_Mapping_Template.
• Outcome: CPQ pre‑entry list ready.

9) CF04.Handoff

• Action: Create Technical Handoff Summary (counts by area class, compliance highlights, alarms & CCR, accepted deviations, open RFIs/TQs, CPQ notes; Revisions & Open Items).
• Assert: attachments_manifest_present true AND quality_docs_manifest_present true AND reference_list_present == true
• Outcome: Handoff one‑pager complete.

10) CF04.ClientSkeleton

• Action: Assemble client‑ready skeleton (cover, ToC, 200–300‑word executive summary tailored to EPC, attachments manifest). If applicable, prepare annexes via Prequalification_Annex_Template, Quality_Documents_Manifest_Template, Datasheets_CoCs_Manifest_Template, Reference_List_Template.
• Assert: appendix3_autopopulated == true
• Outcome: Client packet skeleton ready.

10a) EvidencePackGate (new)

• Action: Populate Evidence_Pack_Checklist (EMC/EMI declarations; Ex/IECEx/ATEX certificates; spec extracts). Ensure every Partially Compliant row references an Evidence Pack item.
• Assert: evidence_pack_complete true OR explicitly_parked true
• Assert: csv_is_source_of_truth == true (no schema changes)

11) MetricsAndDecision

• Action: Fill Metrics_Template (files/pages, high‑risk, RFIs, deviations proposed/accepted, open items, dual power, weakest‑link class, CPQ notes, evidence completeness %, MR exact‑citation coverage %).
• Check: efficiency >= Efficiency_Target ?
• Assert: annexes_count_recorded true AND prefilled_vs_rfi_tracked true
• Decision: ready_to_demo == true | false (list standards edits if false)

12) RetroAndLogging

• Action: Log changes in CHANGELOG_MVP_Updates; update Standards_Catalog if new templates/edits.
• Schedule: Next run/demo.

Failure

// FALLBACKS: // - Unreadables: enumerate exact paths; convert or RFI. // - Profile mismatch: reset baseline; re-run affected checks. // - Time overrun: park deep dives; log as open items.