Dry-Run Run of Show — Safety Shower MVP (Standards-Enforced)

Purpose

• Prove the pilot pattern end-to-end with human-in-the-loop, using real artifacts, while enforcing standards and the Infinity Method grammar.
• Outcomes: (a) Operator confidence; (b) Standards exercised and improved; (c) Metrics captured; (d) Revisions to prompts/templates logged.

Scope & Constraints

• Pilot scope: Safety Showers specification review; cohort ≤ 5 participants; non‑production.
• Human-in-the-loop: Required at all gates.
• Success bar (today): Demonstrate ≥70% time reduction potential and strict citation discipline.

Roles & Responsibilities

• Facilitator: keeps time, enforces grammar/standards, drives decisions.
• Operator (Proposals Engineer): drives CF01–CF03 actions, accepts/edits outputs.
• Orchestrator (PM/Lead): tracks open items (TQs/RFIs), ensures cross‑team handoff quality (CF04).
• Scribe: captures metrics, decisions, deltas to standards, and retro notes.
• Observer(s): ask “Where am I wrong?” questions and flag missed risks.

Pre‑Flight Checklist

• Environment
  • Open the 4 Projects (CF01–CF04) or equivalent workspaces.
  • Ensure these files are present: MR, Datasheet, Instrumentation Spec (or client baseline), Vendor Offer, relevant datasheets.
  • Load Prompt Packs: CF01_PromptPack_ADNOC.md … CF04_PromptPack_ADNOC.md.
• Standards & Templates
  • Matrix template opened: Compliance_Matrix_Template_Extended.xlsx (mirrors CSV header).
  • Deviation template: Deviation_Report_Template_ADNOC.md.
  • Deviations library: Past_Deviations_Library.md (ready to append accepted entries).
  • Evidence Pack checklist: Evidence_Pack_Checklist.md (open for EMC/Ex/Certs tracking).
• Governance
  • Confirm pilot constraints, participant roles, decision authority for this session.
• Method Grammar Setup
  • Value Pair (read aloud; 1 sentence).
  • Primary SEA intent(s) for today’s loop: CF01=Streamline; CF02–CF03=Enrich; CF04=Accelerate.
• Standards Toolkit (open these side‑by‑side)
  • 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
• Assert
  • profile_set == true (Client_Profile explicitly set)

Standards & Method Grammar Enforcement

