Mission 2 Service Quality Evaluation Lab Guide
📥 Lab input
- •
day5_signup_flow.md(screen flow spec)
💾 Lab output
- •
edge-case-analysis.md(exception scenario report)
1. Story and lab background
On the first night after a startup successfully launches its MVP, an unexpected server alarm goes off. Two users pressed the pay button at the same time for the same booking slot; both payments succeeded, but the database was overwritten by the last payer, and the first payer's booking data was lost. (A concurrency control exception)
Turn readability (Information Display), control accessibility, error recovery and flow efficiency into objective scores based on international Usability Standards.
In this lab, you give Codex the full screen design and user flow, and build a quality report (Usability Evaluation) with overall scores, painful design debts and an action plan to fix them.
2. Learning goals
- Detect logical design flaws in the defined table schema and foreign key structure.
- Derive weak points such as low control accessibility (3.0/5.0), poor error recovery and long flows, and turn them into an action plan.
- Prepare responses such as Soft Delete (logical delete) to guard against Hard Delete on account deletion.
🛠️ Follow-along lab guide
- Create the lab file: press the download button below and save
day5_signup_flow.mdin theautomation/folder. - Hand the check to Codex: send the **Codex request prompt** below in the Codex Client prompt box and build.
- Check the response design: review whether the report sets specific DB improvements like double-booking prevention (distributed lock/Unique constraint) and Soft Delete flag design.
Download lab materials
Codex request prompt
Mission 02 Prompt
Based on the provided day5_signup_flow.md spec, score each of 1) information readability, 2) control accessibility, 3) error recovery and 4) flow efficiency out of 5, and build a service quality evaluation (Usability Evaluation) with an overall score, strengths and painful areas to improve.
4. Example output
Codex dissects the schema logic as a white box and derives serious exception scenarios like these.
| Item | Detailed diagnosis and score | System impact | Overall improvement plan (Action Plan) |
|---|---|---|---|
| Information readability (3.5/5.0) | Two users pay for the same session slot at the same time, both are judged successful, and they're mapped twice | Critical | Create a composite UNIQUE constraint on the DB booking table or use a Redis distributed lock |
| Control accessibility (3.0/5.0) | Hard Deleting a User record with payment history breaks the foreign key and breaks daily sales settlement queries | Critical | Change the table design to Soft Delete (logical delete) with an is_deleted column and deletion time |
| Error recovery (2.5/5.0) | External PG payment approval succeeds, but our DB insert rolls back because of a network failure and the payment record vanishes | Normal | Wrap the payment in a distributed transaction (Saga Pattern) and run a batch check script for unconfirmed payments |