A cleaned text extract from the T1985 archive, shown for source transparency. This is one of the documents T1985 Intelligence draws on. Restricted, financial, and personal material is excluded from public view.
Keturah Portfolio: Coordination Matrices & Design Cycle Workflows Document ID: KPF-WF-20260110 Effective Date: January 10, 2026 Subject: Detailed Workflows, Coordination Matrices, and Communication Protocols for Keturah Portfolio Projects Issued by: Manus AI, on behalf of Keturah Leadership 1. PURPOSE This document provides the detailed operational workflows and coordination matrices that supplement the main Operational Directive (KPF-OD-20260110). Its purpose is to provide granular, actionable guidance on how the appointed entities will interact, review submissions, and manage the flow of design information to ensure seamless project execution. 2. MASTER PROJECT COORDINATION (RACI) MATRIX This RACI matrix defines the roles for key activities across the portfolio. R=Responsible, A=Accountable, C=Consulted, I=Informed. Activity Keturah Team CITIC CMCU / HORZIEN NEB / DEWAN MAG RSP Strategic Direction & Final Approval A I I I I I Overall Project Delivery & Timeline A R C C C C Lead Coordination of All Parties I A/R C C C C New Design Development (Plot 14, 1B) C A R C C N/A RSP Design Submission (Plots 16 & 12) I A C C C R Technical Review & Verification of Submissions I A/R R C R I On-Site Supervision & Quality Control A C C R C I Budget & Cost Management A R C C I I Contractor & Sub-consultant Management I A/R I I I I Reporting to Keturah Leadership A R I I I I 3. DESIGN CYCLE WORKFLOWS 3.1. Standard Design Cycle Workflow (Plot 14, 1B Mansion) This workflow applies to projects where the CITIC-led consortium is responsible for design from SD to IFC. ``mermaid graph TD A[Start: Approved Concept] --> B{Design Phase Kick-off}; B --> C[CMCU/HORZIEN: Draft Design Package (e.g., SD)]; C --> D{Internal Review Cycle}; D -- Comments --> C; D -- Coordinated Draft --> E[CITIC: Consolidate & Verify]; E --> F{Specialist Review}; F -- Input --> G[MAG: Review & Comment]; G -- Comments --> E; F -- No Input Needed --> H{Formal Submission to Keturah}; E --> H; H --> I[Keturah Team: Review & Approve]; I -- Approved --> J{Advance to Next Phase (e.g., DD)}; I -- Comments --> E; J --> C; ` Workflow Steps: 1. Design Drafting: CMCU/HORZIEN produce the draft design package for the current phase. 2. Internal Review: The draft is circulated internally within the CMCU/HORZIEN/NEB/MAG consortium for initial coordination. 3. Lead Coordinator Verification: CITIC consolidates all input and verifies the package for completeness and compliance. 4. Specialist Review: MAG provides specialist review where required. 5. Formal Submission: CITIC formally submits the verified and consolidated package to the Keturah Team. 6. Client Approval: The Keturah Team provides final approval or comments for revision. 7. Advancement: Upon approval, the cycle repeats for the next design phase (DD, TD, IFC). 3.2. RSP Submission Review Workflow (Plots 16 & 12 Mansions) This workflow is mandatory for all submissions from RSP. `mermaid graph TD A[RSP: Submits Design Package] --> B[CITIC: Log Submission & Initiate Review]; B --> C{Parallel Verification Cycle}; C --> D[CMCU/HORZIEN: Technical & Design Intent Review]; C --> E[NEB: Constructability & Supervision Review]; C --> F[MAG: Specialist Discipline Review]; D -- Comments --> G{CITIC: Consolidate All Comments}; E -- Comments --> G; F -- Comments --> G; G --> H[CITIC: Issue Consolidated Review Report to RSP]; H -- Revisions Required --> A; G -- No Major Issues --> I{CITIC: Formal Verification}; I --> J[CITIC: Submit Verified Package to Keturah Team]; J --> K[Keturah Team: Final Approval]; K -- Approved --> L{RSP Proceeds to Next Stage}; K -- Comments --> J; ` Workflow Steps: 1. Submission: RSP submits their design package to CITIC. 2. Review Initiation: CITIC logs the submission and distributes it for parallel review to CMCU, HORZIEN, NEB, and MAG. 3. Parallel Verification: Each consultant reviews the submission against their area of expertise. 4. Comment Consolidation: CITIC gathers all comments and compiles a single, consolidated review report. 5. Report Issuance: CITIC issues the report to RSP. If revisions are required, RSP must resubmit, and the cycle restarts. 6. Formal Verification: If the submission is deemed acceptable, CITIC issues a formal Verification Certificate. 7. Client Submission: Only after a Verification Certificate is issued will CITIC submit the package to the Keturah Team for final approval. 3.3. 1B Mansion Concept Completion Workflow `mermaid graph TD A[Start: 70% Concept] --> B{Keturah Team: Facilitate Workshops}; B --> C[Talal / Khazal / Mark Brian: Provide Input & Direction]; C --> D{Design Charrette}; D --> E[CMCU/HORZIEN: Live-document & Sketch Revisions]; E --> F{Review & Refine}; F -- Iterate --> C; F -- Finalized --> G[Keturah Team: 100% Concept Approval Sign-off]; G --> H{Activate Standard Design Cycle}; H --> I(See Workflow 3.1); `` Workflow Steps: 1. Workshops: The Keturah Team facilitates intensive design workshops with key stakeholders. 2. Live Documentation: CMCU/HORZIEN architects and designers participate in the workshops to provide live sketching and immediate documentation of ideas. 3. Iteration: The process iterates rapidly until all stakeholders are aligned. 4. Formal Sign-off: The Keturah Team provides a formal, written 100% approval of the final concept. 5. Activation: Upon sign-off, the project immediately transitions to the Standard Design Cycle Workflow (3.1) for progression through SD, DD, TD, and IFC. 4. CONSOLIDATED SUPERVISION FRAMEWORK (KETURAH'S CREEK) Lead Supervision: NEB / DEWAN Framework Principles: 1. Single Point of Contact: NEB/DEWAN will act as the single point of contact for all on-site supervision matters, reporting to the Keturah Team. 2. Unified Standards: A single set of quality, safety, and reporting standards will be applied across all Keturah's Creek projects. 3. Proactive, Not Reactive: The supervision team will focus on proactive quality assurance and defect prevention, rather than reactive defect identification. 4. Direct Interface with CITIC: The NEB/DEWAN site team will interface directly with the CITIC construction management team. 5. Design Compliance: The primary role is to ensure the work executed by CITIC and its subcontractors is in strict compliance with the IFC documents and design intent. Reporting Structure: • Daily: Site inspection reports submitted to CITIC and Keturah Team. • Weekly: Consolidated progress and quality report, including a risk register and look-ahead schedule. • Monthly: Executive summary report presented to the Steering Committee. End of Document