RTOpacks Workspace — Product Constitution¶

Document ID: WORKSPACE-PRODUCT-CONSTITUTION
Version: 1.0
Date: 7 April 2026
Status: Canonical — update this document, do not supersede it
Location in repo: docs/product/workspace-product-constitution.md
Companion documents:
- docs/ops/standing-rules.md — operational rules
- docs/ops/infrastructure-reference.md — infrastructure canonical
- docs/ops/kn-personality-standard.md — KN character standard

Purpose of This Document¶

This document is the anchor for all Workspace product development. It exists because the RTOpacks Workspace product has been designed across dozens of sessions since February 2026, and the thinking behind it — the why, not just the what — has been scattered across conversation history. This document consolidates that thinking into a single readable source so that any new session, any new team member, or any future brief can start from a well-understood position without archaeology.

Rule: When a product decision is made in any session that affects the Workspace, it lands here. This document is never stale.

Part 1 — Product Summary¶

What the RTOpacks Workspace Is¶

The RTOpacks Workspace (my.rtopacks.com.au) is a subscriber-facing platform for Australian Registered Training Organisations (RTOs). It is the operational surface where an RTO's management team accesses the full RTOpacks product suite — intelligence tools, compliance tools, content production tools, and integrations.

It is not a public site. It is not an admin panel. It is the subscriber's day-to-day working environment.

What It Is Not¶

It is not a student-facing platform. Learners never touch the Workspace.
It is not a public intelligence tool. The public site (rtopacks.com.au) handles search and discovery.
It is not an ASQA compliance system. It supports compliance work but does not replace an RTO's SMS or compliance obligations.
It is not Rules and Regs (rulesandregs.com.au), which is a separate future product for other regulated industries.

The Commercial Logic¶

RTOpacks solves two problems Joe Newbery identified in his February 2026 article "VET in the Age of AI and Automation":

The national training framework cannot keep pace with employer demand. RTOs that survive will be those who can design and deliver non-accredited training quickly, bolt it onto existing programs, and explain it clearly to employers.
RTOs are drowning in compliance overhead. The tools they use are fragmented, outdated, and disconnected from the training package data they need to operate.

RTOpacks is the infrastructure answer to both problems. The Workspace is where the RTO operator lives. The public site is where the sector finds them.

The Architecture Position¶

The Workspace sits at Layer 3 (World Operator) in the UCCA five-layer model. UCCA owns L1/L2 (God Mode and Staff). RTOpacks owns L3/L4/L4A. The API boundary between L2 and L3 is the security and federation boundary.

L4 — Client Org (RTO manager/admin): Full Workspace access per their subscription tier
L4A — Members (trainers, authors): Narrower grid — Studio, Trainer Mapper, Document Manager only. No intelligence tools, no competitive data.

Part 2 — The Grid¶

Structure¶

The Workspace home screen is an icon grid — three rows of app tiles. The grid is the launcher. Each icon opens its app. The grid is:

Role-aware: L4 sees all three rows. L4A sees a narrower set by default.
Configurable: Users can hide apps they don't use. A reset button restores the default layout for their role. Users cannot reveal apps their role does not permit.
Data-driven: The grid is configured in lib/grid-config.ts. Adding a new app is a config change, not a code change.

The Grid — Current State¶

ROW 1 — CORE PRODUCT
┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│   Studio    │  │   Trainer   │  │  Document   │
│             │  │   Mapper    │  │   Manager   │
└─────────────┘  └─────────────┘  └─────────────┘

ROW 2 — INTELLIGENCE  (L4 admin only)
┌─────────────┐  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│    Radar    │  │  Landscape  │  │ Market Data │  │  Marketer   │
└─────────────┘  └─────────────┘  └─────────────┘  └─────────────┘

ROW 3 — INTEGRATIONS & MARKETPLACE  (L4 admin only)
┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│ SMS Connect │  │     LMS     │  │  InstaLearn │
│             │  │  Connector  │  │             │
└─────────────┘  └─────────────┘  └─────────────┘

Shell Elements (Always Present)¶

