Orbit Edu 100-Point Pastoral Conduct Scoring, Commendations & Detention Proctoring SOP

1. System Topology & Architectural Ingress

The Pastoral Conduct and Discipline engine is centralized within apps/api/src/modules/edu/services/discipline.service.ts and operated via the administrative console at apps/edu/src/app/admin/discipline/page.tsx. It provides real-time conduct dossier tracking, disciplinary incident ingestion, collision-checked detention assignments, and automated clearance gate holds.

+----------------------------------------------------------------------------------------------------+
|                                    PASTORAL CONDUCT CONTROL PLANE                                  |
|                                                                                                    |
|   +-----------------------+     +-----------------------+     +--------------------------------+   |
|   |   INCIDENT INGRESS    |     |   CONDUCT SCORE LOG   |     |   DETENTION PROCTOR ENGINE     |   |
|   |   - Tardiness Truancy |     |   - Baseline: 100 Pts |     |   - After-School Sessions      |   |
|   |   - Classroom Disrupt |     |   - Demerit Penalty   |     |   - Timetable Collision Check  |   |
|   |   - Academic Malpract |     |   - Commendation Add  |     |   - Faculty Proctor Assign     |   |
|   |   - Uniform Breach    |     |   - Standing Tier     |     |   - Service Completion Sign-off|   |
|   +-----------+-----------+     +-----------+-----------+     +---------------+----------------+   |
|               |                             |                                 |                    |
|               +----------------------+      |      +--------------------------+                    |
|                                      |      |      |                                               |
|                                      v      v      v                                               |
|                      +-----------------------------------------------+                             |
|                      |             PASTORAL CARE COORDINATOR         |                             |
|                      |  apps/api/src/modules/edu/services/           |                             |
|                      |              discipline.service.ts            |                             |
|                      +-----------------------+-----------------------+                             |
|                                              |                                                     |
|                      +-----------------------+-----------------------+                             |
|                      |                                               |                             |
|                      v                                               v                             |
|   +------------------------------------+   +---------------------------------------------------+   |
|   |      CLEARANCE GATE LIEN BLOCK     |   |             GUARDIAN ESCALATION HUB               |   |
|   |   - Active Detentions > 0: HOLD    |   |   - Automated Warning Slips (Yellow / Red)        |   |
|   |   - Standing === PROBATION: HOLD   |   |   - Guardian Portal Demerit Notification          |   |
|   |   - Blocks TC & Final Graduation   |   |   - Formal Counseling Appointment Booking         |   |
|   +------------------------------------+   +---------------------------------------------------+   |
+----------------------------------------------------------------------------------------------------+

1.1 Relational Schema Definitions

The pastoral discipline domain models student conduct profiles, incident violation reports, and detention rosters within the relational persistence kernel:

export interface StudentConductDossierRecord {
  id: string;
  studentId: string;
  studentName: string;
  admissionNumber: string;
  className: string;
  sectionName: string;
  currentScore: number;
  standing: 'EXEMPLARY' | 'GOOD_STANDING' | 'UNDER_WATCH' | 'PROBATION';
  demeritCount: number;
  commendationCount: number;
  activeDetentionsCount: number;
  totalDetentionsServed: number;
}

export interface IncidentReportRecord {
  id: string;
  studentId: string;
  studentName: string;
  admissionNumber: string;
  className: string;
  sectionName: string;
  reporterName: string;
  reporterRole: string;
  incidentDate: string;
  category:
    | 'TARDINESS_TRUANCY'
    | 'CLASSROOM_DISRUPTION'
    | 'ACADEMIC_DISHONESTY'
    | 'UNIFORM_INFRACTION'
    | 'BULLYING_HARASSMENT'
    | 'COMMENDATION_EXCELLENCE';
  pointsAdjustment: number;
  description: string;
  actionPrescribed?: string;
}

export interface DetentionRosterRecord {
  id: string;
  incidentId: string;
  studentId: string;
  studentName: string;
  admissionNumber: string;
  className: string;
  sectionName: string;
  scheduledDate: string;
  startTime: string;
  endTime: string;
  room: string;
  proctorFacultyId: string;
  proctorFacultyName: string;
  status: 'SCHEDULED' | 'SERVED' | 'MISSED_ESCALATED' | 'EXCUSED';
  supervisorNotes?: string;
}

