The Spark is the request or problem that kicks off architectural discovery. A request to add a button or change a database value may sound like a quick coding task; first, clarify what the user should do, where it belongs, and whether it changes or adds a flow. Then pause and ask why. section 1.5.2
Sometimes the spark reveals more than the original task: an order-validation bug or new payment option can expose an OrderProcessor that is doing too many jobs. The bug may be the trigger, but the deeper design problem is what deserves investigation. section 3.5.2
Use the spark to begin a repeatable decision process:
- Clarify the request, then investigate its reasons and constraints before sketching options or recording a decision. section 1.5.2 section 2.1
