[F4] Product MVP definition — Stages 0–5 (Profile→Finding)

[anmolg1997]

Workstream: product-ux | Estimate: 5d normal → 2.5d AI-assisted | Phase: 2

Why

B1-B3 need a face: invite users, assign roles, manage tenant settings.

Scope

• User CRUD/invites, role assignment, tenant settings page

Acceptance criteria

• Admin can onboard a new reviewer without touching the DB

---

From the enterprise-readiness backlog (codebase audit + pharma/GxP research + tooling survey, 2026-06-12).

[akhileshap9]

Stage	What happens	Who will be involved	What the agent will perform
Stage 0: Product / Project Onboarding	A product, project, process, or audit scope is onboarded. The reusable review baseline is created for that product/project. This baseline defines the review items, document requirements, rules, and checklist that can be reused every time an audit is performed.	Team Lead or Site Lead	Reads uploaded SOPs, templates, protocols, historical audit reports, CAPAs, deviations, validation documents, and regulatory commitments. Generates draft review items, checklist rules, evidence requirements, risk indicators, document mappings, and ownership suggestions.
Stage 1: Audit Planning	A specific audit event is created using the approved product/project baseline. Scope, departments, timelines, due dates, and audit objectives are defined.	Team Lead, Audit Reviewer, Site Lead	Pre-populates checklist from the approved baseline, identifies high-risk areas, suggests priority review areas, estimates audit readiness effort, and highlights historical risk areas.
Stage 2: Evidence Collection	Required documents and evidence are uploaded against the review items. Document Owners provide batch records, SOPs, audit trail reports, training records, deviation records, CAPA records, validation reports, and other evidence.	Team Lead, Document Owner	Classifies uploaded documents, maps evidence to checklist items, detects missing documents, validates document type, checks version/date relevance, and flags gaps before review.
Stage 3: Automated Audit Analysis	The system performs automated audit checks before human review. It compares submitted evidence against the checklist, rules, and expected document trail.	Audit Reviewer	Checks completeness, signatures, approvals, missing attachments, version issues, date mismatches, audit trail gaps, open deviations, CAPA linkage, training gaps, calibration validity, and rule violations. Generates risk scores and draft observations.
Stage 4: Human Review	The Audit Reviewer validates AI findings. If evidence is acceptable, the item is approved. If something is missing or unclear, the reviewer sends it back to the Document Owner for clarification or correction.	Audit Reviewer, Document Owner, Team Lead	Summarizes the evidence, explains detected gaps, highlights source references, recommends accept/reject/clarification actions, drafts review comments, compares resubmitted evidence with the original issue, and updates review status.
Stage 5: Finding Management	Confirmed gaps are formally logged as audit findings or observations. Findings are categorized by severity, process area, department, product/project, and risk.	Audit Reviewer, Team Lead, Site Lead	Converts confirmed issues into structured findings, suggests severity, maps finding to evidence, checks whether it is a repeat issue, groups similar findings, and recommends whether CAPA is required.
Stage 6: CAPA Management	Serious, repeated, or systemic findings are assigned to a CAPA Owner. The CAPA Owner performs root cause analysis, defines corrective/preventive actions, uploads closure evidence, and submits for review.	CAPA Owner, Audit Reviewer, Team Lead	Suggests possible root causes, drafts corrective and preventive action recommendations, recommends closure evidence, tracks due dates, checks whether submitted CAPA evidence addresses the finding, and flags weak responses.
Stage 7: Site Readiness Review	Site-level audit readiness is reviewed. Leadership checks whether the site is ready for internal, customer, or regulatory audit.	Site Lead, Team Lead, Audit Reviewer	Generates readiness score, summarizes open risks, highlights overdue items, shows department-wise gaps, identifies critical blockers, and prepares leadership summary.
Stage 8: Audit Pack / Inspection View	Approved evidence is organized into a controlled audit pack or inspection room. Only finalized and approved records are exposed for audit presentation.	Team Lead, Audit Reviewer, Site Lead, Auditor / Inspector View	Creates audit evidence pack, builds traceability from checklist to evidence, hides drafts/internal comments, prepares auditor-facing summaries, and enables controlled search over approved evidence.
Stage 9: Audit Closure & Learning Loop	Audit is closed after findings, CAPAs, evidence, and responses are completed. Lessons learned are used to improve future review baselines.	Team Lead, Audit Reviewer, CAPA Owner, Site Lead	Summarizes audit outcomes, captures recurring gaps, updates risk patterns, recommends checklist improvements, and suggests new rules for the product/project audit profile.

[akhileshap9]

For MVP, let's only consider till stage 5.
Considering that we would only be dealing with:

• team lead
• reviewer
• document owner
• site head
  for now
  The rest of the folks like CAPA owner, auditor, or inspector. We will onboard them as we keep on adding new workflows or stages as we progress or as we mature the product over time.

[anmolg1997]

Redefined — this is the product anchor. F4 (originally 'Admin UI: users/roles/tenants') now hosts the MVP product definition: the 10-stage AutoAudit lifecycle, MVP = Stages 0–5, 4 roles, 9 screens, defined in planning/VISION.md, MVP.md, ROADMAP.md, JOURNEY_MAPS.md. The old admin-UI scope (users/roles/tenants) becomes part of Sprint-1 multi-user auth. The MVP build is tracked in the new Phase-0 + Sprint 1–5 issues.

See planning/RECONCILIATION.md (PR #156) for the full product↔engineering mapping.

[anmolg1997]

Status -> Done. DEFINITION deliverable only. The Product MVP definition is complete: 5 feature specs (PROFILES / PLANNING_EVIDENCE / ANALYSIS_REVIEW / FINDINGS / NOTIFICATIONS), the AuroPro Design System brand contract, and 8 module mockups (each with a chosen variant + design-review done), all landed on product-planning. Two design steps remain: End-to-End Journey Assembly & Review (which folds in Notifications), then a Final Cross-Module Design Review (MODULE_CHECKLIST lines 25-26). This item is the DEFINITION deliverable only — the BUILD is tracked under the sprint items #158-#162 on branch product-mvp and is NOT closed by this flip. (If #131 is instead intended as the umbrella MVP-product epic per RECONCILIATION §3, it should stay In Progress / convert to an EPIC linked to #158-#162 rather than Done — confirm with Akhilesh; this update assumes definition-only.)