Risk Register

Active risks tracked for the Daanaa engagement. Each risk is assessed for severity, likelihood, and impact, with defined mitigations.

Summary

ID	Risk	Severity	Status
R01	No internal champion identified	High	Open
R02	IP classification unresolved	High	Open
R03	Engineer resistance to new tooling	Medium	Open
R04	Scope creep into full PDP redesign	Medium	Open
R05	Data access constraints	Medium	Open
R06	Udi single-thread dependency	Medium	Open
R07	ISO/automotive scope mismatch	Low	Open

High Severity

R01 — No Internal Champion

Without a named internal champion at Daanaa (someone below CEO level who drives adoption day-to-day), the pilot has no operational sponsor. This is the single highest-risk item for the engagement.

Mitigation: Identify champion candidates during discovery interviews (Jim, Mark, Ehsan, or Javad are candidates from artifacts). Champion identification is a gate-1 KPI.

R02 — IP Classification Unresolved

Daanaa handles sensitive power electronics IP, customer NDAs, and potentially automotive-safety-related data. Without a clear IP classification scheme (foreground / background / customer-confidential), the substrate cannot be scoped for data handling.

Mitigation: Raise IP classification as a discovery interview topic. Map the classification scheme before pilot design. Default conservative: all data stays in Daanaa environment.

Medium Severity

R03 — Engineer Resistance

Engineers may resist "yet another tool" if the substrate is perceived as adding work rather than removing it. The confirm-rate on auto-drafted summaries is the key adoption signal.

Mitigation: Design the pilot for Achievement 1 (Engineer's Lens) — value must be visible to the engineer within the first week.

R04 — Scope Creep into Full PDP

Udi's initial framing mentions ISO compliance, knowledge base, and automated documentation — scope that could expand well beyond a focused pilot. If we try to do everything at once, we deliver nothing.

Mitigation: Gate-2 explicitly defines pilot scope. Everything not in scope is documented as future phases, not rejected.

R05 — Data Access Constraints

If Daanaa's security policies, hosting rules, or AI/LLM constraints prevent the substrate from accessing the data it needs, integration becomes impossible or requires expensive workarounds.

Mitigation: Map constraints in the discovery constraint-envelope section. Identify hard constraints vs. negotiable preferences early.

R06 — Udi Single-Thread Dependency

All communication currently routes through Udi (CEO). If Udi becomes unavailable, the engagement stalls. CEOs have competing priorities.

Mitigation: Identify and establish relationships with additional contacts during discovery. Champion identification partially addresses this.

Low Severity

R07 — ISO/Automotive Scope Mismatch

If Daanaa requires 26262 (automotive functional safety) or AEC-Q100 compliance and the substrate doesn't address those standards, the engagement may have a gap between what's promised and what's delivered.

Mitigation: Confirm ISO standards in scope during discovery. 9001 is confirmed; automotive standards TBD. Scope the pilot for 9001 first, extend later.