SOFTWARE ARCHITECTURE DECISION WORKSHEET Space Office | https://www.spaceoffice.ai/blog/software-architecture Decision title: Status (proposed / accepted / superseded): Human owner: Decision date: 1. Context Critical user journey: Business rule the design must preserve: Users and external dependencies: Data that crosses each boundary: Operational and staffing constraints: 2. Quality scenarios Trigger | Expected response | Verification method | Owner Concurrent booking | Unavailable downstream dependency | Unauthorized access | Backup restore | Change to an important rule | 3. Alternatives Option | Structure and owner | Benefit | Trade-off | Unverified assumption A | B | 4. Decision and consequences Chosen structure: Data authority and write controls: Expected behavior in the main failure case: New monitoring or recovery responsibilities: Required evidence and location: Unresolved assumptions and owner: 5. Review Revisit condition: Date and evidence of human acceptance: Supersedes / superseded by: Worked example: Use a transactional store to protect one active room reservation per slot. Run email delivery separately from the visitor's request. Review concurrent booking, failed delivery, access, and recovery before approval.