AvailableQuestion evidence
A buyer-facing proof model for the 44-type K-12 question registry, including generator readiness, renderer readiness, Storybook parity, and gaps that still need scoring or accessibility proof.
What this supports
44 K-12 question types are tracked through explicit readiness gates, with 38 generator-ready and 42 renderer-ready types at the last validation pass.
Proof boundary
The registry supports evidence-led evaluation. It does not claim every type is production-scored, fully accessible, or validated against every state syllabus descriptor.
Heads of learningAssessment leadsIT evaluators
Requires validationCurriculum governance
How GoHiMark frames ACARA, Australian Curriculum v9.0, and state/territory syllabus language without overstating validation coverage.
What this supports
Curriculum alignment is presented as a governed workflow: descriptor mapping, teacher review, evidence packaging, and authority-specific caveats before public coverage claims.
Proof boundary
No page should claim ACARA certification, complete Australian Curriculum coverage, or state/territory validation until descriptor-level manifests and authority review evidence exist.
Curriculum leadersDeputy principalsCompliance reviewers
AvailableTeacher workflow
A practical description of how live assistance, question drafting, rubric preparation, review, export, and teacher override should be shown in marketing without implying teacher replacement.
What this supports
The teacher workbench is positioned as a human-in-the-loop authoring and review surface for drafting, transforming, checking, banking, and exporting assessment materials.
Proof boundary
The workbench should not be described as fully autonomous, certification-ready, or a substitute for teacher judgement.
TeachersFaculty headsSchool executives
Requires validationAccessibility
A validation plan for question rendering, keyboard flow, screen-reader naming, captions/transcripts, alternative representations, and inclusive assessment settings.
What this supports
Accessibility is treated as a validation program across question types, media, controls, navigation, and alternative representations.
Proof boundary
The marketing site can discuss accessibility review and design intent, but should not claim full accessibility conformance until WCAG evidence exists for each public route and question surface.
Inclusive education leadsIT teamsLearning support coordinators
DraftIntegration
How the wider GoHiMark application suite should be described through route proof, contract proof, integration status, and deployment evidence.
What this supports
The product story can connect LMS, Beacon, assessment, video, and governance surfaces when each route and service claim is backed by proof.
Proof boundary
No copy should imply production LMS write-back across all providers or completed integrations until provider-specific contract tests and deployment proof pass.
IT managersProcurement teamsSchool operations leaders
DraftLearning science
A conservative framework for positioning adaptive practice, mastery signals, feedback timing, teacher override, and learning-outcome evidence.
What this supports
Adaptive learning is a planned feedback-loop capability that must be evaluated through learner-state evidence, teacher overrides, intervention quality, and outcome measurement before stronger claims are made.
Proof boundary
Do not claim guaranteed learning gains, predictive outcomes, or classroom-ready mastery automation before pilot data and statistical review exist.
Learning designersSchool executivesResearch partners