Product decisions, carried into software.
An employee request workflow, with a manager review queue and explicit rules for approvals, refusals, and failed actions.
Define the workflow
Employees submit requests. A manager reviews them, with the oldest requests first.
Decide the behavior
The operator approved the requirements with an addition: if manager sign-out fails, keep the session and review data intact.
Build and revise
The pipeline generated the backend and interface, then corrected a session-cookie defect during verification.
Check the result
Recorded browser checks exercised the application on desktop and mobile, including successful actions and failure paths.

Recorded outcome
Observed in the recorded run: an employee corrected a request without losing their note, and the application saved it once with an Open status.
Historical internal run. Built and tested locally, with maintainer interventions.
Scope, evidence & limitations
- Historical local experiment; no public deployment.
- Maintainer fixes and restarts were required. This is not a demonstration of zero developer intervention.
- The archived report contains a story-label mismatch; full accepted-requirement coverage is not claimed.
