Decision Log

Decision Capture Model

Every customer answer must map to a clarification Question ID. Every decision must keep an owner, status, affected baseline areas, and evidence or meeting reference.

Decision Statuses

• Open
• Answered
• Accepted Assumption
• Rejected Assumption
• Deferred
• Requires Follow-Up
• Superseded
• Closed

Decision Fields

• Decision ID
• Question ID
• Decision Statement
• Customer Answer
• Decision Status
• Decision Owner
• Decision Date
• Affected Requirement IDs
• Affected Feature IDs
• Affected Interface IDs
• Affected Security Capability IDs
• Affected Architecture Elements
• Baseline Impact
• Follow-Up Required
• Evidence Reference

Baseline Impact Classes

• Confirms requirement
• Rejects assumption
• Refines interface
• Refines security capability
• Refines architecture element
• Adds new open question
• No baseline impact

Decision Log

Generated: 2026-06-17T15:29:25+00:00

No customer answer baseline has been ingested yet.

Open Decision Register

Generated: 2026-06-20T16:56:36+00:00

All entries are open until a customer answer is captured and mapped through the post-workshop delta process.

Decision: D-001

• Question ID: CQ-BOUNDARY-01
• Decision statement: Confirm disposition for CQ-BOUNDARY-01 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00006
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-002

• Question ID: CQ-BOUNDARY-04
• Decision statement: Confirm disposition for CQ-BOUNDARY-04 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00146
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-003

• Question ID: CQ-BOUNDARY-06
• Decision statement: Confirm disposition for CQ-BOUNDARY-06 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00175
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-004

• Question ID: CQ-BOUNDARY-16
• Decision statement: Confirm disposition for CQ-BOUNDARY-16 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00317
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-005

• Question ID: CQ-BOUNDARY-19
• Decision statement: Confirm disposition for CQ-BOUNDARY-19 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00338
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-006

• Question ID: CQ-BOUNDARY-23
• Decision statement: Confirm disposition for CQ-BOUNDARY-23 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00480
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-007

• Question ID: CQ-BOUNDARY-24
• Decision statement: Confirm disposition for CQ-BOUNDARY-24 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00488
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-008

• Question ID: CQ-BOUNDARY-28
• Decision statement: Confirm disposition for CQ-BOUNDARY-28 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0051
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-009

• Question ID: CQ-BOUNDARY-31
• Decision statement: Confirm disposition for CQ-BOUNDARY-31 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00634
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-010

• Question ID: CQ-BOUNDARY-38
• Decision statement: Confirm disposition for CQ-BOUNDARY-38 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00866
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Blocks architecture baseline
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-011

• Question ID: CQ-BOUNDARY-02
• Decision statement: Confirm disposition for CQ-BOUNDARY-02 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_SEC_0040
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-012

• Question ID: CQ-BOUNDARY-03
• Decision statement: Confirm disposition for CQ-BOUNDARY-03 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_SEC_0041
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-013

• Question ID: CQ-BOUNDARY-05
• Decision statement: Confirm disposition for CQ-BOUNDARY-05 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: Req.ID-Description-6.22.1
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-014

• Question ID: CQ-BOUNDARY-07
• Decision statement: Confirm disposition for CQ-BOUNDARY-07 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00190
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-015

• Question ID: CQ-BOUNDARY-08
• Decision statement: Confirm disposition for CQ-BOUNDARY-08 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00246
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-016

• Question ID: CQ-BOUNDARY-09
• Decision statement: Confirm disposition for CQ-BOUNDARY-09 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00250
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-017

• Question ID: CQ-BOUNDARY-10
• Decision statement: Confirm disposition for CQ-BOUNDARY-10 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00272
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-018

• Question ID: CQ-BOUNDARY-11
• Decision statement: Confirm disposition for CQ-BOUNDARY-11 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00278
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-019

• Question ID: CQ-BOUNDARY-12
• Decision statement: Confirm disposition for CQ-BOUNDARY-12 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00279
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-020

• Question ID: CQ-BOUNDARY-13
• Decision statement: Confirm disposition for CQ-BOUNDARY-13 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00284
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-021

• Question ID: CQ-BOUNDARY-14
• Decision statement: Confirm disposition for CQ-BOUNDARY-14 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00292
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-022

• Question ID: CQ-BOUNDARY-15
• Decision statement: Confirm disposition for CQ-BOUNDARY-15 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00294
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-023

• Question ID: CQ-BOUNDARY-17
• Decision statement: Confirm disposition for CQ-BOUNDARY-17 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00335
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-024

• Question ID: CQ-BOUNDARY-18
• Decision statement: Confirm disposition for CQ-BOUNDARY-18 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00337
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-025

• Question ID: CQ-BOUNDARY-20
• Decision statement: Confirm disposition for CQ-BOUNDARY-20 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00343
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-026

• Question ID: CQ-BOUNDARY-21
• Decision statement: Confirm disposition for CQ-BOUNDARY-21 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00378
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-027

• Question ID: CQ-BOUNDARY-22
• Decision statement: Confirm disposition for CQ-BOUNDARY-22 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00420
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-028

• Question ID: CQ-BOUNDARY-25
• Decision statement: Confirm disposition for CQ-BOUNDARY-25 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00492
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-029

• Question ID: CQ-BOUNDARY-26
• Decision statement: Confirm disposition for CQ-BOUNDARY-26 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0041
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-030

