[VIEW] agent=Engineering Integration Lead | scenario_id=35 | rounds=20

--- Round 0 ---
[R0.1] Cybersecurity & Compliance Lead (speak, public): To determine whether we can safely proceed with the 60-day controlled pilot of the cloud-hosted 'digital thread' collaboration enclave, I'd like to understand the expected data footprint and collaboration tempo. Can you share some insights on how intensive the collaboration will be and what kind of data we'll be handling?
[R0.2] Engineering Integration Lead (speak, public): The pilot needs to support 28 concurrent users with file checkout under 30 seconds. We're expecting one integration drop per week, with a package size of 18 GB. Our model repository is currently 3.2 TB and grows by 120 GB monthly. We also have a tight schedule tied to the Critical Design Review on July 1, 2026, meaning the pilot must start by May 6, 2026.
[R0.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to understand the scale and growth of the technical footprint you've described. For the collaboration enclave, can you confirm if there are any cross-border data access requirements or hidden assurance timing constraints that could impact our contract structure or risk reserve? Additionally, I can share that we have a management reserve of $85,000 available for unexpected costs, with a pilot budget ceiling of $420,000 NTE and 2,100 labor hours.

--- Round 1 ---
[R1.1] Cybersecurity & Compliance Lead (speak, public): To assess the cybersecurity and compliance readiness for the pilot, I'll need to confirm that the proposed collaboration enclave meets our minimum control set. Based on your description, the expected data footprint is substantial, with 3.2 TB growing by 120 GB monthly, and the collaboration tempo is intensive with 28 concurrent users and weekly 18 GB integration drops. Given this scale, I'd like to highlight that we'll need to ensure the enclave adheres to our requirements, such as MFA for all users, 90-day audit log retention, and 15-minute session timeout. Additionally, we'll need to treat the engineering models as CUI with ITAR technical data, with a 5-year retention policy. Can you confirm if the proposed cloud-hosted solution meets these requirements or if there are any plans to achieve compliance?
[R1.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements you've outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set, such as MFA for all users, 90-day audit log retention, and 15-minute session timeout? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R1.3] Contracts & Program Controls Manager (speak, public): To assess contractual feasibility and financial control, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the Engineering Integration Lead's description, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance, and also share the contracting timeline to determine when access can be turned on?

--- Round 2 ---
[R2.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll outline a few key considerations. First, we need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Additionally, given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. I'd like to highlight that we have an internal CMMC Level 2 gap count with 7 open gaps, 2 of which are high priority, and we're targeting closure within 45 days. Furthermore, our SSP update workload for the pilot boundary involves refreshing 12 security artifacts, with a draft SSP update due by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R2.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I'll need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R2.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on.

--- Round 3 ---
[R3.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R3.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R3.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 4 ---
[R4.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R4.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R4.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 5 ---
[R5.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R5.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R5.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 6 ---
[R6.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R6.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R6.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 7 ---
[R7.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R7.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R7.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 8 ---
[R8.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R8.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R8.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 9 ---
[R9.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R9.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R9.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 10 ---
[R10.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R10.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R10.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 11 ---
[R11.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R11.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R11.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 12 ---
[R12.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R12.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R12.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 13 ---
[R13.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R13.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R13.3] Contracts & Program Controls Manager (speak, public): To assess whether the pilot is contractually feasible and financially controlled, I need to confirm if there are any cross-border data access requirements or hidden assurance timing constraints. Based on the information shared, the scale is substantial with 3.2 TB growing by 120 GB monthly. I've shared our management reserve and pilot budget ceiling. Can you confirm if the proposed cloud-hosted solution meets our minimum control set and if there are any plans to achieve compliance? Additionally, I'd like to know the contracting timeline to determine when access can be turned on. Specifically, I'm concerned about meeting our contract modification schedule, with the mod request due on April 22, 2026, and signature target on May 3, 2026.

--- Round 14 ---
[R14.1] Cybersecurity & Compliance Lead (speak, public): To ensure we're on track with our cybersecurity and compliance requirements, I'll summarize the key considerations. We need to confirm that the proposed cloud-hosted solution meets our minimum control set, including MFA for all users, 90-day audit log retention, and 15-minute session timeout. Given the substantial data footprint and intensive collaboration tempo, we must treat engineering models as CUI with ITAR technical data and adhere to a 5-year retention policy. Additionally, we're working on closing 7 internal CMMC Level 2 gaps within 45 days and updating our SSP for the pilot boundary by April 30, 2026. Can you both confirm if these requirements can be met and if there are any plans to achieve compliance?
[R14.2] Engineering Integration Lead (speak, public): To ensure we can meet the cybersecurity requirements outlined, I need to understand the operational security guardrails and data-handling expectations that will shape our workflows. Can you confirm if the proposed cloud-hosted solution has been assessed against our minimum control set? Additionally, I'd like to know the contracting timeline to determine when access can be turned on and if there are any upcoming assurance events or commercial terms that could indirectly constrain user onboarding or tooling choices.
[R14.3] Contracts & Program Controls Manager (leave, public): 

--- Round 15 ---
[R15.1] Cybersecurity & Compliance Lead (leave, public): 
[R15.2] Engineering Integration Lead (leave, public): 
[R15.3] Contracts & Program Controls Manager (leave, public): 

--- Round 16 ---
[R16.1] Cybersecurity & Compliance Lead (leave, public): 
[R16.2] Engineering Integration Lead (leave, public): 
[R16.3] Contracts & Program Controls Manager (leave, public): 

--- Round 17 ---
[R17.1] Cybersecurity & Compliance Lead (leave, public): 
[R17.2] Engineering Integration Lead (leave, public): 
[R17.3] Contracts & Program Controls Manager (leave, public): 

--- Round 18 ---
[R18.1] Cybersecurity & Compliance Lead (leave, public): 
[R18.2] Engineering Integration Lead (leave, public): 
[R18.3] Contracts & Program Controls Manager (leave, public): 

--- Round 19 ---
[R19.1] Cybersecurity & Compliance Lead (leave, public): 
[R19.2] Engineering Integration Lead (leave, public): 
[R19.3] Contracts & Program Controls Manager (leave, public): 