• Value Pair at top of session; keep visible.
• SEA intent stated at the start of each CF.
• Frame steps as: Signal → Goal → Steps → Outcome.
• Add TOTE to each major step (Test→Operate→Test→Exit) with explicit pass/fail.
• Possible × Feasible: declare the limits; let AI go first, operator critiques.
• Quality bar: If you can’t cite it, you can’t claim it (filename + doc no + page/section/note).
• Naming: CF{##}_{Artifact}_{RFQ#}_v{N}; track Revisions timeline.
• Integrity & RFIs: list unreadable/unsupported files by exact path; generate RFI lines.
• CF03 guardrails (generic): Before exit, ensure Variant_Decision (if variant‑available phrasing detected), Power_Decision (spec vs offer mismatch), Environmental_Minima (evidence attached), and Regulatory_Declarations (attached or RFI) are satisfied for High‑Risk rows.

Agenda & Timeboxes

0–5: Orientation & Roles

• Read Value Pair; declare SEA intent(s); confirm success bar and metrics to capture.

5–15: CF01 Anchor & File Map (TOTE)

• Prompt: Anchor Hunt & File Map (confirm primary anchor). Output: Top‑3 anchors; counts; collections.
• Use: Client_Profile_Baselines (set profile), start Revision_Timeline_Log_Template.
• Produce: Confirmed primary anchor; initialized revision log.
• Pass: Anchor confirmed; File Map captured.
• Assert: profile_set == true

15–25: CF01 RFQ at a Glance

• Include: counts, anchors, cross‑refs, Complexity S/M/L, Missing Docs, Integrity issues, Revisions timeline, TQ tracker, Product group clustering.
• Use: Citation_Style, TQ_Tracker_Template (init), Revision_Timeline_Log_Template (update).
• Produce: One‑pager + updated TQ tracker + revision log.
• Pass: All fields populated with citations; Next Best Action set.
• Assert: tq_tracker_materialized true AND revision_log_materialized true

25–35: CF01 Completeness & Targeted RFI

• Run completeness check; draft RFI lines for gaps and unreadables (with exact paths).
• Use: Targeted_RFI_Template.
• Produce: Targeted RFI draft with citations and exact file paths.
• Pass: RFI ready if gaps exist; otherwise proceed.
• Assert: quantity_reconciliation_present == true

35–50: CF02 Extraction & Curator View

• Extraction of enforceable lines; capture T‑class/Area Class; categorize (Perf/Elec/HazArea/Materials/Testing/Docs/Integration/Painting/Signage/Alarms/Prequalification/Labeling).
• Curator view: operator Accept/Edit/Delete of High‑Risk subset.
• Use: Citation_Style, High_Risk_Keywords.
• Produce: Curated High‑Risk subset; populated matrix rows with citations.
• Pass: High‑Risk curated; matrix rows populated with citations; required/offer class/power fields considered.
• Assert: matrix_extended_fields_present true AND prefill_done true

50–60: CF02 Spec Cross‑walk (new)

• Action: For each High‑Risk row, record exact file path + section/line ranges (MR/spec/datasheet/offer) using Spec_Crosswalk_Template.
• Pass: All High‑Risk rows mapped with precise lines.

50–65: CF03 Status & Deviations

• Pre‑step: Stage Evidence Pack items (datasheets/CoCs) as Parked before status/deviation work; mirror EP Item_IDs in Decision_Notes.
• Status per row; per‑component hazardous‑area matrix → weakest‑link; detect dual power; IP minima.
• Draft deviations (pre‑seeded candidates); write back accepted deviations to Past_Deviations_Library.md.
• Use: Deviation_Report_Template_ADNOC, Past_Deviations_Library, CPQ_Mapping_Template.
• Produce: Decision table; deviation report draft; appended deviations library; CPQ mapping list.
• Pass: Decision table ready; deviation report draft coherent; library appended.
• Assert: haz_component_matrix_present true AND weakest_link_flag true AND cpq_list_present true AND appendix2_autopopulated true

65–75: CF04 Handoff & Proposal Skeleton

• Internal handoff with Revisions & Open Items; client packet skeleton with attachments manifest; prequalification annex if files exist.
• Use: Prequalification_Annex_Template, Quality_Documents_Manifest_Template, Datasheets_CoCs_Manifest_Template, Reference_List_Template.
• Produce: Technical Handoff Summary; client packet skeleton; annex manifest(s) if applicable.
• Pass: Handoff page complete; client skeleton acceptable.
• Assert: attachments_manifest_present true AND quality_docs_manifest_present true AND reference_list_present true AND appendix3_autopopulated true
• Step: Remap packet links to current repo paths (Trial Runs/<Project>/... and Reference Examples/<Project>/...); verify each link resolves.

75–80: Evidence Pack Gate (new)

• Action: Populate Evidence_Pack_Checklist (EMC declarations, Ex/IECEx certs, spec extracts). Ensure each Partially Compliant row references an Evidence Pack item.
• Pass: Evidence Pack complete OR items explicitly parked with filenames; Manifest mirrors filenames/status; CSV Decision_Notes include EP Item_IDs.

Appendices Closure Rule

• When closing Appendix 2/3 entries, include a brief “Why Closed” line with precise citations (Doc_No + page/line).

85–90: Retro (Standards & Grammar)

• What removed the most friction? Any standards confusing? What to tighten before next run?
• Use: CHANGELOG_MVP_Updates, Standards_Catalog.
• Produce: Logged standards deltas and changes for next rev.

Copy‑Paste Prompt Kit (per step)

• CF01 Anchor: “Scan filenames/first pages. Propose Top‑3 anchors with reasons and exact paths. Ask me to confirm primary anchor.”
• CF01 RFQ at a Glance: “Create RFQ at a Glance with counts, anchors, cross‑refs, Complexity S/M/L+rationale, Missing Docs, Integrity issues, Revisions timeline, TQ tracker, Product groups. End with Next Best Action.”
• CF01 RFI: “Draft a Targeted RFI for gaps and unreadables. Include exact contradictions/citations and exact file paths for unreadables.”
• CF02 Extraction: “Extract enforceable (‘shall/must’) requirements. Output Requirement_text (verbatim), Source_Doc/No/Page/Note, Interpretation; capture any T‑class/Area Class.”
• CF02 Categorize: “Assign Category; risk‑flag High for [IIC, Zone 1, IP65, IP55, IEC 61000/61326, IEC 62305, 30 years, 415 VAC 3Ph, Arabic/English, CCR indication, FAT/SAT/IFAT/CIT/SIT, AVL, A‑22 paint, Labeling].”
• CF02 Curator: “Show High‑Risk subset with 1‑line ‘Why High‑Risk’ and a Decision column (ACCEPT/EDIT/DELETE).”
• CF02 Export: “Populate extended matrix fields, including Client_Profile, Required/Offer T‑Class, Area Class, Power Supply.”
• CF02 Cross‑walk: “Create Spec Cross‑walk with exact file paths and line ranges for each High‑Risk row.”
• CF03 Status: “Propose status per requirement with Offer_Evidence_Doc + Page/Line; rationale in 1 line.”
• CF03 Haz‑Area Table: “Build per‑component hazardous‑area table; consolidate to weakest‑link status.”
• CF03 Deviations: “For each mismatch, draft Deviation with client requirement (verbatim+source), offered provision (quote+page/line), justification, impact, proposed client wording, CPQ implication. Assign Deviation_ID and 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.”
• CF03 Write‑back: “Append accepted deviations (ID + rationale + citations) to Past_Deviations_Library.md.”
• CF04 Handoff: “Create Technical Handoff Summary with counts by area class, compliance highlights, alarms & CCR, accepted deviations, open RFIs/TQs, CPQ notes; include Revisions & Open Items.”
• CF04 Client Skeleton: “Assemble client‑ready packet (cover, ToC, 200–300‑word executive summary tailored to EPC, attachments manifest). Include prequalification annex manifest if present.”

Decision Gates & Pass/Fail Criteria

• CF01 Gate: Proceed to Analysis if anchors confirmed, RFQ at a Glance complete, and gaps documented or RFIs drafted.
• CF02 Gate: Proceed to CF03 if High‑Risk curated and matrix traceability is intact.
• CF02 Cross‑walk Gate: All High‑Risk rows have precise file paths + line ranges.
• CF03 Gate: Proceed to CF04 if status/justifications are evidence‑backed and deviations drafted; write‑back complete.
• CF04 Gate: Handoff + client skeleton acceptable to Orchestrator; open items listed.
• Evidence Pack Gate: All Partially Compliant rows reference an Evidence Pack item; pack enumerated in Attachments.

Metrics Capture (use Metrics_Template.md)

• Files/pages processed; High‑Risk count; RFIs drafted; deviations proposed/accepted; dual power detected; weakest‑link area class; CPQ implications; open items; evidence completeness %; MR exact‑citation coverage %.

Facilitation Guide (maximize standards efficacy)

• Anchor the Value Pair and SEA at start; keep visible.
• Ask “Where am I wrong?” after each AI output; operators critique, not compose.
• Enforce citations; block acceptance without doc+page.
• Timebox decisions; perfect is the enemy of lovable.
• Capture standards deltas inline (scribe marks exact phrasing to update in Prompt Packs/templates right after the run).

Post‑Run Actions

• Update Prompt Packs and templates per decisions (small, high‑impact edits only).
• Append accepted deviations to Past_Deviations_Library.md.
• Update CHANGELOG_MVP_Updates.md and Cross-Examination-Report.md if new insights affect representativeness.
• File RFIs; schedule next dry‑run or demo.

Risks & Mitigations

• Unreadable/unsupported files → enumerate exact paths; RFI line + request alternate format.
• Client profile mismatch → set Client_Profile and baselines at start.
• Time overrun → defer deep debates to a follow‑up; log as open items.

References

• SOPs: MVP_Operator_SOPs.md
• Metrics: Metrics_Template.md
• Matrix checklist: Matrix_XLSX_Update_Checklist.md
• Annex: Prequalification_Annex_Template.md
• Governance: README section “Pilot constraints & governance”