Whiteboard Frameworks for Coherency: Debug Playbook

Debug playbook

Debug Playbook for Whiteboard Frameworks for Coherency explains how to reason from coherency invariant to measurable engineering decision.

1. Freeze reproducer and preserve transaction identity.

2. Find first invariant break, not loudest downstream alert.

3. Validate ownership-state transitions against protocol intent.

4. Test smallest reversible change and rerun key regressions.

Review template

STAFF REVIEW MEMO — Interview and Staff Execution / Whiteboard Frameworks for Coherency

1) Symptom
   - Tracked metric: interview rubric score and clarity feedback
   - Workload and mode: <explicitly named>
   - First failing evidence: <artifact ID and timestamp>

2) Mechanism hypothesis
   - Candidate mechanism: Strong explanations move from invariant to transaction sequence to measurable decision criteria.
   - Alternative explanations: ordering, backpressure, metadata staleness, or software misuse
   - Missing evidence required for decision: <list>

3) Action plan
   - Smallest reversible fix: <RTL, firmware, policy, or tooling>
   - Expected movement: <numeric trend expectation>
   - Risk of regression: performance, power, compatibility, or timing

4) Signoff gates
   - Primary artifact: whiteboard rubric + sample answer bank
   - Owners: hiring-panel, architecture, technical-leadership
   - Decision: fix now, bounded waiver, or escalate

Cache coherency deep dive

Cache coherence is a correctness contract across caches, interconnect, and software ordering.

Concept diagram

requester -> coherence fabric -> owner or memory -> state update

Metric graph

traffic mix across request, snoop, response, data

Metrics and artifacts to collect

• coherence latency

• invalidation rate

• retry rate

• stale-read incidents

Mini case study

Anchor debug to first stale read and the exact line state transition.

Debug branches

• Track ownership

• Track ordering

• Track evidence

Senior review question

Ask: what is the first line state transition that deviates, and which ordering rule does it break?

Key takeaways

• Tie every coherency claim to one cache line, one transaction identity, and one measurable counter.

• Keep proof artifacts from simulation and silicon replay aligned by address, state, and ordering event.

Common pitfalls

• Chasing bandwidth regressions without checking false sharing and line bouncing first.

• Assuming coherence correctness implies memory consistency correctness.

• Declaring closure without litmus, stress, and post-silicon replay evidence.