Add system design: trip lifecycle orchestration

[gardusig]

Goal

Model end-to-end trip or job lifecycle state machines: events, sagas, timeouts, and compensating actions. This note lives in gardusig/interviewing as interview prep, not production runbooks.

Acceptance criteria

• New markdown under system-design/concepts/ or system-design/architecture/ (pick the closer fit) and linked from the relevant folder README.md index when appropriate.
• Covers: requirements, scale or traffic assumptions, core APIs or events, data model sketch, and failure modes or retries.
• Optional mermaid diagram if it clarifies data or control flow.
• Stays shareable: no confidential employer internals, customer PII, or unreleasable numbers—use rounded hypothetical loads.

---

Source issue title (before rename)

Trip Lifecycle Service

---

References

• (none yet — add papers, docs, or diagrams when drafting.)