Mock — B2.1 Teacher-initiated child enrollment

Mock of B2.1 — Teacher-initiated child enrollment

Sources: spec §3.2.1 B2.1. No corresponding PRD §5 journey — B2.1 is spec-only, introduced to distribute child-enrollment work off the director's critical path.

Invariants enforced in this screen: review is surfaced, never gating (B2.1-AC2); enrolled_by_user_id distinguishes teacher-enrolled from director-enrolled for audit (B2.1-AC3); teacher cannot enroll into a classroom they are not assigned to (error case).

Inference flags:

inference: entry point from classroom view — spec says teacher "enters the child's details from the classroom view" (§3.2.1 step 1); exact UI affordance (button placement, label) not specified.
[copy for the admin-dashboard "new enrollment" surfacing] — spec says "appears ... as a 'new enrollment' surfacing (gentle, non-blocking)" but exact wording is not specified
PRD gap: this behavior has no counterpart in PRD §5 journeys. The director-facing dashboard surfacing implied here is not explicitly drawn in PRD J2 (setup) or J8 (dashboard). Calibration signal for Nelson/Allan: does B2.1 warrant a PRD journey entry, or is it acceptable as a spec-only sub-behavior?

B2.1 — Teacher-initiated child enrollment

Teacher view — classroom roster with "add child" affordance

Teacher is logged in (see B4) and viewing their assigned classroom. A button surfaces the enrollment form. If the teacher is assigned to multiple classrooms, they pick which (§3.2.1 inputs).

Classroom: Toddler Room

[child 1]
[child 2]
[child 3]

+ Add a child to this classroom

Enrollment form (teacher-initiated)

Child name

Age group

Date of birth (optional)

Classroom

Enroll

Duplicate detection: matching (name, DOB, classroom) triples warn before saving (§3.2.1 error case, §4.4 Child invariants). Same rule as B2.

On enrollment:

Child.enrolled_by_user_id = this teacher's User.id (spec §3.2.1 step 1 + §4.4).
Child.admin_reviewed = false (spec §4.4 — becomes true when admin accepts).
Consent.level defaults to all, matching director-enrollment behavior (§3.2.1 step 2).
Child is immediately eligible for photo tagging under default consent — no gate on admin review (§3.2.1 step 4).

Admin dashboard — new enrollment surfacing (parallel view)

Surfaced gently on the admin dashboard as a pending review item. Director can accept, correct consent, reassign classroom, or reject (§3.2.1 step 3).

Child	Enrolled by	Classroom	Consent	Action
[newly enrolled]	Teacher (Toddler Room)	Toddler Room	`all` (default)	Accept Reassign classroom Change consent Reject

[exact surfacing style — banner, inline card, separate tab — not specified in spec]

If director rejects

Child record is archived (not hard-deleted unless never tagged in a photo). Any existing delivery records are deleted per B-ChildOffboard (see B9).

Error path — cross-classroom attempt

If a teacher attempts to enroll into a classroom they are not assigned to, the system rejects the action (§3.2.1 error case).

[exact error message — not specified in spec]