RTOpacks InstaLearn — Product Specification¶

Document ID: IL-SPEC-01
Version: 0.1
Status: Living document — foundational thinking captured; briefs scoped separately
Location: docs/docs/workspace/apps/instalearn.md
Last updated: 14 April 2026

Changelog¶

Version	Date	Changes
0.1	14 Apr 2026	Initial — product ladder, four surfaces, marketplace model, governing principles

How to Use This Document¶

This spec is the full-picture reference for the InstaLearn product family. Like the other core specs, it is deliberately comprehensive — built from the accumulated product thinking across multiple sessions, rationalised into a single authoritative document.

This document does not constitute a brief. Briefs are scoped, sequenced, and issued separately. Each brief references this document as its source of truth. Existing InstaLearn fragments in the doc database (partial briefs, session notes, Time Machine references) are superseded by this document.

Alex: read this document before picking up any InstaLearn brief. The briefs will tell you what to build. This document tells you why, and what it needs to eventually become.

What InstaLearn Is¶

InstaLearn is the outward-facing commercial layer of the RTOpacks platform. Where the compliance spine — Studio, People, Record — faces inward toward the RTO's operational and regulatory obligations, InstaLearn faces outward toward learners, employers, and the non-accredited training market.

It is a product family, not a single product. Four surfaces, one launcher row, one shared content substrate. Each surface is a distinct product with a distinct value proposition and a distinct user. They share the same catalogue, the same credential infrastructure, and the same underlying architecture — but they serve different needs and should be understood separately.

The context that created this: Joe Newbery's February 2026 analysis predicted that demand for non-accredited training would surge as the national training framework fails to keep pace with employer needs. RTOs that respond will be those who can deliver fit-for-purpose content quickly, under their own brand, without building infrastructure. InstaLearn is that response. The content exists. The infrastructure runs. The RTO's job is marketing.

The Launcher Row¶

InstaLearn occupies the fourth row of the Workspace launcher, labelled Learning.

The four tiles in this row are:

Tile	Label	What it is
1	InstaLearn	The catalogue. Browse, preview, and access content. Ten free on signup delivered as SCORM.
2	Campus	The managed store. Select content, RTOpacks provisions the infrastructure, the store goes live.
3	Creator	The lightweight authoring tool. Build simple courses and publish them to Campus or export as SCORM.
4	Marketplace	The peer content exchange. Creator-built content listed for sale. Other RTOs browse and deploy.

These four tiles represent a complete product ladder — each rung is a logical step from the one before it, and each has a clear reason to exist independently.

The Content Substrate¶

All four surfaces draw from the same content foundation stored in microcredentials-db.

Two content tiers:

InstaLearn Essential — the atomic unit. - Single lesson, approximately 6–10 minutes - One embedded video - One scenario-based quiz question - Summary and pro tip - Covers one specific workplace skill or concept - Equivalent to what you'd watch on a bus commute

InstaLearn DeepDive — the compiled course. - 6–8 lessons, approximately 45–60 minutes total - Multiple videos, interactive elements (flashcards, accordions, thought exercises) - Knowledge Check (3 questions) and Summary lesson - Covers a full topic area in depth - Equivalent to a half-day workshop, compressed

The catalogue: Approximately 600+ Essential modules and 100+ DeepDive courses. Topic map drawn from Articulate Rise's two-tier library structure as a blueprint — not their content, their taxonomy. All content is original. Original Articulate reference titles stored in original_ref field, never displayed.

Four content themes (the white-collar workplace knowledge territory): 1. Interpersonal competence — communication, empathy, conflict, feedback 2. Self-management — time, stress, resilience, mental health, goal setting 3. Organisational risk mitigation — harassment, WHS, ethics, security 4. Role capability — leadership, sales, marketing, project management, customer service

The catalogue is office and knowledge worker territory. No trade content. No technical vocational content. An RTO with a plumbing scope gets the same catalogue as one with a business services scope — non-accredited content is jurisdiction and scope agnostic.

