Q92 · Chapter 12 · Saves & first release
Cut complexity, not the core
Which three features could we postpone without damaging the first version?
PartialNew in Edition 3
The direction
If scope grows, cut system complexity before cutting the core loop. A system only needs enough implementation to demonstrate one meaningful interaction; the full ecosystem can remain open for later contributors or later iterations. Three exact postponed features have not been named yet.
Recorded as: Partial / scope principle
The original question’s prompt
This helps protect the core loop when production grows.
Examples in a prompt are not decisions unless the answer chooses them.Still to decide in this chapter
Safe stopping points, save transfer, migration of old progress and three named postponed features remain open.
