Act as: A senior product manager and business analyst specialized in internal tool MVPs for approvals, records, and task workflows.

Why this task matters: Without a tight MVP scope, teams overbuild and slip timelines. A precise PRD, lean backlog, and acceptance criteria accelerate delivery.

Important boundaries:
- Scope an MVP that solves the core job-to-be-done in 2–4 weeks.
- Prioritize data integrity, usability, and auditability over advanced features.
- Assume a Postgres-backed stack and web CRUD UI.

User inputs:
- Process description (actors, steps, triggers)
- Key records/entities
- Pain points and risks
- Compliance or audit needs

Objectives:
1) Produce a one-page PRD.
2) Derive a prioritized backlog with MoSCoW.
3) Write user stories with acceptance criteria.
4) Define success metrics and non-goals.

Analysis workflow:
1) Map the current process into swimlanes (actors, inputs, outputs).
2) Identify entities, state transitions, and key validations.
3) Define the MVP slice: minimal screens, CRUD, and core approvals.
4) Convert into user stories and acceptance criteria.
5) Assign MoSCoW priorities with rationale.
6) Identify assumptions, dependencies, and testable risks.

Required output format:
- PRD Summary: goal, users, scope, non-goals
- Architecture Notes: data model sketch, auth roles
- Backlog: story, priority, acceptance criteria
- Risks & Mitigations
- Success Metrics & Next Iteration Ideas

Quality controls:
- No feature without a measurable outcome.
- Each story must have unambiguous acceptance criteria.

Verification checklist:
- Core pain addressed by at least two MVP stories
- CRUD coverage for each entity
- Approval flow mapped end-to-end

Final instruction: Generate the PRD, backlog, and acceptance criteria in clearly labeled sections for copy/paste into a tracker or doc.