GoHiMark presents question authoring, teacher-controlled assistance, rubric review, banking, export, and proof records as one governed workflow for Australian schools.
Assessment materials move through review states. Public copy must not imply autonomous release or completed hosted AI routing until those gates are proven.
Governed trust signals
Curriculum alignment is governed through descriptor-level evidence.
Current UI proof keeps teachers in control of AI-assisted drafting.
Public hosted routing requires validation before stronger demo claims.
Certifications and data-residency statements require deployment evidence.
The current workbench proof shows a practical authoring surface for drafting questions, checking language and complexity, building rubrics, saving to a bank, planning lessons, and exporting classroom materials.
Teachers choose subject and year context, draft the task, and use controlled transforms for scaffolding, differentiation, and rubric preparation.
Toggle the proof controls to see what can safely move from draft to release.
Evaluate the significance of the Eureka Stockade in the development of Australian democracy using source evidence.
| Subject | History - Year 10 | Selected |
|---|---|---|
| Draft | Source-backed response prompt | Editing |
| Transform | Scaffold and differentiate | Available |
The controls above update the readiness state and preview pipeline without claiming an automated release workflow.
Current evidence proves the local route, screenshots, and video. Hosted public AI routing should be validated before stronger public demo claims.
The evidence package includes breakpoint screenshots and a teacher-workbench workflow video for guided review.
This view translates the product suite into inspectable capabilities: teacher workbench, assessment building, marking review, student feedback, analytics, governance packs, LMS/microfrontends, and video walkthroughs. Each capability keeps its proof status visible.
Draft, transform, review, rubric-check, bank, and export assessment materials with teacher approval.
Homepage proof frame, teacher assistance section, and workflow video package.
Compose exams from a 44-type registry with 38 generator-ready types, 42 renderer-ready types, and explicit generation gates where proof is pending.
Question framework registry, validation rules, shared exam Storybook surfaces, and subject-coverage matrix.
Separate objective checking from AI-assisted rubric suggestions so teachers can approve, override, and annotate.
Teacher review copy and marking workflow components.
Package feedback drafts, practice prompts, and progress signals for release after educator review.
Student learning route copy and adaptive-service boundary.
Turn assessment evidence into dashboards and review packs without claiming unsupported predictive outcomes.
Monitoring, Beacon, and generated validation artifacts.
Cross-reference question types, Storybook examples, ACARA, and state/territory framework targets before making descriptor-level coverage claims.
Question-type/curriculum validation audit: all 15 subject domains have ready representation coverage; descriptor manifests remain pending.
Show graph, chart, table, diagram, image-region, audio/file, code, scenario, and parameter-entry surfaces across the school subject catalogue.
Subject coverage matrix classifies 21 representation modes; 18 high-variance interaction types now have accessibility readiness boundaries.
Show what is implemented, what is validated, what is planned, and which claims are blocked until proof exists.
Unfounded-claims register and marketing validation artifacts.
Connect the wider application suite through route proof, smoke tests, contracts, and integration status.
Prelaunch route maps, Storybook surfaces, and service contract outputs.
Use workflow media to explain live assistance, product usage, and evidence boundaries during school review.
Video platform evidence and teacher-workbench walkthrough package.
Prioritize a teacher-review marking walkthrough and a claim scanner. Those two artifacts unlock stronger, safer marketing because they prove teacher control and prevent unsupported claims from returning.
This homepage section translates the Storybook question taxonomy into a buyer-facing product surface. It shows how teachers can choose a subject, grade band, and item type, then inspect Bloom coverage, example prompts, validation needs, and LMS-ready workflows.
Choose the best answer from four options.
Year 5 Science: Which material is the best insulator for a lunchbox?
Distractor quality, answer key, syllabus outcome, and reading load.
Objective answers can be checked directly while constructed responses should surface rubric suggestions for teacher approval, override, and annotation.
The public claim should stay bounded to evidence packs, cohort signals, coverage heatmaps, and export candidates until school-facing reports are route-proven.
Practice modes should inherit question taxonomy metadata, spaced-repetition timing, mastery confidence, and teacher release controls.
Exam assembly, course binding, LMS export, and gradebook write-back need separate proof rails before stronger deployment copy is used.
Promote this section with three proof rails: Storybook taxonomy parity, curriculum descriptor coverage, and route-level teacher approval for generated, graded, practised, and LMS-delivered items.
The marketing frontend now presents the language-graph workflow as an auditable ACARA-facing process: source registration, descriptor normalization, prerequisite and co-dependency graphing, question and answer generation, teacher validation, LMS delivery, analytics, and coverage feedback.
This section describes an alignment workflow and evidence model. It does not claim full national curriculum coverage, certification, or production readiness for every state syllabus until descriptor manifests, gold-set evaluation, and jurisdiction-specific proof are complete.
Based on the language-graph app pattern: graph nodes, prerequisite chains, validation states, and coverage gaps.
Number, algebra, measurement, space, statistics, and probability sequences
Prepares number fluency and estimation.
Connects fractions, ratios, rates, and percentages.
Feeds graph interpretation and simultaneous equations.
Requires rubric and exemplar calibration.
Current graph shows alignment workflow and prerequisite modelling. Descriptor-complete ACARA/state coverage still requires manifest counts and authority-version reconciliation.
ACARA Version 9.0, state and territory syllabus sources, version dates, and ingestion owner.
In validationLearning area, strand, content descriptor, achievement standard, general capability, and cross-curriculum priority mapping.
In validationPrerequisites, co-dependencies, year progression, gateway nodes, and remediation paths modelled as graph edges.
ImplementedQuestion type, subject, grade band, Bloom level, answer key, rubric, accessibility, and misconception controls.
ImplementedSource match, solution accuracy, reading load, rubric fit, moderation samples, and human approval.
Proof availableLMS or exam delivery, learner evidence, analytics, mastery state, coverage gaps, and next-item recommendations.
In validationSimilar education platforms sell activity breadth, AI prep, accommodations, and analytics. GoHiMark should compete by making those ideas inspectable: show the workflow, show the evidence, and show the boundary before a claim becomes a promise.
AI drafts and rubric suggestions stay behind teacher review, approval, override, and release decisions.
The public builder now maps to the Storybook question taxonomy and exposes question type, Bloom, grade, and validation detail.
ACARA and syllabus language is framed as an alignment workflow until descriptor-level coverage manifests are validated.
Course delivery, gradebook write-back, and reporting are shown as staged integration work with explicit proof gates.
Assessment and classroom platforms lead with many activity types.
GoHiMark should lead with taxonomy depth, validation controls, and teacher approval.
AI teacher tools focus on lesson prep, rubrics, reports, and question generation.
GoHiMark should show prep speed only when paired with review, provenance, and export readiness.
Mature school platforms make learner access and accommodations visible.
GoHiMark should expose accessibility checks per question type and per delivery mode.
LMS and assessment platforms sell insight, not raw charts.
GoHiMark should show evidence packs, intervention candidates, and confidence caveats.
Route buyers from proof center to builder, then from builder to a governed walkthrough request. The sequence is stronger than a generic demo CTA because it lets teachers and procurement inspect the product before a sales conversation.
This section now separates implemented UI, runtime proof, validation work, and roadmap intent. Stronger public claims should only appear after the corresponding governance artifact or live service proof exists.
A product-like authoring flow for drafting, reviewing, packaging, and exporting assessment materials with teacher approval visible at each step.
Assessment creation is shown as a governed workflow with visible question-type framing and review gates.
ACARA and state-framework language is framed as an alignment workflow under validation, not as complete public coverage.
Adaptive practice is retained as a roadmap capability connected to backend services, without claiming classroom-ready mastery automation.
Reporting is positioned as evidence packaging and review readiness, not live predictive analytics or parent-ready automation.
Video workflows are included as a validated adjacent capability for teacher walkthroughs, media-rich assessment, and product education.
The platform story acknowledges the wider app surface while separating live proof from unfinished LMS write-back and school deployment work.
Security, compliance, data residency, accuracy, and time-saved statements require documented proof before they return to prominent marketing copy.
Use calm, specific, inspectable language: what the product shows today, what service or Storybook surface proves it, and what must be validated before stronger claims such as accuracy, certification, data residency, or school-wide outcomes are used.
Whether you're a teacher crafting assessments or a student preparing for exams, GoHiMark has a purpose-built experience for you.
GoHiMark is currently in development. Register your school's interest to receive early access, founding-school pricing, and product updates.