Four-level taxonomy in microcredentials-db: - Domain — top-level subject area (e.g. Leadership, Communication, Workplace Compliance) - Stream — thematic cluster within a domain (e.g. Leadership Styles, Emotional Intelligence) - Module — the atomic Essential unit (one lesson, one video, one quiz) - Course — a compiled DeepDive (ordered collection of Modules with section structure)

The Credential Infrastructure¶

All four surfaces share the same credential issuance system.

When a learner completes a module or course and passes the quiz, a credential is issued automatically:

PDF certificate — carries RTO branding, course name, learner name, completion date, verification reference
Digital credential — self-signed, verifiable at InstaLearn.com/verify/{token}
The verification page pulls the issuing RTO's config (name, logo) and displays it alongside the credential

No Credly. No Badgr. No third-party credentialing platform. The infrastructure is native to RTOpacks. The credential domain (InstaLearn.com) is intentionally separate from the RTOpacks platform for two reasons:

Branding: A learner verifying a credential should not land on a page that says "RTOpacks" — that is an operator platform name, not a credentialing authority name. InstaLearn.com is the right credential authority identity — neutral, learner-friendly, global.
Architecture: The credential verification server is a separate concern from the B2B operator platform. Separate concern, separate surface, separate domain.

InstaLearn.com was registered 7 April 2026. .com not .com.au — the content is not Australian-specific and the credential authority should not be geographically constrained.

Surface 1: InstaLearn (The Catalogue)¶

What it is: The entry point. Browse and access the full content catalogue. The free tier gives every RTOpacks subscriber ten courses delivered as SCORM on signup — no configuration, no store, no infrastructure. Just download the SCORM package and load it into whatever LMS the RTO already has.

Who uses it: Any L4 user. This is the lowest-friction entry to the InstaLearn product family.

The free ten: On first opening InstaLearn, the RTO selects ten courses from the catalogue. These are delivered immediately as SCORM packages. No strings, no time limit, no configuration required.

The SCORM reality: SCORM is a format from the 1990s. It runs on tools like Moodle. Most RTOs are not good at Moodle. The SCORM delivery is the hook — it works, it's free, it gets content in front of learners. The friction of SCORM in a poorly-managed Moodle instance is the natural nudge toward Campus.

The SCORM warning (displayed on every export):

"SCORM is a format written in the 1990s and played on tools like Moodle. What you experience on our platform will not translate faithfully to a SCORM player. This export exists because the industry uses the format, not because we recommend it. No support is provided for SCORM exports."

This warning is not aggressive. It is honest. RTOs who know their Moodle will ignore it. RTOs who don't will hear it.

Beyond the free ten: Additional courses are available for purchase from the catalogue. Purchased courses can be delivered as SCORM or deployed into Campus.

Surface 2: Campus (The Managed Store)¶

What it is: A fully managed, white-label learning store provisioned by RTOpacks on the RTO's behalf. The RTO selects their content, configures their branding, and RTOpacks spins up the infrastructure. The store is live. The RTO's job from that point is marketing.

Who uses it: L4 admin to configure and manage. Learners access it directly through the RTO's own domain.

The provisioning sequence: 1. RTO opens Campus from the Workspace grid 2. First-run configurator: branding (logo, colours), store name, domain/subdomain, Stripe account connection (theirs or we set one up), course selection 3. RTOpacks provisions: Cloudflare Workers + D1 + KV + domain configuration 4. Store is live — typically minutes, not days

What RTOpacks manages: Everything operational. The infrastructure runs. The content serves. The checkout processes payments. Credentials issue automatically on completion. The RTO does not manage any of this.

What the RTO manages: Marketing. That is the entire job. Get on TikTok. Push to corporate employers as staff professional development. The commuter angle — people learning on buses instead of gaming. The content is there, the checkout works, the credential issues. There is nothing to support because nothing breaks.

The white-label model: There is no InstaLearn branding on the learner-facing surface. The RTO's brand is the brand. Learners never know InstaLearn exists. The tell is in the HTML — a meta tag or comment, invisible to learners. The RTO feels like this is their secret weapon. That feeling makes them more successful.

InstaLearn branding exists in: - The Workspace grid tile label - The backend product name in RTOpacks operator context - The credential verification domain (InstaLearn.com)

InstaLearn branding does NOT exist in: - The learner-facing store - The completion certificate (RTO brand only) - Any public-facing URL the learner sees

Revenue model: The RTO sets their own price for content. The RTO keeps the margin. RTOpacks takes a platform fee (percentage TBD). Content is licensed from the RTOpacks catalogue — RTOs do not own the content, they licence the right to deliver it through their Campus instance.

Multiple instances: An RTO can run more than one Campus — a public-facing store and a private staff training portal, for example. Additional instances are a paid add-on.

The immediate value proposition: The justification for the RTOpacks monthly subscription fee includes a revenue-generating learning store with a cash register attached to it, live within minutes of signup. This is not a future benefit. It is immediate.

Student management: The learner-facing store has its own self-contained student management. It does not live in RTOpacks. Learner signs up, pays, completes, receives credential, done. If they lose access they re-register. The credential re-issues from their record. No helpdesk. No support calls. Self-serve by design.

The SCORM exit: If an RTO wants to move their selected courses to their own LMS, they can export as SCORM. When they leave they keep the Cloudflare account and the domain. They do not keep the content experience — that requires the live connection to generate. They receive their SCORM export. That is the exit path.

Surface 3: Creator (The Authoring Tool)¶

What it is: A lightweight, simple course authoring tool. Not Studio. Nowhere near Studio. Creator is for simple content — a health and hygiene induction for a fish and chip shop, a customer service module for a small employer, a site-specific safety briefing. The barrier to use is near zero. If it needs a manual, it has failed.

Who uses it: L4 users who want to build their own content without compliance depth. Also directly accessible to non-RTO small business owners who want to create simple training for their own staff.

What Creator produces: - A lesson with a title, video embed, text content, and a quiz - A completion certificate issued under the creator's brand - Verifiable at InstaLearn.com/verify/{token} - Exportable as SCORM - Deployable directly into Campus

What Creator does not produce: - Content mapped to TGA units - Compliance evidence for ASQA audit purposes - Anything that satisfies the Standards for RTOs 2025

Creator content is not accredited training. It is not presented as accredited training. The credential it issues is a completion certificate — not a Statement of Attainment, not a nationally recognised qualification. This distinction is clear in the UI and in the credential itself.

The small business use case: A fish and chip shop owner can use Creator to build a three-lesson induction — food handling, customer service, workplace behaviour — badge it with their shop name, and issue a completion certificate to every new employee. No RTO required. No compliance overhead. Just simple training that works and proves it happened.

The relationship to Studio: Creator is not a stepping stone to Studio. They serve different purposes. A Creator user who needs compliance depth will eventually need Studio — but that is their choice to make. Creator does not push toward Studio. It is complete in itself for what it does.

Pricing: Creator is free. The value to RTOpacks is content volume — every Creator course that gets listed in the Marketplace increases the catalogue depth. Every Campus deployment that uses Creator content is additional licensing revenue.

Surface 4: Marketplace (The Content Exchange)¶

What it is: A peer content exchange where Creator-built courses can be listed for sale. Other RTOs (and Campus operators) browse the Marketplace, purchase content, and deploy it directly into their Campus instance. RTOpacks takes a platform fee. The creator keeps the margin.

Who uses it: Any L4 user can browse and purchase. Creator users who have built content can list it for sale.

The model: Analogous to Google's Bitnami marketplace — some content is free, some is paid, all of it works because it was built on the same platform. No compatibility issues. No integration headaches. Content either runs on the InstaLearn stack or it doesn't exist in the Marketplace.

Why this works without a support burden: Creator content is built on the RTOpacks platform using RTOpacks tools. It is validated on submission. If it runs in Creator it runs in Campus. There is no "it works on my machine" problem. The platform is the guarantee.

Quality signal: Sales and completion rates are the quality signal. Good content sells. Poor content doesn't. No editorial gatekeeping required — the market self-regulates. RTOpacks may introduce a minimum completion rate threshold for continued listing in Phase 2.

Pricing: The seller sets the price. RTOpacks takes a platform fee (percentage TBD, consistent with Campus platform fee model). Free listings are permitted — creators may choose to offer content free to build audience and reputation.

Content standards: Marketplace content must meet minimum technical standards (video renders, quiz works, certificate issues). It does not need to meet any pedagogical standard beyond that. The platform validates technical function, not educational quality. That is the buyer's judgement to make.

The Product Ladder¶

The four surfaces form a complete ladder. Each rung is accessible independently but also flows naturally to the next.

InstaLearn  →  Campus  →  Creator  →  Marketplace
(consume)      (deploy)    (build)     (publish)

The upgrade logic:

InstaLearn → Campus: "The SCORM files work but Moodle is painful. Campus has a working store in ten minutes."

Campus → Creator: "I want to add my own content alongside the catalogue. Creator lets me build it without compliance overhead."

Creator → Marketplace: "I built something good. Other RTOs would pay for this."

The bridge back to the compliance spine:

Creator → Studio: "I need this content to be audit-ready and compliant. Studio is built for that."

This is the natural funnel. An RTO that starts with non-accredited content in Creator and grows to the point where they need accredited delivery is already inside RTOpacks. The transition to Studio is not a platform change — it is a tile change.

What InstaLearn Is Not¶

It is not accredited training. Nothing produced by InstaLearn — whether from the catalogue, Campus, or Creator — satisfies the requirements of nationally recognised training. It does not map to TGA units. It does not produce Statements of Attainment. It does not create compliance evidence for ASQA audit purposes.

It is not a general-purpose LMS. Campus is a managed deployment of a specific content experience. It is not configurable as an LMS in the way Moodle or Canvas are. RTOs who need a general LMS should use an LMS.

It is not Studio. Creator is deliberately simple. The moment Creator starts adding features that bring it closer to Studio's compliance depth, it has lost its purpose. The two tools serve different markets. Creator is for simple content. Studio is for compliant content. They are not competing.

It is not a student records system for the RTOpacks Workspace. Learner data from Campus lives in the Campus D1 instance provisioned for that RTO. It does not flow into the RTOpacks Workspace. The operator can see summary analytics but does not manage individual learner records from within RTOpacks.

Integration with the Compliance Spine¶

InstaLearn sits above and alongside the compliance spine, not inside it.

Record: In Phase 3, credentials issued through InstaLearn are stored in Record and linked to the relevant People records — confirming that a trainer's professional development was completed and verifiable. This is a Phase 3 integration.

People: Trainer-facing Campus deployments (private staff training portals) can contribute CPD evidence to People records — a trainer completes a leadership DeepDive, the completion record links to their CPD log in People. Phase 3.

Studio: The Marketplace creates a content pipeline that Studio can eventually draw from — pre-built non-accredited modules that can be contextualised and mapped to TGA units for use in accredited delivery. This is a future consideration, not a current design constraint.

Technical Foundation¶

Databases: microcredentials-db (UUID: 3924412d) — content taxonomy, modules, courses, Marketplace listings.

Credential domain: InstaLearn.com — registered 7 April 2026. Credential verification Worker at InstaLearn.com/verify/{token}.

Campus provisioning: Each Campus deployment is a separate Cloudflare account provisioned in the RTO's name — Workers + D1 + KV + domain. RTOpacks manages the provisioning. The RTO owns the account.

Code module: apps/workspace/instalearn/

Status: OBJECT-01 complete (schema). INSTALEARN-DEPLOY-01 pending (headless LMS deployment system). INSTALEARN-CONTENT-01 pending (content production pipeline).

Build Sequence and Phasing¶

Phase 1 — InstaLearn Catalogue¶

Catalogue browsing UI in the Workspace
Free ten selection and SCORM export on signup
Additional course purchase
SCORM delivery with honest warning
Credential Worker at InstaLearn.com/verify/{token}

