04 — Information Architecture (Attendance Module)

• 1. Position in the app shell
• 2. Attendance IA tree
• 3. Navigation model (per 00-shared/05 §3)
• 4. Routing table (module)
• 5. Cross-links (inbound/outbound)
• 6. Modal hierarchy (per 00-shared/05 §5)
• 7. Quick actions & FABs
• 8. Role → surface map

Where attendance screens live in the app shell (00-shared/05), what links into them, and what they own. Role gating derives from role.schema.ts:8-65 and permissions.constants.ts:29-30,39-43; routes use studylyon:// deep-link convention (00-shared/05 §4).

1. Position in the app shell

Attendance is a top-level destination /attendance for teacher and admin (00-shared/05 §2); default landing for teacher = "Attendance/Today" (00-shared/05 §2). Parents/students reach attendance through the student profile surface (S7), not the top-level tab.

AppShell (role-aware, 00-shared/05 §1)
 ├─ /home            Dashboard (admin) / Home (teacher)
 ├─ /attendance      ATTENDANCE MODULE (this doc) — teacher, admin
 ├─ /students        student profile → S7 Attendance tab
 ├─ /reports         admin → S5 Monthly report entry (proposed)
 └─ /notifications   parent alert deep-link → S7 day view

2. Attendance IA tree

/attendance
 ├─ S1 Today's roster            — my classes → pick class (default today)
 │   └─ S2 Marking grid          — roster rows × StatusChip
 │       ├─ S3 Batch edit sheet  — multi-select → one status for N rows
 │       └─ StatusChip popover   — per-row: 6 statuses + checkIn/checkOut/remarks
 ├─ S4 History / calendar        — pick class, month → heatmap → day detail
 ├─ S5 Monthly report            — class × range → summary + report job (admin)
 │   └─ S6 Report detail         — per-status breakdown + drill to S4/S7
 └─ S8 Biometric device status   — devices, last punch, ingest trend (admin/operator)

/students/:id → S7 Student attendance profile tab (self: student, child: parent)
/notifications → absent alert → studylyon://attendance/:date (parent)

Screen numbering matches 05_Screen_Inventory.md.

3. Navigation model (per 00-shared/05 §3)

• Phone: /attendance stack: S1 → S2 → S3 (sheet, half-height); S4/S5 tabbed or pushed from S1 context menu; S8 pushed from S1 app-bar menu.
• Tablet/desktop: master-detail — left: class + month list; right: S2 grid or S4 heatmap (≥ 840 dp, 02_Design_Tokens.md §8).
• Tabs within attendance (teacher): Today (S1) · History (S4) · Devices (S8, admin only) — AppTabs (00-shared/03).
• Breadcrumbs (desktop only): Attendance › Class › Date.

4. Routing table (module)

Guard model: route guards check user.permissions; server remains authoritative (00-shared/05 §9, 00-shared/06 §5 — 403 → permission screen or hidden destination). Note: backend has no per-endpoint RBAC metadata on attendance yet (OQ-5) — client gating must not promise 403 where server might 200.

5. Cross-links (inbound/outbound)

6. Modal hierarchy (per 00-shared/05 §5)

1. Snackbar — "Marked absent" / "Saved (3)" / undo.
2. Bottom sheet — S3 batch edit, StatusChip popover (half-height), date/class pickers.
3. Dialog — confirm bulk "Mark 34 as absent?" when selection is large (> 10, or leaving grid with unsaved offline queue); destructive confirms only.
4. Full-screen — S6 report detail; S8 device add/edit (planned).
5. Loader — only grid refresh when nothing cached; skeletons otherwise.

7. Quick actions & FABs

• FAB on S1/S2: "Mark attendance" (opens S2 for default class/date) — one FAB per screen (00-shared/05 §7).
• Context menu on S2 row: edit details (checkIn/checkOut/remarks), view student, copy.
• Swipe on S4 day cell: mark-as-present/late quick fix (desktop: right-click).
• Keyboard (desktop): P/A/L/H/V/D cycle status on focused row (see 10_Interaction_Specification.md).

8. Role → surface map

Teacher has no report.* permission (role.schema.ts:31) — S5/S6 are admin-only today (OQ: confirm if teacher monthly view should be granted report.read).