Multi-Platform Parity

This page is generated from the canonical slide file in the repository and the supporting references listed below.

Open wceu-2026/slides/slide-08-multi-platform-parity.md

• Tool-specific manifests with shared capability intent.
• Platform parity reduces behavioural surprises.
• Registry and scoped validation support staged rollout.

• Mention parity as a DevEx and risk-control practice.
• Clarify that parity is never perfect but can be managed explicitly.

• Keep layout simple: title + 3 bullets + one visual zone.
• Use minimal visuals (one icon, one screenshot, or one simple diagram only).
• Avoid dense process diagrams, nested callouts, and complex animation.
• Keep on-slide text short (roughly 25-40 words total where possible).
• Use high contrast and consistent spacing; prioritise readability over decoration.