--- status: accepted --- # Initial MVP scope Phase 1 scope revision: the user subsequently narrowed the first release to enrollment, subjects, class schedules and COR, with direct Teacher entry of final grades now confirmed. [Phase 1 MVP scope](../phase-1-mvp-scope.md) takes precedence over the broader grading and Learning Material plans below. Grading periods, assessment score entry and automatic grade calculation are deferred. Existing code and academic history are preserved. The first release will focus on junior high school, senior high school, and college. Elementary and vocational education are intended future additions, so the design should allow additional school levels without building their complete workflows into the MVP. This keeps the first release manageable while preserving the school's intended expansion path. Each school deployment has one database shared by its branches. Each student has one school-wide record, with enrollments and academic records carrying their branch context and staff access restricted to authorized branches. Detailed internal branch-move workflows are deferred. Planning focuses on the recurring enrollment, teaching, final-grade, and next-period enrollment cycle described in [Enrollment to Final Grades and Next Period](../enrollment-to-final-grades.md). Enrollment applications will initially be entered by school staff. Student or parent self-service enrollment is deferred so the MVP can first establish the school's eligibility checks, approval process, and COR issuance. The registrar has final authority to finalize enrollment and authorize COR release. Finalization requires the required academic and financial clearances to be satisfied, including any properly authorized financial payment arrangement. Phase 1 also permits Registrar enrollment amendments after COR issuance, with a required reason, renewed eligibility/capacity/timetable/financial checks and a new COR Version retaining the original and audit history. Preserve official grades, prior subject attempts and existing records. Once a Student's final subject grade is finalized, the Registrar cannot drop or switch that subject's class; other ungraded subjects remain amendable. Teacher grade corrections preserve history and do not reopen the Registrar's drop/switch access. An outstanding previous balance holds enrollment by default. A designated finance approver may authorize a documented payment arrangement recording the approver, reason, and payment terms. The registrar cannot independently bypass financial clearance. For the revised Phase 1 release, Finance Staff manually marks each enrollment Cleared or On Hold under the school's current-term payment conditions. Registrar finalization requires valid Cleared status. An unsettled past balance also requires the Finance Approver's documented arrangement; a Finance Staff clearance cannot waive that approval. Retain decision and approval audit history. Automatic tuition assessment/payment-rule calculation is outside this minimal clearance workflow. Subject prerequisites will be defined in curriculum setup and checked during enrollment against the student's academic record. Checks use finalized passing subject results or approved transfer credits; draft grades remain provisional. An unmet prerequisite blocks enrollment in the dependent subject. No prerequisite override is available to any user role in the MVP. The design must allow a future approved exception process to be added without replacing the prerequisite rules; that process and its approvers are deferred. The exact rules for satisfying prerequisites and broader progression rules, including high school promotion, remain open decisions. College enrollment supports irregular students, including retakes and eligible subjects from different year levels. Staff start with subjects suggested by the assigned curriculum and may adjust the student's subject load while prerequisite checks remain enforced. The MVP permits retaking an already passed or approved-credited subject with a non-blocking warning. Existing academic, timetable and financial checks still apply, and each new attempt preserves the previous results and credit history. An earlier valid pass continues to satisfy the curriculum requirement and prerequisites even if a later retake is failed; the later attempt retains its actual result. Any future GPA/GWA treatment of repeated grades is a separate school-policy decision. The MVP also supports crediting subjects completed at other schools. Staff record the source school, external subject, grade, and supporting transcript, then map the subject to its equivalent in the student's assigned curriculum. Each mapping requires explicit approval before the credit counts toward curriculum requirements or satisfies prerequisite checks; an uploaded transcript alone remains pending review. The registrar approves these mappings in the MVP through a dedicated Approve Transfer Credits permission, which can be assigned to another evaluator later. Approved transfer credits satisfy the corresponding curriculum requirements and prerequisites, but their source grades are retained separately and excluded from the school's computed GWA/GPA. The subject is displayed as Credited. Converting source-school grades for inclusion in local averages is deferred until the school defines a conversion policy. Junior high school, senior high school, and college each have their own configurable grading scale and passing rules. Supported scales include percentage grades such as 75, 80, and 85, and numeric ratings such as 1.0 and 2.0. Grade meaning, direction, and passing outcomes follow the assigned policy; specific scale bounds, cutoffs, and conversion mappings have not yet been set. The school configures these during setup, and teachers automatically use the grading policy assigned to their classes. Prerequisite checks use the resulting passing outcome. For a later phase, the school defines reusable grading templates with categories and weights per school level or subject. Teachers add graded items and record scores using the template assigned to their class. That future gradebook calculates grades from assessment scores for Teacher review and editing, including projects, activities, recitations, quizzes and exams. This is excluded from the revised Phase 1 scope. Recorded exam scores and the assessment gradebook are deferred from Phase 1, along with online exam authoring, online Student attempts and automatic marking. In the later gradebook phase, calculated results can be converted into official grades through school-defined conversion tables. The school supplies the mappings; no universal percentage-to-rating equivalency is assumed. Exact formulas, conversion order and adjustment rules remain to be clarified for that phase. Confirmed Phase 1 manual final-grade entry uses the school's official grade scale and passing outcomes without requiring assessment calculation or calculated-score conversion. Each subject teacher has final say on grades for students in their assigned subject or class. The teacher's Finalize Grades action makes those grades official immediately, and departments can track submission status. Ordinary editing locks after finalization, but the subject teacher may use a separate Correct Grade action with a required reason. History preserves the previous grade, corrected grade, teacher, and date. The registrar handles enrollment, COR release, and transfer-credit approvals, and uses finalized academic results for enrollment eligibility checks. Learning Material uploads/links and lesson or module authoring are deferred from Phase 1. Student admission documents, transcripts, profile photos and private record files remain separate enrollment/Student-record features. Students have individual logins to a simple mobile-friendly portal for their own enrolled subjects, schedules, COR and official final results. Academic records are view-only for Students. Enrollment applications remain entered by Enrollment Staff or the Registrar. The MVP is a responsive website for desktop, tablet and phone browsers; native mobile apps remain deferred. Learning Materials belong to a later phase. The development baseline is Laravel 13 with React, TypeScript, and Inertia, backed by PostgreSQL, in one repository. The official Laravel AI SDK is the planned integration for future AI capabilities; AI-powered product features are outside the MVP. Developer tooling such as Laravel Boost is optional and is not a product requirement. The proposed role dashboards, operational reports, and permission bundles are described in [Dashboards Reporting and Access](../dashboards-reporting-and-access.md). These proposals preserve the agreed teacher, registrar, finance, student, and branch boundaries; exact role bundles and report scope remain to be confirmed. System-wide audit logs are mandatory in the MVP across every module. Coverage includes enrollment and COR actions, financial entries and arrangements, curriculum and grading-policy changes, assessment scores and calculated or adjusted grades, finalization and corrections, transfer credits, learning materials, accounts and permissions, and security and sensitive-record access or export events. Audit entries identify the actor, action and outcome, affected record and scope, time, changed fields where applicable, and any required reason. Logs are stored in the database, with no audit-log viewer or application-user browsing access in the MVP. Application users cannot edit or erase audit history. Retention periods remain to be agreed.