v2.1 — what we redesigned and what's next · 2026-05-16

A one-page tour of the v2.1 pass — what got reviewed, how the advanced review worked, and what's open before production handoff.

1Where we are

The v2 admin tool has ten sections. Four were closed out in the previous phase. Five were closed out in this phase. Billing is held for its own pass.

DashboardPrevious
Student MgmtPrevious
Semester MgmtPrevious
ContentPrevious
SchedulingThis phase
TeachersThis phase
BillingHeld
ReportingThis phase
Comm.This phase
Admin/SysThis phase
Previous phase — closed in earlier walkthroughs This phase — closed in v2.1 Held — separate pass pending

2How the advanced review worked

Four phases, each with a small team of agents handing off to the next. Every artifact has a path on disk; every commit traces back through the chain.

A
Phase A Raw Audit
Spec-Fidelity Lens
Spec ↔ mockup compliance checks
Workflow Realist Lens
End-to-end admin task realism
Data-Model Lens
Data shape & schema gaps
Consistency Lens
Cross-screen vocabulary & patterns
21raw lens files · ~365findings, each carded with severity + reasoning

Filesdocs/admin-spec-v2-1/pre-review/_raw/

B
Phase B Depth Investigation
Lead
Cross-domain synthesis & themes
Data-Model Specialist
Deep schema shapes & migrations
Workflow Specialist
Deep workflow & state gaps
UX-Pattern Specialist
Deep UI pattern alignment
71chunked investigations · 5per-domain punch lists

Filesdocs/admin-spec-v2-1/pre-review/_depth/

C
Phase C Decision Packages
Lead
Cross-domain agenda & sequencing
Teacher converter
Assignment & placement decisions
Billing converter
Payment decisions (now held)
Reporting converter
Composition & revenue decisions
Admin converter
Issues, settings, audit decisions
Comm converter
Email, push & messaging decisions
5stakeholder-ready packages · ~200items, each with default direction

Filesdocs/admin-spec-v2-1/pre-review/decision-packages/

D
Phase D Implementation
Lead
Sequencing & QA across domains
Primitives
Shared components shipped first
Teacher impl.
Teacher screens to mockup
Reporting impl.
Reporting screens to mockup
Admin impl.
Admin screens to mockup
Comm impl.
Communication screens to mockup
~89items shipped as mockup code on branch v2.1/phase-d

Filessrc/pages/v2/ · src/data/

Deployed quranflow-admin.pages.dev/v2

Teacher Mgmt
Teachers list Teacher detail Assignment Criteria Manual Placement TA Reports Student Groups
Communication
Automation Emails Blast Emails Push Notifications Announcement Board Private Messages Communication Logs
Reporting
Student Report Active Enrollment Composition Revenue Breakdown Specific Reports Reporting Logs
Admin & System
Admins Settings Support Links Issue Queue Issue Detail
▸
Post-D ripple · documentation Screen-data bindings updated

For mockup changes that affect the data layer, a binding map was created — each changed surface is linked to the backend schema fields it touches. This gives the production build a direct line from screen to schema and makes future changes easier to track. The same pass surfaced 45 schema open questions for stakeholder review.

Filesdocs/admin-spec-v2-1/screen-data-bindings/

3What's open, and what's next

Two gates remain before production handoff — schema decisions on what we've shipped, and the Billing pass we haven't yet started.

45 open questions, by domain

13 · Communication
11 · Teacher Mgmt
8 · Admin
8 · Reporting
5 · Cross

Each item is a specific shape-of-data question raised against 01-schema.md:

enum values table shapes column nullability encoding choices

To be batched into a small set of decision packages for stakeholder review.

Billing & Payments Held

Billing is the one domain v2.1 hasn't touched. It's held for a dedicated pass because of the complexity of its Stripe integration — the surface spans:

subscriptions payment intents family plans coupons & scholarships refunds & disputes webhook reconciliation

Each interacts with Stripe state that the mockup can't fairly represent without modelling the real API. We're treating it as its own review pass once schema decisions land.

NEXT Resolve open questions → THEN Final mockup pass → AFTER Production handoff

Kamran · 2026-05-16 · v2.1 mockup lives at quranflow-admin.pages.dev/v2. Billing pass and schema decisions are the two remaining gates before production.