2. Interactive Operator Interface

The Pastoral Conduct Console gives deans and disciplinary proctors immediate oversight of school-wide conduct scores, pending detentions, and student behavioral tiers:

3. Behavioral Standing Classification & Mathematical Rules

The conduct engine computes standing using a piecewise threshold function implemented in DisciplineService.calculateStanding(score):

Standing(Score) =
  EXEMPLARY:      if Score >= 95
  GOOD_STANDING:  if 80 <= Score < 95
  UNDER_WATCH:    if 65 <= Score < 80
  PROBATION:      if Score < 65

3.1 Point Adjustments by Violation Category

4. Timetable Collision Detection for Detention Proctors

Assigning faculty proctors to supervise after-school detentions requires strict verification against instructional schedules to eliminate conflicts:

4.1 Collision Verification Code

As programmed in DisciplineService.assignDetentionProctor():

if (this.timetableService) {
  const collision = await this.timetableService.checkTeacherPeriodCollision(
    dto.proctorFacultyId,
    detention.scheduledDate,
    detention.startTime,
  );
  if (collision.hasCollision) {
    throw new BadRequestException(
      `Detention proctor assignment collision: ${collision.message || 'Supervisor has an active lecture period conflict'}`,
    );
  }
}

5. Operational Runbook: Incident Filing & Detention Completion

The daily pastoral care workflow covers incident recording, proctor assignment, and detention service validation.

Phase 1: Incident Blotter Recording

1. Initiate Incident Entry:

   • The faculty member or pastoral supervisor navigates to apps/edu/src/app/admin/discipline and clicks File Incident Report.
   • Input the student's admission number (#ADM-2024-004).
   • Select the violation category (e.g., CLASSROOM_DISRUPTION).
   • Enter an objective narrative description of the behavioral infraction.

2. Automated Conduct Calculation:

   • The service calculates currentScore = currentScore + pointsAdjustment.
   • If the score decreases past threshold limits, the student's standing advances from GOOD_STANDING to UNDER_WATCH or PROBATION.
   • If the infraction mandates detention, a pending DetentionRosterRecord is created with status SCHEDULED.

Phase 2: Detention Room Proctoring & Service Verification

1. Student Ingress at Detention Hall:

   • The scheduled student reports to the detention room (e.g., Room 104) at 02:45 PM.
   • The faculty proctor accesses the detention roster on the workstation.
   • The proctor verifies student identity and monitors reflective writing or academic assignments during the 45-minute detention period.

2. Mark Detention Served:

   • At the conclusion of the session (03:30 PM), the proctor clicks Mark Served.
   • DisciplineService.serveDetention() executes:

     detention.status = 'SERVED';
     if (dossier && dossier.activeDetentionsCount > 0) {
       dossier.activeDetentionsCount -= 1;
       dossier.totalDetentionsServed += 1;
     }
     

   • If activeDetentionsCount reaches zero and the student's conduct standing is not PROBATION, any clearance holds on the student dossier are automatically cleared.

Phase 3: Operational Throughput & Conflict Detection Telemetry

The pastoral discipline engine is benchmarked across real-time incident processing and collision checks:

6. Failure Modes & Recovery SOP

The following operational contingency protocols resolve behavioral and detention exceptions:

7. Cross-Vertical Internal Linkages

The pastoral discipline module coordinates with other core subsystems across the academic network:

• Registrar 360 Student Dossier & Clearance Gates — Restricts issuance of official Transfer Certificates while active detentions or disciplinary probations persist.
• Campus Supervision Duty Rosters & Invigilation Neutrality — Cross-references faculty schedules to prevent detention proctor collisions with instructional duties.
• RFID Turnstile Gate Kiosk & Tardiness Escalation — Feeds automated 3rd-strike morning tardiness violations directly into the pastoral incident blotter.
• Guardian Self-Service Portal & Turnstile Stream — Displays conduct scores, commendation badges, and detention notices directly to parents in real time.
• Faculty Monthly Payroll & Currency-in-Words Payslips — Compensates proctors for after-school detention supervision under Special Duty Allowances.