Catalog
/catalogPreview discoverable learning and enrolment.
Paideia is a learning platform for adult, corporate, partner, and customer education. Teams can author courses, manage enrolment, deliver media and live sessions, run assessments, issue certificates, track skills, and govern AI-assisted learning work.
Prepare governance, learning content, roles, and acceptance evidence for the Paideia adult and corporate learning platform before release.
This is a release-readiness guide for Paideia authoring, catalog, enrolment, delivery, assessment, certificates, skills, imported content, webinars, analytics, and governance. It is not production learner guidance or authorization to publish a live academy.
| Role | Access | Responsibilities |
|---|---|---|
| Learner tester | Preview assigned catalog, course, lesson, quiz, webinar, and certificate flows. |
|
| Author | Preview course structure, content, assessment, skills, packages, and sessions. |
|
| Academy or compliance administrator | Preview enrolment, reporting, roles, governance, and elevated operations. |
|
Establish content rights, human accountability, privacy, accessibility, and expected learning outcomes before testing delivery.
Define what may be tested, by whom, with which data and content, and under which stop conditions.
Capture environment, version, available scope, known gaps, support path, and test window.
Confirm learner, author, and administrator scope and test denied access.
Use synthetic learners and content with known rights, classifications, accessibility, and expected results.
Keep AI disabled unless approved; define human review, audit, privacy, retention, and elevated-access rules.
Stop on cross-tenant access, unauthorized publication, real personal data, invalid certificates, or uncontrolled external launch.
The preview has explicit scope, roles, synthetic inputs, accountable owners, governance settings, and stop conditions.
Build a compact test course that exercises content, assessment, completion, and accessibility without production publication.
Write measurable outcomes, audience, prerequisites, completion rule, and expected evidence.
Prepare modules, lessons, text/media blocks, sequencing, and one accessible alternative for each medium.
Use synthetic questions, pass threshold, attempt rules, feedback, and known expected scores.
Include SCORM, LTI, webinar, or AI only when separately approved and safely isolated.
Specify enrolment, progress, completion, certificate, skill, analytics, audit, and notification outcomes.
A rights-cleared, accessible, synthetic course has documented expected behavior for every tested capability.
Use separate author and learner sessions and verify records, permissions, and human controls at every transition.
Validate controlled publication, enrolment, learning, assessment, completion, and certificate evidence.
Create the prepared structure and verify preview, accessibility, metadata, and content ownership.
Confirm only the synthetic tenant audience can discover or enrol and preserve the publication audit event.
Verify assigned and self-enrolment rules, duplicate handling, reminders, and denied access.
Exercise media, sequencing, resume, lesson completion, quiz attempts, feedback, and optional approved integrations.
Reconcile progress, score, completion, certificate, skills, analytics, notifications, and audit history with the expected ledger.
Verify permitted changes, certificate verification, and how erroneous or withdrawn outcomes are handled.
The synthetic learner journey is accessible, tenant-scoped, human-governed, auditable, and reconciled to expected outcomes.
Require evidence from functional, privacy, security, accessibility, and operational owners.
Assess authoring, publication, enrolment, delivery, assessment, completion, certificate, analytics, and recovery.
Assess tenant isolation, RLS, audit, privacy requests, AI controls, elevation, content rights, retention, and external integrations.
Test keyboard and assistive use, captions/alternatives, localization, errors, performance, and diagnostics.
Record severity, owner, mitigation, retest, accepted scope, version, date, and production authorization status.
A dated, multi-owner decision states whether the tested scope is accepted, conditional, or blocked and why.
These limits describe the source-pinned Paideia 0.1.0 pre-release scope and must be rechecked when the product changes.
Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.
Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.
Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.
Likely cause: Completion rules, attempt state, event processing, filters, integration callbacks, or preview implementation differ from the expected ledger.