Linear Walkthrough

A walkthrough is not a reference document or a summary. It is a guided tour: it takes the reader from the beginning to the end, building understanding progressively, with each section setting up the next.

Before You Start

Clarify two things — ask if not obvious from context:

1. Audience

• Product / non-senior technical: Focus on what and why. Use analogies. Explain jargon when it appears. Keep implementation detail light unless it directly clarifies intent. Think: "would a smart PM who codes a little follow this?"
• Engineering / senior technical: Full detail. Implementation specifics, edge cases, architectural decisions, tradeoffs.
• Mixed or unknown: Default to PM-level narrative, with optional "Under the Hood" callout blocks for deeper technical content that more technical readers can explore.

2. Intent / downstream use

Why is this walkthrough being created? This shapes depth and emphasis: