Episode 2 — Onramp

Purpose

Reduce time to flow by tightly coupling to the current saliency landscape and providing a clear, self-contained launch plan that does not rely on this chat thread.

Set Saliency Context
- Rationale: Aligns Episode 2 work with the most representative examples and stakeholder priorities.
Confirm Method Asserts
- Rationale: Guarantees consistency and quality gates from Episode 1 carry forward.
Define Target Outcome for Episode 2
- Rationale: Keeps focus on a measurable, proposal-quality end state.
Launch Checklist
- Rationale: Shortens time-to-action by making setup deterministic.

Representative examples: Q-32859 - NMDC - Ruwais, Q-21699 - Saipem COMP2
End-state reference: Example proposals with complete appendices and manifests
Stakeholder goals: Proposal-quality assembly with strict citations, minimal RFIs, and high prefill coverage

profile_set == true
quantity_reconciliation_present == true
matrix_extended_fields_present true AND prefill_done true
haz_component_matrix_present true AND weakest_link_flag true
cpq_list_present == true
attachments_manifest_present true AND quality_docs_manifest_present true AND reference_list_present == true
appendix2_autopopulated true AND appendix3_autopopulated true (operator review)

Produce a near client-ready proposal packet for one selected example (recommend Q-32859), including:
- Fully populated executive summary
- Completed annexes: Appendix 2 (deviations), Appendix 3 (clarifications), Quality Docs manifest, Reference List
- Prefill coverage ≥80% for enforceable and component claims; RFIs only for genuine unknowns

Open runbooks: Safety Shower MVP, MVP Sequencing
Open Standards Toolkit: Standards_Catalog
Select example: Q-32859 (NMDC) or Q-21699 (Saipem)
Set Client_Profile per Client_Profile_Baselines
Execute CF01→CF04 with asserts; use templates to prefill from offers/datasheets before drafting RFIs
Assemble final packet with: Prequalification_Annex_Template, Quality_Documents_Manifest_Template, Reference_List_Template, Appendix2_Technical_Deviation_List_Template, Appendix3_Technical_Clarification_List_Template
Record metrics: Metrics_Template; update: CHANGELOG_MVP_Updates

All required references and templates are within the vault; no external chat context required.
The runbooks include explicit asserts to guide quality gates during execution.

Proceed with Episode 2 by opening the runbook and selecting the example. Follow the asserts to completion.