MICROSERVICES EXTRACTION WORKSHEET Space Office | https://www.spaceoffice.ai/blog/microservices 1. Problem and baseline User-visible problem: Representative period and workload: Baseline with units and denominator: Simpler options tested and observed results: 2. One boundary Capability and service owner: Record that stays authoritative: Existing writer and proposed writer: Contract version, identifiers, and required fields: Stable operation key and duplicate policy: What users see when the new dependency is unavailable: How old versions and cancellations are handled: 3. Test and release evidence Test environment and allowed data: Case | Expected result | Observed result | Evidence Duplicate delivery | Provider accepted, worker crashed | Out-of-order cancellation | Provider unavailable | Incompatible event version | Delayed queue catches up | 4. Pilot and recovery Routing rule and designated writer per operation: Baseline and stop thresholds: What staff monitor and who can pause: Cutoff and rollback procedure: How to identify delivered, pending, and ambiguous operations: Who reviews ambiguous sends before replay: Recovery drill result and evidence: 5. Human decision Owner: Decision and date: Approved next action: Scope and outstanding conditions: Worked example: Keep the pottery workshop reservation and payment authoritative in the booking application. Separate confirmation delivery only if the bounded pilot addresses the observed problem and pending work can be reconciled safely.