Scenario: Missing Isolation - Interview Scenario

Scenario

A low-power regression passes functional checks in ON mode, but data corruption appears when one producer domain powers down. Interface receivers sample unconstrained values during OFF windows.

OBSERVED METRIC
Mismatch count on powered-down boundary interfaces and X-propagation rate during domain-off windows.

45-MINUTE INTERVIEW FLOW
0-5: define context and KPI
5-15: classify first failing LP boundary
15-25: identify proving artifact packet
25-35: propose bounded fix with owner
35-45: define validation matrix and rollback

Common traps to avoid

• Checking scoreboards first without proving clamp behavior at boundary crossings.

• Assuming isolation intent is correct because UPF compiles without semantic warnings.

• Treating random waveform X bursts as simulation noise instead of protocol-impacting errors.

Scenario debrief

Score response quality on transition-boundary classification, evidence chain, owner assignment, and rollback-safe closure.

intent -> transition behavior -> evidence -> owner action -> closure

escape risk and closure trend

Debrief prompts

1. Which low-power phase boundary failed first and how is it proven?

2. Which failure class best explains the symptom: setup, transition, boundary, retention, or X-prop triage?

3. Which bounded fix and validation matrix close risk with minimal collateral change?

Key takeaways

• Tie each LPV claim to a concrete transition boundary and one proving artifact.

• Prefer minimal reversible fixes with explicit owner and rollback criteria.

Common pitfalls

• Treating power-aware failures as random before boundary classification.

• Waiving X-prop failures before proving impact and root cause.

• Declaring closure without deterministic replay across key modes.