Preparing this page…
Your current navigation and account state stay available while the next page loads.
One session can carry hours of streamed output and far more history than the DOM should hold. Choose the transport, define what a resume means, and keep reading position and memory under control. This independent, original scenario is designed for ML / Inference Systems, Software / Infrastructure preparation. Work through the stages in order, explain each decision, and use the review dimensions to test whether the result remains defensible when constraints change.
A connection drops halfway through an answer. State what a reconnecting client may show, how much output is replayed, and how duplicates are suppressed when the server and the client both retry.
Do the resume rules survive retries from both ends?Markdown arrives faster than the layout can settle. Describe how you would render partial output without reflowing the whole transcript, and where you would deliberately wait.
Can the candidate trade instant rendering for a stable reading surface?The reader scrolls back while output continues, and the transcript is larger than the DOM can keep. Explain virtualization, scroll anchoring, and history paging as one design.
Can position, memory, and continuity stay consistent together?Use these checks after a first draft. They are review prompts, not six more questions to answer.
Clarifies goals, constraints, and ambiguous requirements.
Protects invariants and handles boundary conditions.
Identifies realistic failures and designs recovery paths.
Makes ownership and transitions explicit.
Provides enough visibility to diagnose and run the system.
Explains what is gained, lost, and intentionally deferred.
Use a different system, project, or situation and check whether the structure still produces a specific, defensible answer.