Phase 2 — Campus¶

First-run configurator (branding, domain, Stripe, course selection)
Cloudflare account provisioning automation
Learner-facing storefront (white-label, RTO brand only)
Stripe checkout integration (RTO's account)
Automatic credential issuance on completion
Operator analytics dashboard in Workspace
Multiple instance support (paid add-on)

Phase 3 — Creator¶

Simple lesson builder (video embed, text, quiz)
Certificate generation under creator's brand
SCORM export from Creator
Direct deployment from Creator to Campus
Small business access model (non-RTO operators)

Phase 4 — Marketplace¶

Creator content submission and validation
Marketplace browse and purchase UI
Platform fee processing
Direct deployment from Marketplace to Campus
Sales analytics for creators

Open Questions¶

Platform fee percentage: The percentage RTOpacks takes from Campus and Marketplace transactions is not yet set. Must be decided before Phase 2 commercial launch.
Marketplace quality threshold: Whether to introduce a minimum completion rate for continued Marketplace listing is deferred to Phase 2. Phase 1 Marketplace has no quality gate beyond technical validation.
Creator access model for non-RTOs: Small businesses without RTOpacks subscriptions accessing Creator directly — the access model, pricing (if any), and account type for these users is unresolved. Likely a separate lightweight account tier.
CPD evidence integration with People: The mechanism by which Campus completion records contribute to People CPD logs is a Phase 3 design question. Not a constraint on Phase 1 or 2.
Content licensing terms: The precise terms under which RTOs licence catalogue content for Campus delivery — exclusivity, territory, duration — are not yet documented. Required before commercial launch.
Marketplace content standards document: The minimum technical standards for Marketplace submission need to be written before Phase 4 build begins. Not a brief — a standards document.

Decisions Log¶

Why white-label for Campus (not branded)? Decided 7 April 2026. RTOs feel more empowered when the tool is invisibly theirs. A secret weapon drives more engagement and purchase than a co-branded platform. Success of the RTO is success for RTOpacks. The InstaLearn identity is preserved in the HTML and in the credential domain — it does not need to be on every learner-facing surface.

Why InstaLearn.com and not InstaLearn.com.au? Decided 7 April 2026. The content is not Australian-specific. Business ethics, communication, leadership, sales — none of it is jurisdiction-dependent. .com positions this as a global product. InstaLearn.com.au was unavailable. InstaLearn.com was available and has been registered.

Why native delivery instead of SCORM-first? Campus uses native Workers-rendered delivery because SCORM was only produced previously due to the absence of an alternative. The 14-step production workflow produced a quarter of the Essential corpus over six months. Native delivery eliminates that entirely. SCORM export exists as an escape hatch, not the primary model.

Why no Credly or Badgr? The credentialing marketplace charges significant fees for infrastructure that is trivially replicable. A self-signed verifiable credential at a trusted domain (InstaLearn.com) is more defensible than a third-party platform the issuer does not control.

Why is Creator free? Content volume is the value. Every Creator course in the Marketplace increases catalogue depth. Every Campus deployment using Creator content generates licensing revenue. Creator is the content flywheel. Charging for it slows the flywheel.

Why is Creator deliberately simple? The moment Creator approaches Studio's capability it loses its purpose and its market. A fish and chip shop owner should be able to build a three-lesson induction in an afternoon without reading a manual. That constraint is a product decision, not a technical limitation. Resist feature creep in Creator.

Why is the student management layer separate from RTOpacks? The Workspace is a B2B tool for RTO operators. Learners are not operators. Mixing learner management into the operator workspace creates the wrong product. The InstaLearn store is a standalone product that reports summary analytics back to the operator — it does not require the operator to manage day-to-day learner interactions.

IL-SPEC-01 v0.1 — RTOpacks — 14 April 2026
Living document. Add to it, don't replace it.
Briefs reference this document. This document does not replace briefs.
Supersedes all prior InstaLearn fragments in the doc database.