Build workflow

Requirements, roles, dependencies, entities, acceptance criteria, assumptions, and gaps are documented.

Next: Keep the scope log as the source of truth.

Public landing page, dashboard preview, layouts, responsive tokens, timezone, trusted hosts, and lazy-loading protection are in place.

Next: Reuse the layouts as real modules arrive.

Institution, access, academic, people, admission, finance, examination, CMS, notification, audit, and system table inventory is migrated.

Next: Expand generic metadata tables with feature-owned columns before each module goes live.

Done: login, logout, password reset/change, email verification boundary, protected dashboard, active-account enforcement, throttling, failed-attempt tracking, login history, role/permission relationships, access views, profile/photo, admin boundary tests, session security, policies, and 2FA.

Next: Done.

Institution profile, campuses, sessions, terms, classes, sections, subjects, routines, rooms, and teacher assignments.

Next: Depends on authentication and scoped authorization.

Student, guardian, staff, admission review, merit, approval, ID generation, and enrollment lifecycle.

Next: Use enrollment as the source for attendance, fees, and exam candidates.

Attendance entry/corrections, invoices, manual payments, proofs, approvals, receipts, gateways, refunds, and reconciliation.

Next: Manual payment works.

The result pipeline is operational: institutions select the configured exam/class, enter or import their own student marks, and the system applies catalog-aware validation, two-paper GPA aggregation, fourth-subject bonus, persistence, audit history, guarded publication, and authorized withdrawal for corrections.

Next: Institution adds verified marks, then Submit → Verify → Approve → Publish; authorized controllers can withdraw a published result with a reason.

Candidate policies, attempt limits, effective dates, status flags, uniqueness constraints, re-scrutiny versions, approval, recalculation, correction request UI, and catalog integrity tests are implemented.

Next: Replace baseline dates with any future circular amendments when officially confirmed.

Core panels, organized admin navigation, CMS and reporting are available; regression coverage and production hardening continue alongside the board rules work.

Next: Run full regression after the ruleset is connected to all endpoints.