• Question ID: CQ-BOUNDARY-27
• Decision statement: Confirm disposition for CQ-BOUNDARY-27 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0049
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-031

• Question ID: CQ-BOUNDARY-29
• Decision statement: Confirm disposition for CQ-BOUNDARY-29 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00563
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-032

• Question ID: CQ-BOUNDARY-30
• Decision statement: Confirm disposition for CQ-BOUNDARY-30 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00588
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-033

• Question ID: CQ-BOUNDARY-32
• Decision statement: Confirm disposition for CQ-BOUNDARY-32 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00652
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-034

• Question ID: CQ-BOUNDARY-33
• Decision statement: Confirm disposition for CQ-BOUNDARY-33 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0135
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-035

• Question ID: CQ-BOUNDARY-34
• Decision statement: Confirm disposition for CQ-BOUNDARY-34 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00704
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-036

• Question ID: CQ-BOUNDARY-35
• Decision statement: Confirm disposition for CQ-BOUNDARY-35 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00785
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-037

• Question ID: CQ-BOUNDARY-36
• Decision statement: Confirm disposition for CQ-BOUNDARY-36 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00843
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-038

• Question ID: CQ-BOUNDARY-37
• Decision statement: Confirm disposition for CQ-BOUNDARY-37 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00859
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-039

• Question ID: CQ-BOUNDARY-39
• Decision statement: Confirm disposition for CQ-BOUNDARY-39 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00932
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-040

• Question ID: CQ-BOUNDARY-40
• Decision statement: Confirm disposition for CQ-BOUNDARY-40 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00947
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-041

• Question ID: CQ-BOUNDARY-41
• Decision statement: Confirm disposition for CQ-BOUNDARY-41 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-00996
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-042

• Question ID: CQ-BOUNDARY-42
• Decision statement: Confirm disposition for CQ-BOUNDARY-42 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-01013
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-043

• Question ID: CQ-BOUNDARY-43
• Decision statement: Confirm disposition for CQ-BOUNDARY-43 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ-AUTO-01056
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: System boundary / item definition
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-044

• Question ID: CQ-INTERFACE-01
• Decision statement: Confirm disposition for CQ-INTERFACE-01 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: req-6.3
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: External Interfaces / vehicle network boundary
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-045

• Question ID: CQ-DIAG-01
• Decision statement: Confirm disposition for CQ-DIAG-01 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0051
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-046

• Question ID: CQ-DIAG-02
• Decision statement: Confirm disposition for CQ-DIAG-02 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0051
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-047

• Question ID: CQ-DIAG-03
• Decision statement: Confirm disposition for CQ-DIAG-03 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0051
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-048

• Question ID: CQ-DIAG-04
• Decision statement: Confirm disposition for CQ-DIAG-04 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0305
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-049

• Question ID: CQ-DIAG-05
• Decision statement: Confirm disposition for CQ-DIAG-05 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0345
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-050

• Question ID: CQ-DIAG-06
• Decision statement: Confirm disposition for CQ-DIAG-06 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0346
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-051

• Question ID: CQ-DIAG-07
• Decision statement: Confirm disposition for CQ-DIAG-07 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0348
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-052

• Question ID: CQ-DIAG-08
• Decision statement: Confirm disposition for CQ-DIAG-08 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0349
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-053

• Question ID: CQ-DIAG-09
• Decision statement: Confirm disposition for CQ-DIAG-09 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0093
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-054

• Question ID: CQ-DIAG-10
• Decision statement: Confirm disposition for CQ-DIAG-10 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0295
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-055

• Question ID: CQ-DIAG-11
• Decision statement: Confirm disposition for CQ-DIAG-11 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0134
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-056

• Question ID: CQ-DIAG-12
• Decision statement: Confirm disposition for CQ-DIAG-12 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0136
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-057

• Question ID: CQ-DIAG-13
• Decision statement: Confirm disposition for CQ-DIAG-13 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0208
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-058

• Question ID: CQ-DIAG-14
• Decision statement: Confirm disposition for CQ-DIAG-14 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0215
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-059

• Question ID: CQ-DIAG-15
• Decision statement: Confirm disposition for CQ-DIAG-15 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0217
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-060

• Question ID: CQ-DIAG-16
• Decision statement: Confirm disposition for CQ-DIAG-16 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0218
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-061

• Question ID: CQ-DIAG-17
• Decision statement: Confirm disposition for CQ-DIAG-17 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0220
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-062

• Question ID: CQ-DIAG-18
• Decision statement: Confirm disposition for CQ-DIAG-18 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0221
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-063

• Question ID: CQ-DIAG-19
• Decision statement: Confirm disposition for CQ-DIAG-19 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0222
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Decision: D-064

• Question ID: CQ-DIAG-20
• Decision statement: Confirm disposition for CQ-DIAG-20 in the RFQX baseline.
• Decision status: Open
• Decision owner: Joint
• Affected requirement IDs: REQ_UDS-0003
• Affected feature IDs: To be determined from post-workshop impact.
• Affected interface IDs: To be determined from post-workshop impact.
• Affected security capability IDs: To be determined from post-workshop impact.
• Affected architecture elements: Diagnostic access boundary / Secure Diagnostics
• Baseline impact: Can remain as tracked assumption
• Follow-up required: yes
• Evidence / meeting reference: Pending workshop minutes.

Unmatched Answers

Unmatched Customer Answers

• None.

New Questions From Answers

New Questions From Customer Answers

• None.