How verification works

Trust here is earned by process, not assertion. Every published artifact passes independent machine review before it reaches you — and anyone can verify a credential for free.

The generator ↔ checker loop

Two different model roles — preferably from different providers — check each other's work, backed by deterministic validators.

  1. Trusted sources

    Material is compiled only from sources you provide or curated references, with provenance preserved.

  2. Generator model

    Builds the candidate artifact: lessons, activities, simulations.

  3. Independent checker + deterministic gates

    A separate model audits factual accuracy, pedagogy, accessibility, security, and provenance; rule-based validators run alongside it.

  4. Structured issue registry

    Findings are recorded as typed, severity-ranked issues — never a vague “looks good.”

  5. Repair & recheck

    The generator fixes each blocking issue and the checker verifies again. Publication requires zero unresolved blockers.

VERIFIED → PUBLISHED

Verification scales with visibility

Private compile

Courses you compile for yourself need no public review. Deterministic validators and an independent checker model audit are available on demand.

Community shared

Sharing for rewards requires the full multi-model pipeline, deterministic checks, and provenance.

Marketplace public

Adds quality thresholds, fraud checks, creator accountability, and dispute processes.

Certified / high-stakes

Domain experts or qualified institutional issuers review, with human signoff where required. No external statutory accreditation (such as ISO/IEC 17024) is claimed unless formally awarded within verified scope.

A hybrid issuer network

Platform Issuer (Active)Institutional / Qualified Issuer (Application Gated)Community Issuer (Peer-Reviewed)

Skills can be attested by three issuer tiers — Platform, Qualified Institutional, and Community — each tracked on domain authority, historical accuracy, disputes, and revocations. Third-party statutory accreditation claims are governed strictly by formal audits; third-party evidence strengthens the proof-of-skill chain without replacing it.

Enterprise answers, fixed scope

Employers receive answers under a versioned, fixed schema (EVS): capability claim, level, confidence band, evidence categories, issuer, and last-verified date. Raw private learning history and tutor conversations are never part of the answer set.

Verifying a credential is free — for everyone

Every credential carries a Public Verification ID. Anyone — no account needed — can confirm that it exists, who issued it, and its current status:

/verify/<verification-id>

Have a verification ID? Open it directly at the route above — no account needed.