Proof Center

Inspect the evidence before trusting the claim.

This page is built for school leaders, IT teams, and curriculum teams who need to separate current product proof from validation work and roadmap intent.

44
K-12 question types
42
Renderer-ready types
0
Blocked marketing claims after validation
Next
Docker route smoke and proof pack
Proof center

Give schools a reason to believe every claim before they book a pilot.

Similar 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.

Implemented

Teacher-controlled AI

AI drafts and rubric suggestions stay behind teacher review, approval, override, and release decisions.

Evidence to show
Teacher workbenchReview queuesClaim status badges
Proof available

Question taxonomy depth

The public builder now maps to the Storybook question taxonomy and exposes question type, Bloom, grade, and validation detail.

Evidence to show
36 Storybook codesBuilder parity validatorQuestion examples
In validation

Curriculum claim hygiene

ACARA and syllabus language is framed as an alignment workflow until descriptor-level coverage manifests are validated.

Evidence to show
Governance planClaim scannerBlocked wording list
In validation

LMS and reporting pathway

Course delivery, gradebook write-back, and reporting are shown as staged integration work with explicit proof gates.

Evidence to show
LMS governance docsRoute inventoryIntegration caveats
Buyer journeys

Classroom teacher

  1. 1Select subject, year, Bloom level, and question type.
  2. 2Generate or adapt a draft item.
  3. 3Review answer, rubric, accessibility, and difficulty.
  4. 4Approve for quiz, flashcards, practice exam, or lesson use.

Head of Department

  1. 1Inspect common-assessment coverage by year and subject.
  2. 2Compare item types and moderation requirements.
  3. 3Review department-level gaps and blocked claims.
  4. 4Approve what can be piloted now versus later.

IT and procurement

  1. 1Check data, AI, hosting, and integration boundaries.
  2. 2Trace claims to evidence and validation status.
  3. 3Separate local proof from production deployment work.
  4. 4Request security and implementation evidence packs.
What stronger competitors teach us

Activity variety

Assessment and classroom platforms lead with many activity types.

GoHiMark should lead with taxonomy depth, validation controls, and teacher approval.

Teacher prep acceleration

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.

Accessibility and accommodations

Mature school platforms make learner access and accommodations visible.

GoHiMark should expose accessibility checks per question type and per delivery mode.

Analytics that inform action

LMS and assessment platforms sell insight, not raw charts.

GoHiMark should show evidence packs, intervention candidates, and confidence caveats.

Best next conversion path

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.

Current proof checklist

These are the gates the marketing app now uses to keep public copy useful without letting it outrun the application.

Homepage and builder route proof

Marketing routes should render the builder section and proof center in local and Docker runtime.

Storybook taxonomy parity

The builder must include every canonical question code from the Storybook question taxonomy.

Curriculum claim scanner

Marketing copy must avoid unsupported full-coverage, auto-grading, outcome, and LMS write-back claims.

Procurement evidence pack

Security, privacy, AI routing, data retention, and hosting claims need a named evidence artifact.

Publicly visible
3

Claims shown without development reveal

Verified/proven
3

Implemented or proof-backed capabilities

Development gated
2

Hidden until explicitly requested

Proof register

Public claims are listed as evidence records. Search and filter without making development-only claims public by accident.

Showing 3 of 3 visible proof records. 2 development records remain hidden.
Capability
Status
Last validated
Evidence

Current proof artifacts

Question-type subject coverage matrix

Proof available

documentation-governance/generated/question-type-subject-coverage-2026-07-01/question-type-subject-coverage.md

Unfounded claims validation

Proof available

documentation-governance/generated/unfounded-claims-2026-07-01/unfounded-claims-validation.md

Marketing bento validation

Proof available

documentation-governance/generated/marketing-bento-governance-2026-06-30/marketing-bento-validation.md

Full-spectrum audit packet

Proof available

documentation-governance/generated/question-type-full-spectrum-audit-2026-07-01/question-type-full-spectrum-audit-parts-01-10.zip