Audit Folder — persistent drawer, accessible from any app. Everything from every pipeline step lands here automatically. The compliance dossier, assembled without manual effort.
Account Menu — top right. Credit balance, subscription tier, settings.
Interaction Layer — reserved slot, future brief. The step-down support path.

Part 3 — App Specifications¶

STUDIO¶

Grid label: Studio
Row: 1
Role access: L4 and L4A
Code module: apps/workspace/studio/
Status: In active development

What It Is¶

Studio is the core course design and content production environment. It is a canvas-based tool where RTOs design, map, audit, and produce training content for their nationally recognised training (NRT) programs.

The Problem It Solves¶

RTOs spend enormous time building course materials that must map precisely to TGA training package content — performance criteria, knowledge evidence, assessment conditions. Doing this manually against PDFs on training.gov.au is slow, error-prone, and produces inconsistent outputs. Studio gives them a structured canvas where the mapping happens visually, and AI assists with generation.

The Pipeline Inside Studio¶

Studio contains four tools that operate as a pipeline, left to right:

Composer — the free canvas. Design course structure, drag nodes, set connections (Twilio-style node-and-wire model). Fill response fields against TGA performance criteria. Three modes:
Blank — empty canvas, build from scratch
Shell Fill — pre-populated skeleton from the unit structure
Shell Fill + Edit — skeleton plus AI-drafted content for review
Contextualiser — one AI run against the completed canvas. One considered observation per canvas. References AQF, AQTF, training package frameworks. Arrives with weight — you reckon with it, you don't ignore it.
Auditor — maps completed content to unit outcomes and ASQA standards. Two modes:
Self-audit — free, trainer draws their own mapping arrows
AI audit — paid, AI reads canvas + unit + ASQA standards, cites exact words from the standard, produces tooltip-per-block evidence
Trainer Mapper — given this unit, does this trainer map? Green/amber/red verdict. Printable ASQA-ready report. Works standalone (its own grid icon) or at the end of the Studio pipeline.

The Fill It Handoff¶

After the pipeline, Fill It is the paid content production step. The meter starts here. The context spec produced by Composer/Contextualiser/Auditor is handed to Mavis — the AI content engine — which produces the actual course content. Mavis may be AI (automated) or a human content producer working externally. The Workspace does not distinguish — it receives the output either way.

Credit Model¶

Action	Cost
Canvas graph build	Low
AI Contextualiser run	Medium (Sonnet — quality matters here)
Node seed draft (light assist)	Low-medium
Full content generation	Medium
Corporate context layer (second run)	Medium-high
Video production	High
Voice model training	High
SCORM packaging	Low add-on

Included in subscription: 1,000 credits/month, rollover. Unused credits do not expire. Top-up available on demand.

Technical Notes¶

Canvas runs in apps/workspace/studio/
Content produced by Studio feeds into the Audit Folder automatically
SCORM export is available as a low-cost add-on — but carries an explicit warning: SCORM is a 1990s format. What the RTO sees in Studio will not translate faithfully to a SCORM player. Export at own risk, no support.
The node-and-wire canvas model was inspired by Twilio's visual flow builder. Not Moodle. Not any existing LMS tooling.

TRAINER MAPPER¶

Grid label: Trainer Mapper
Row: 1
Role access: L4 and L4A
Code module: apps/workspace/trainer-mapper/
Status: Specified, pending build

What It Is¶

A credential verification tool. Given a unit of competency and a trainer's qualifications and industry currency, Trainer Mapper produces a green/amber/red verdict on whether that trainer is mapped to deliver the unit.

The Problem It Solves¶

ASQA requires RTOs to demonstrate that every trainer delivering a unit has the relevant qualifications AND industry currency. Maintaining and auditing this mapping manually is one of the most time-consuming compliance tasks an RTO faces. Trainer Mapper automates the assessment and produces a printable, ASQA-ready report.

How It Works¶

Trainer profile is loaded (qualifications, credentials, industry currency dates)
Unit of competency is selected from rtopacks-db
Trainer Mapper reads the unit's requirements against the trainer's profile
Verdict: Green (fully mapped), Amber (mapped with conditions or expiring currency), Red (not mapped — specific gaps identified)
Report generated — printable, suitable for ASQA audit evidence

