Course applications
Where the system meets real course work
Applications use the core system through a named implementation. They supply evidence, constraints and refinements without becoming the reusable system themselves.
Source authority remains separate: approved course documents govern learner-facing copy. The design system governs presentation, interaction, accessibility and reusable technical behaviour.
Current ISQ applications
Child Protection for Teachers
Evidence sourceEstablished course application informing the current Rise component family, decision pathways and production styling.
Child Protection for Principals and Board Directors
In developmentControlled course build applying and refining the shared learning patterns and approved ISQ Rise components.
Application record contract
| Record | Purpose |
|---|---|
| Source authority | Identifies the approved content and mandatory development requirements. |
| Implementation | Names the organisational theme, platform and component versions used. |
| Exceptions | Records any course-specific treatment and why it has not been generalised. |
| Qualification evidence | Captures accessibility, responsive, publishing and telemetry verification. |
| Contribution back | Identifies refinements proposed for the reusable system. |