Person/Elon Musk/First-Principles Framework/1 - Question every requirement

• Every requirement should have a name attached to it. Never accept "it's always been done that way."
• Trace every architectural decision to its original author and reason; validate assumptions against current business needs.
• Distinguish hard constraints (laws of physics, real business rules) from soft constraints (preferences, legacy patterns).