Technical Notes¶

Reads from rtopacks-db (read-only, as always)
Trainer profiles stored in ops-db
Report output lands in Audit Folder
Can be accessed standalone from the grid or at the end of the Studio pipeline

DOCUMENT MANAGER¶

Grid label: Document Manager
Row: 1
Role access: L4 (admin)
Code module: apps/workspace/document-manager/
Status: Specified, pending build

What It Is¶

RTO policy and procedure document management. The spiritual successor to what Joe Newbery sells as Word document packs with placeholders — but done properly. Pre-built, editable, versioned, stored.

The Problem It Solves¶

Every RTO needs a suite of policies and procedures: complaints policy, assessment policy, marketing policy, RPL policy, continuous improvement policy, and dozens more. Most RTOs either buy Word docs from consultants (Newbery's model) or cobble together their own. Neither approach produces versioned, auditable documents connected to the training standards they reference.

How It Works¶

Pre-built document templates aligned to ASQA Standards for RTOs
RTO fills in their details once (ABN, name, scope, contact) — auto-populated across all docs
Versioning — every edit is tracked, previous versions retained
Documents reference the specific ASQA standard clauses they satisfy
Output lands in Audit Folder

Technical Notes¶

Documents stored in R2 (rtopacks-client-media)
Metadata and version history in ops-db
Template library maintained centrally, pushed to subscribers

RADAR¶

Grid label: Radar
Row: 2 (Intelligence)
Role access: L4 admin only
Code module: apps/workspace/radar/
Status: Data pipeline complete, UI in development
Database: radar-db (d5e88e32)

What It Is¶

Competitive intelligence on the Australian RTO market. 12,508 RTOs in the pipeline. Scope movements, registration changes, risk signals, screenshots of competitor sites captured and stored in R2 (radar-screenshots).

The Problem It Solves¶

RTOs operate in a competitive market but have almost no visibility into what their competitors are doing — what qualifications they're adding or dropping, whether they're growing or contracting, what their public presence looks like. Radar is the outward-facing intelligence layer.

How It Works¶

Continuous sync from TGA data (tga-sync Worker)
RTO scope changes detected and flagged
Competitor site screenshots captured and stored (R2 radar-screenshots)
Risk signals: registration status changes, suspension flags, scope contractions
Filtered to the RTO's relevant geography and qualification scope

Technical Notes¶

radar-db (d5e88e32) — the intelligence store
tga-sync Worker handles ongoing ingestion
Screenshots in R2 radar-screenshots
Read-only from rtopacks-db for NRT data enrichment

LANDSCAPE¶

Grid label: Landscape
Row: 2 (Intelligence)
Role access: L4 admin only
Code module: apps/workspace/landscape/
Status: Data pipeline complete, 115 vendors
Database: landscape-db (dd355937)

What It Is¶

Competitive intelligence on the VET sector tooling ecosystem. 115 vendors tagged and enriched — the LMS providers, SMS vendors, compliance tools, content providers, and consultants that compete for RTO budget and attention.

The Problem It Solves¶

RTOs make vendor decisions in the dark. They don't know who owns what, which products are genuinely independent vs. holding company shells, or how the competitive landscape is shifting. Landscape reveals the structure behind the market.

How It Works¶

115 vendor entities tagged with product category, target market, pricing signals
Legal entity enrichment via WHOIS/ABR — reveals holding companies and related entities
Relationship mapping between vendors (acquisitions, rebrands, partnerships)
Updated on a scheduled cadence

Technical Notes¶

landscape-db (dd355937)
Enrichment runs via qual-enrichment Worker
ABR data cross-referenced for legal entity verification

MARKET DATA¶

Grid label: Market Data
Row: 2 (Intelligence)
Role access: L4 admin only
Code module: apps/workspace/market-data/
Status: Data pipelines complete, UI pending

What It Is¶

Macro intelligence for RTO strategic decision-making. Live stats drawn from ABS, NCVER, TGA, and JSA. The context layer for understanding where the sector is heading.

The Problem It Solves¶

RTOs make scope decisions — which qualifications to add, which to drop — largely on gut feel or anecdote. Market Data gives them the labour market and demographic context to make those decisions on evidence: where vacancies are growing, which occupations are in shortage, what the employment outcomes look like for specific qualifications.

Data Sources¶

ABS Labour Force — unemployment, vacancies, earnings (abs-db 66389f3f, 39,236 rows)
JSA — occupation skill levels, vacancy/new entrant data (osl_ratings, vnda_atlas, jsa_qual_training)
TGA — live RTO count, qualification counts, training package releases
NCVER — enrolment and completion data
yourcareer.gov.au — career pathway enrichment (1,107 quals, 54,640 pathway rows)

Technical Notes¶

abs-db (66389f3f) — ABS Labour Force data
stats-cache Worker — caches live stat bar figures
JSA ingest via dedicated pipeline

MARKETER¶

Grid label: Marketer
Row: 2 (Intelligence)
Role access: L4 admin only
Code module: apps/workspace/marketer/
Status: Specified, pending build

What It Is¶

A digital presence audit for the RTO's own brand. Turns the intelligence lens inward — what does your RTO look like to a prospective student or an ASQA auditor who searches for you?

The Problem It Solves¶

Most RTOs have poor, inconsistent, or inaccurate digital presences. Their training.gov.au listing is outdated. Their Google Business profile has wrong hours. Their website hasn't been touched since 2019. Marketer surfaces these gaps without the RTO having to hunt for them.

How It Works¶

Pulls the RTO's own public data from training.gov.au, myfuture, joboutlook, CRICOS
Audits Google Business profile completeness and review scores
Checks social media presence and posting cadence
Flags directory listing inconsistencies (name, address, contact, scope)
Scores overall digital presence and prioritises improvement actions

Technical Notes¶

Reads from rtopacks-db for scope and registration data
External data fetched via scheduled Worker
Output is a scored report, not real-time

SMS CONNECT¶

Grid label: SMS Connect
Row: 3 (Integrations)
Role access: L4 admin only
Code module: apps/workspace/sms-connect/
Status: Specified, pending build

What It Is¶

Student Management System integration. A configuration screen that connects the RTO's existing AVETMISS-compliant SMS to RTOpacks. Not a built SMS — an integration point.

The Problem It Solves¶

RTOs already have SMS tools (Wisenet, VETtrak, RTOManager, etc.). They don't need RTOpacks to replace them. They need RTOpacks to talk to them — so that enrolment data, completion data, and trainer records can inform the intelligence and compliance tools without manual re-entry.

How It Works¶

Configuration screen: select SMS provider, enter API credentials
RTOpacks reads enrolment and completion data from the SMS
Data used to enrich Trainer Mapper (trainer records), Radar (enrolment trends), and Audit Folder (evidence)
Write-back is out of scope at this stage — read only

Technical Notes¶

Credentials stored encrypted in ops-db
Integration Workers per SMS provider
Twilio AU number (INFRA-AU-01) deferred — Twilio queue has 12 unmatched records pending

LMS CONNECTOR¶

Grid label: LMS Connector
Row: 3 (Integrations)
Role access: L4 admin only
Code module: apps/workspace/lms-connector/
Status: Specified, pending build

What It Is¶

Learning Management System integration. Dual mode: connect an existing LMS, or provision a hosted instance.

The Problem It Solves¶

SCORM packages produced by Studio need somewhere to land. RTOs that already have Moodle (or similar) need a clean handoff. RTOs that don't have an LMS need a path to one that doesn't involve a six-month implementation project.

Two Modes¶

Connect — wire up their existing LMS. Moodle is the primary target. SCORM packages push directly. xAPI support is a future consideration.
Provision — spin up a hosted instance (future capability, not first build). Managed by RTOpacks infrastructure, billed as an add-on.

Technical Notes¶

SCORM export from Studio delivers through here
Mode 2 (provision) is post-revenue — do not build yet
The SCORM warning applies: export fidelity is not guaranteed relative to the native Studio experience

INSTALLEARN¶

Grid label: InstaLearn
Row: 3 (Integrations & Marketplace)
Role access: L4 admin only to configure / L4A to browse catalogue
Code module: apps/workspace/installearn/
Status: OBJECT-01 complete (schema), INSTALEARN-DEPLOY-01 pending
Databases: microcredentials-db (3924412d)
Credential domain: InstaLearn.com (registered 7 April 2026)

What It Is¶

A turnkey non-accredited content delivery system. The RTO selects courses from the InstaLearn catalogue, deploys a white-labelled learning store to their own domain or subdomain, and starts selling or assigning professional development content to learners — without building anything, configuring an LMS, or producing any content.

The Context (Why This Exists)¶

Joe Newbery's February 2026 article 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 non-accredited content quickly. InstaLearn is that response — a ready-made catalogue of general workplace knowledge content that RTOs can deploy immediately under their own brand.

The content fills the gap Newbery identified: employers want training now, not when the next training package review cycle completes.

The 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 Content Taxonomy¶

Four-level hierarchy 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 InstaLearn Essential unit (one lesson, one video, one quiz)
Course — a compiled InstaLearn DeepDive (ordered collection of Modules with section structure)

Approximately 600+ Essential modules and 100 DeepDive courses in the catalogue, derived from the Articulate Rise taxonomy as a topic blueprint. All titles rewritten — original Articulate titles stored in original_ref for traceability, not displayed anywhere.

The Content Origin¶

The topic map was drawn from Articulate's Rise course library — specifically their two-tier structure of short lessons and compiled courses. Articulate's taxonomy reflects years of research into what corporate L&D teams need. The content itself is original — generated through the engine, not Articulate's SCORM packages. The Articulate structure is used as a blueprint only.

Content clusters into four underlying themes (the "white-collar workplace anxiety" read): 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 (the mandatory tier) 4. Role capability — leadership, sales, marketing, project management, customer service

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

The Deployment Model¶

This is not an LMS the RTO manages. It is a managed service RTOpacks provisions on their behalf.

What the RTO does: 1. Opens InstaLearn from the Workspace grid 2. First-run configurator: branding (logo, colours), store name, domain/subdomain, Stripe account (theirs or we set one up), course selection 3. We spin up a Cloudflare account in their name — Workers + D1 + KV + domain 4. Their store is live

What RTOpacks manages: Everything. The infrastructure runs. The content serves. The checkout works. The RTO's job is marketing.

What the RTO's job is: Marketing. Get on TikTok. Get on Instagram. Push the commuter angle — people on buses learning instead of gaming. Market to corporate employers as staff professional development. The content is there, the checkout is built, the credential issues automatically. There is no support required because nothing breaks.

Multiple instances: An RTO can run more than one store (e.g. a public-facing store and a private staff training portal). Additional instances are a paid add-on.

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. More success = more courses purchased.

InstaLearn branding exists in: - The Workspace grid icon 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

Credential Issuance¶

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 at InstaLearn.com 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 ours and it is better.

The credential domain (InstaLearn.com) is intentionally separate from RTOpacks for two reasons: 1. Branding: A learner verifying a credential should not land on a page that says "RTOpacks" — that's an operator platform name, not a credentialing authority name 2. Technical: Keeping the credential verification server separate from the B2B platform is correct architecture. Separate concern, separate surface.

The SCORM Exit¶

If an RTO wants to take their selected courses and run them in their own LMS: - They can export as SCORM - They receive the SCORM package with an explicit upfront warning: "SCORM is a format written in the 1990s and played on tools like Moodle. What you have experienced 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." - When they leave: they keep the Cloudflare account and the domain. They do not keep the content experience — that requires the connection to generate. They receive their SCORM export. That is the exit path.

Student Management¶

The learner-facing store has its own self-contained student management. It does not live in RTOpacks. It does not require RTO staff to manage it.

Learner signs up, enters details
Pays via Stripe (RTO's Stripe account — they keep the margin, RTOpacks takes a platform fee)
Completes course, passes quiz
Credential issued and stored in learner record
If they lose access: they re-register with the same details, credential is re-issued

No support line. No helpdesk. No calls about pointing DNS. The system is self-serve by design. If a learner loses their password, they use the recovery flow. If they want their credential reissued, they log back in. That is the entire support surface.

What Is Not In This Brief¶

Content production pipeline (generating scripts, videos, quiz questions from the taxonomy) → INSTALEARN-CONTENT-01
The headless LMS deployment system (Cloudflare account provisioning, Workers/D1/KV stack, storefront) → INSTALEARN-DEPLOY-01
Workspace Studio UI for browsing the InstaLearn catalogue → separate UI brief
InstaLearn.com domain configuration and credential Worker → INSTALEARN-DEPLOY-01

Part 4 — Shell Elements¶

Audit Folder¶

Not an app. A persistent drawer accessible from every app in the Workspace.

Everything produced by the pipeline lands here automatically: Composer outputs, Contextualiser observations, Auditor reports, Trainer Mapper verdicts, Document Manager versions. The compliance dossier assembles itself.

When ASQA knocks, the RTO opens the Audit Folder. The evidence is there, organised, versioned, timestamped.

Top-right shell element. Credit balance (live), subscription tier, plan details, settings link, sign out.

The credit meter is visible here. It is not a global shell element shown on every screen — only in the Account Menu. Running tally is visible inside Studio canvas during a session.

Interaction Layer¶

Reserved slot. Future brief. This is the step-down support path — the mechanism by which UCCA staff or an L2 operator can step into a subscriber's context to assist. Not built yet. Do not confuse with the customer support function.

Part 5 — Commercial Model¶

Subscription Tiers (Indicative)¶

Plan	Seats	Monthly
Starter	1	~$399
Pro	5	~$699
Enterprise	100	Custom

Additional seats purchasable within a tier at ~$35/user/month. The seat math eventually tips in favour of upgrading tiers — that is intentional.

The Seat Model¶

The org entity carries:

{
  "org_id": "rto-001",
  "plan_tier": "starter",
  "base_seats": 1,
  "purchased_seats": 2,
  "active_members": 3,
  "seat_limit": 3
}

Seat enforcement lives at token issuance. If active_members >= seat_limit, no new L4A token is issued. Clean, unfakeable, no UI tricks required.

The InstaLearn Revenue Model¶

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

Credits¶

Credits are consumed by AI-assisted actions in Studio. Subscription includes a monthly allocation with rollover. Top-up available. Credits do not expire.

Part 6 — Decisions Log¶

This section captures the why behind key product decisions so they are not re-litigated in future sessions.

Why white-label for InstaLearn (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 anyway. InstaLearn.com was available and has been registered.

Why keep the credential domain separate from RTOpacks? Decided 7 April 2026. "RTOpacks" is a B2B operator platform name. A learner landing on RTOpacks to verify their professional development credential would be confused and the brand signal would be wrong. InstaLearn.com is the right credential authority identity — neutral, learner-friendly, global.

Why native delivery instead of SCORM-first? Decided 7 April 2026. SCORM was produced by the prior InstaLearn workflow (Articulate → SCORM → LearnWorlds) because there was no alternative. The 14-step production workflow took six months to produce a quarter of the Essential corpus. Native Workers-rendered delivery eliminates that entirely. SCORM export exists as an escape hatch for RTOs with existing LMS infrastructure, not as the primary model.

Why no Credly/Badgr for credentials? Decided 7 April 2026. The credentialing marketplace charges significant fees for infrastructure that is trivially replicable. UCCA already has Apple Wallet pass infrastructure, the VCC architecture is designed, and a self-signed verifiable credential at a trusted domain (InstaLearn.com) is more defensible than a third-party platform that the issuer does not control. The market for digital credentials is fragmented and expensive for no good reason.

Why is the student management layer separate from RTOpacks? Decided 7 April 2026. 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 back to the operator via the Workspace — it does not require the operator to manage day-to-day learner interactions.

Why is the Workspace grid data-driven? Decided April 2026 (WORKSPACE-01 session). Adding a new app should not require changes to the grid rendering logic. lib/grid-config.ts is the single source of truth for what appears in the grid, in what order, and for which roles. This is how you scale a product surface without it becoming a maintenance problem.

Why is Audit Folder a persistent drawer and not an app? Decided April 2026. The Audit Folder is the compliance dossier. It should always be reachable regardless of what app the operator is in. Making it an app would require the operator to navigate away from their current context to access evidence they may need while working. A persistent drawer solves this without breaking flow.

Why Studio, not just a document builder? The RTO compliance problem is not a document problem — it is a mapping problem. RTOs need to demonstrate that their content maps to the training package. A document builder produces documents. A canvas-based mapper with an AI layer produces evidence. Those are different products with different audit outcomes.

Part 7 — What Is Not in the Workspace¶

Rules and Regs (rulesandregs.com.au) — a separate future product. Standalone compliance document platform for other regulated industries (accounting, etc.). Builds after RTOpacks generates revenue. Do not confuse with Document Manager.

KN (Knowledge Navigator) — KN is a character, not a Workspace app. KN lives on the public site within the unit and qualification detail pages. KN is not in the grid. KN is not a product feature. KN is a persona with a standard (see docs/ops/kn-personality-standard.md).

Mavis — not a grid icon. The AI content engine and/or human content producer. The handoff from Studio's Fill It step. Mavis receives the context spec and produces content. The Workspace does not manage Mavis directly.

Carol — not a product. A persona representing any human who chooses to author content manually into the Studio canvas rather than using AI generation. Carol is accommodated by the Studio spectrum without needing a separate feature.

Direct learner access — learners do not have Workspace accounts. Learners access InstaLearn through the RTO's white-label store. If InstaLearn.com eventually supports direct-to-learner enrolment (bypassing the RTO channel), that is a future product extension, not a current Workspace feature.

RTOpacks Workspace Product Constitution v1.0
Compiled: 7 April 2026
Next review: When a new app is confirmed for the grid, or when a major product decision changes the model.
"The tool is ours. The output is yours."

RTOpacks Workspace — Product Constitution¶

Purpose of This Document¶

Part 1 — Product Summary¶

What the RTOpacks Workspace Is¶

What It Is Not¶

The Commercial Logic¶

The Architecture Position¶

Part 2 — The Grid¶

Structure¶

The Grid — Current State¶

Shell Elements (Always Present)¶

Part 3 — App Specifications¶

STUDIO¶

What It Is¶

The Problem It Solves¶

The Pipeline Inside Studio¶

The Fill It Handoff¶

Credit Model¶

Technical Notes¶

TRAINER MAPPER¶

What It Is¶

The Problem It Solves¶

How It Works¶

Technical Notes¶

DOCUMENT MANAGER¶

What It Is¶

The Problem It Solves¶

How It Works¶

Technical Notes¶

RADAR¶

What It Is¶

The Problem It Solves¶

How It Works¶

Technical Notes¶

LANDSCAPE¶

What It Is¶

The Problem It Solves¶

How It Works¶

Technical Notes¶

MARKET DATA¶

What It Is¶

The Problem It Solves¶

Data Sources¶

Technical Notes¶

MARKETER¶

What It Is¶

The Problem It Solves¶

How It Works¶

Technical Notes¶

SMS CONNECT¶

What It Is¶

The Problem It Solves¶

How It Works¶

Technical Notes¶

LMS CONNECTOR¶

What It Is¶

The Problem It Solves¶

Two Modes¶

Technical Notes¶

INSTALLEARN¶

What It Is¶

The Context (Why This Exists)¶

The Two Content Tiers¶

The Content Taxonomy¶

The Content Origin¶

The Deployment Model¶

The White-Label Model¶

Credential Issuance¶

The SCORM Exit¶

Student Management¶

What Is Not In This Brief¶

Part 4 — Shell Elements¶

Audit Folder¶

Account Menu¶

Interaction Layer¶

Part 5 — Commercial Model¶

Subscription Tiers (Indicative)¶

The Seat Model¶

The InstaLearn Revenue Model¶

Credits¶