RTOpacks Workspace — Product Glossary¶
Version: 2.0
Date: 3 June 2026
Status: CANONICAL — read before writing any workspace brief
Scope: apps/workspace/ — the subscriber surface at my.rtopacks.com.au
This document defines every named product in the RTOpacks workspace. These names are canonical — they are the marketing names, the UI labels, and the code module identifiers. Do not deviate without Tim sign-off.
Changelog¶
| Version | Date | Changes |
|---|---|---|
| 1.0 | 4 Apr 2026 | Initial — all workspace products defined; Row 1/2/3 shell model; L4/L4A roles. |
| 2.0 | 3 Jun 2026 | Restructured around the four shipped launcher groups (Intelligence / Course Creation / Learning / Integrations). Roles updated L4→T4, L4A→T4A per ADR-020. People & Culture → People; Document Manager → Record. GenEd Store retired and superseded by Campus + Marketplace. Learning group documented for the first time (Creator, InstaLearn, Campus, Marketplace) — the non-regulated education stream. SMS Connect / LMS Connector identified as regulated-side connectors. Substrate IDs removed (they belong in the architecture docs and were going stale here). |
The Shell¶
The workspace is an icon-grid launcher — an iPad-home-screen model in landscape. One app open at a time, full viewport. The home icon returns to the grid. Tiles are organised into four groups (below); within a group, tiles a user's role permits can be reordered, and tiles for unreleased products show a "Coming soon" state.
The four groups are capped at four. New products may be added as tiles within an existing group as they are built; the group structure itself is fixed and reviewed only once the current roadmap is delivered.
Shell Elements (always visible, not grid icons)¶
Audit Folder — a persistent drawer reachable from every app. Holds the compliance dossier for each course; everything produced by Studio, People, and Record lands here automatically. Folder icon with a count badge; click to slide out the dossier. The dossier assembles itself as a by-product of working — it is not a pipeline step. Code: apps/workspace/components/shell/AuditFolder/.
Identity menu — top-right shell element (avatar with image-or-initials fallback, dropdown). Reads top-to-bottom: who (name · role label derived from the canonical tier per ADR-020 — never the raw L1–L4 — · credit balance) → Personal Settings (the user's site-wide preferences home at /settings, including the Experience/accessibility controls folded from the retired gear FAB) → account block (Admin · Subscription · Invoices · top-up credits — tier-gated: T4 administrator only, hidden for T4A) → Sign out. Code: apps/workspace/components/shell/AccountMenu.tsx.
Interaction Layer (future — reserved slot) — context-aware co-pilot that speaks only when it has something worth saying; knows where the user is in the workflow. Not a chatbot. Code: apps/workspace/components/shell/InteractionLayer/ (stub only).
Group 1 — Intelligence¶
Sector reference and research tools. Dip in at any point. T4 administrator only — not visible to T4A.
Radar¶
Grid icon label: Radar
Code module: apps/workspace/radar/ (also: Field Observer topology map)
Role access: T4
Sector intelligence — the outward-facing layer. Competitive landscape, scope movements, registration changes, risk signals across the RTO pipeline. The Field Observer map provides site-topology and digital-footprint analysis per RTO.
Landscape¶
Grid icon label: Landscape
Code module: apps/workspace/landscape/
Role access: T4
Tagged-entity database of VET-sector vendors. Competitive intelligence on the tooling ecosystem, with legal-entity enrichment (WHOIS/ABR) revealing holding companies.
Market Data¶
Grid icon label: Market Data
Code module: apps/workspace/market-data/
Role access: T4
Macro intelligence. Live stats — unemployment, job vacancies, average weekly earnings, current RTOs, current quals — sourced from ABS, NCVER, TGA. Context for strategic decisions.
Marketer¶
Grid icon label: Marketer
Code module: apps/workspace/marketer/
Role access: T4 (and, per WS-PRODUCT-01, may be operated by a marketing-team user profile distinct from the compliance team, with no access to People or the compliance layer of Record)
Turns the lens inward. Audits the RTO's own digital presence: website quality, Google Business profile, social presence, review scores, directory-listing accuracy (training.gov.au, myfuture, joboutlook). The question it answers: what does this RTO look like to a prospective student — or an ASQA auditor — who searches for it?
Group 2 — Course Creation (the compliance spine)¶
The regulated training-and-assessment pipeline, grounded in TGA units of competency in rto-nrt-db. This group is the compliance spine described in WS-PRODUCT-01: Studio designs, People holds the workforce, Record holds the evidence. The launcher labels it "Course Creation"; canonically it is the spine. Both T4 and T4A have access to this group (per-module below).
Studio¶
Grid icon label: Studio
Code module: apps/workspace/studio/
Role access: T4 (administrator), T4A (trainer/author)
Tier: Included with subscription (credit model applies for production output)
The centrepiece of the regulated product. A unified visual workflow canvas for designing, building, and auditing training courses against TGA units of competency.
The canvas: node-graph interface (drag-and-connect). The TGA unit loads into the canvas with elements and performance criteria as locked anchors. Content nodes (written content, pop quiz, upload task, scheduled video call, observation checklist, practical demonstration, others) are dragged on and connected to PC anchors. Multiple PCs can be grouped ("blobbed") when one activity addresses several. Coverage is visual — unconnected PCs are obvious.
Validation mode: a canvas toggle showing audit state. Green = fully mapped, Amber = partial, Red = no coverage. PC anchors cite the exact clauses from the 2025 Outcome Standards Instrument (F2025L00354) and relevant ASQA Practice Guides.
The AI observation: one AI run against the completed canvas, building outward from the unit — AQF level, legislation, training-package framework, industry context, prerequisite knowledge, assessment conditions. Arrives as an enriched layer on the canvas. One run per session (re-run is deliberate). A deeper corporate-context layer (second inference run against client-specific context) is a paid feature.
Fill spectrum: the content-production handoff — a mode transition inside the canvas when mapping is complete. Five points: (1) Pure human — framework only; (2) Light assist — AI seeds drafts, human owns voice; (3) Heavy AI, human review; (4) Full production — AI generates and polishes, branded video/voice/SCORM; (5) External production — context_spec.json handed to an external author. The canvas framework is the brief.
Credit model: 1,000 credits/month included, rollover, no expiry. Graph build low; node seed low-medium; full generation medium; video/voice/branding higher. A "Price It" drawer shows the running tally for the current course. Top-ups on demand.
Session continuity: the Studio icon opens a landing screen of recent sessions (unit code, title, coverage, last edited). Resume or start new; the grid icon shows a resume badge when a session is active.
People¶
Grid icon label: People
Code module: apps/workspace/people/
Role access: T4 (administrator) — may surface read-only to T4A
Tier: Included with subscription
Workforce compliance. The authoritative record of every person involved in training and assessment delivery — credentials, industry competency, professional development, supervision, and compliance status against the Standards.
Views: an Org Chart (interactive reporting-line graph; filter by trainers/assessors/staff; click a node for a detail drawer); a People table (sortable/filterable; TAE status and industry-currency badges at a glance); and a Trainer Matrix mapping trainers against qualifications on scope, exportable for audit.
Per-person record: contact and employment details, TAE credential with verification status, USI transcript-sharing status, vocational qualifications, industry-currency log, professional-development log, document storage.
Trainer-mapping (credential verification against specific units) is embedded here: given a unit, does a named trainer map? Three verdicts — Green (maps), Amber (addressable gaps), Red (does not map). Trainer compliance reports land in the Audit Folder automatically.
Record¶
Grid icon label: Record
Code module: apps/workspace/record/
Role access: T4 (administrator)
Tier: Base (audit trail) / Mid (full policy framework) / Top (CRICOS, ELICOS, enterprise packs)
Status: Specced (RECORD-SPEC-01 v0.2), not yet built
The evidence layer, and the canonical name for what was previously "Document Manager" and the now-retired "Documents" module. A live, version-controlled compliance system — not static Word docs in a folder.
What it holds: all required policy and procedure documents for RTO compliance (Outcome Standards for RTOs 2025 / F2025L00354, Compliance Standards for RTOs 2025, Credential Policy 2025, AQF, Fit and Proper Person Requirements, Data Provision Requirements 2020); training and assessment materials produced by Studio; trainer-mapping reports; and the Audit Folder contents as a structured dossier.
What makes it different: it is live (when ASQA updates a standard, affected policies flag automatically), connected (complaints policy ↔ complaints register, currency policy ↔ trainer-mapping, validation schedule ↔ Studio audit mode), and the evidence falls out automatically because every workspace action is logged. Traffic lights are earned — they go green because something actually happened in the system, not because a review date passed.
Tier structure: Base (included) stores everything Studio and People produce — the auto-assembled audit trail. Mid (paid) adds the full live, connected policy framework. Top (paid) adds CRICOS, ELICOS, and enterprise packs.
Record is the trust bridge: the familiar artefacts (the policy document, version number, review date, printable audit report) are the interface between a new compliance system and people who have spent twenty years in the old one.
Group 3 — Learning (the non-regulated education stream)¶
General education, distinct from the regulated spine. Where the spine is grounded in TGA units in rto-nrt-db, this stream is non-regulated and lives in rto-micro-db — the HARD SEPARATION line runs between the regulated Course Creation spine and the non-regulated Learning stream. Four products form a chain: Creator authors, InstaLearn is the artefact, Campus delivers and sells, Marketplace licenses on.
InstaLearn¶
Grid icon label: InstaLearn Role access: T4 (authoring/configuration); credentials are issued to end learners Status: Coming soon — not yet built
The verifiable microcredential — content and credential bundled. A short non-regulated course (authored in Creator) that, on completion, issues a verifiable but non-accredited microcredential, branded under the RTO's white label. The verification is the value — it is a genuine, checkable credential, a step above an ordinary general-education course. It is not a nationally recognised AQF qualification (Certificate II/III/IV, diploma) and does not pretend to be; that accreditation belongs to the regulated spine and is deliberately out of scope here. Non-accredited is correct — it is GenEd.
Campus¶
Grid icon label: Campus Role access: T4 (configuration/provisioning); end learners are external students, outside the RTOpacks tier model Status: Coming soon — not yet built
RTOpacks' own white-labelled LMS — gen-ed only. Regulated delivery never touches Campus (that goes out via LMS Connector to the RTO's existing LMS). Campus runs as a separate deployment in Cloudflare, on the RTO's own domain or subdomain, provisioned per-RTO with Stripe hooks and automation, and carries a light built-in student-management capability. Content is pushed from the RTOpacks core into Campus via LTI (Learning Tools Interoperability) — the core is the tool provider, Campus the platform.
The provisioning model: the RTO sets up a subdomain (or registers a domain through Cloudflare), and we stand up an LMS seeded with the 20 free InstaLearn courses we have built, so there is value on day one. The RTO picks the courses to offer, sets their prices, and has a microlearning business running alongside the RTO. Pick courses, set price, push go.
Creator¶
Grid icon label: Creator Role access: T4 (parallels Studio's authoring access) Status: Coming soon — not yet built
Studio with the regulated scaffolding removed — "Studio lite." The same authoring tools, but no TGA unit reference, no performance-criteria mapping, no compliance validation. You arrive with an idea ("a course on how to make soap") and build it. Creator produces InstaLearn courses.
Marketplace¶
Grid icon label: Marketplace Role access: T4 Status: Coming soon — not yet built
Where a creator can sell or license the courses they have built — to other RTOpacks users initially, and in a future version as a public marketplace for buyers seeking SCORM general-education products. Where Campus sells courses to learners, Marketplace distributes the course itself to other producers.
(Supersedes the v1.0 "GenEd Store", whose store/delivery function is now Campus and whose catalogue/licensing function is now Marketplace.)
Group 4 — Integrations¶
Connection points to the RTO's existing systems. These are regulated-side connectors — they exist because a compliance-bound RTO is already invested in its own SMS and LMS, and forcing it onto ours would be both unrealistic and a liability we do not want. Mix of T4/T4A depending on configuration.
SMS Connect¶
Grid icon label: SMS Connect
Code module: apps/workspace/sms-connect/
Role access: T4 (admin) to configure
Student Management System integration. A configuration surface to connect the RTO's existing AVETMISS-compliant SMS (Wisenet, VETtrak, RTOManager, etc.) and pull the compliance-relevant signals. Not a built SMS — an integration point. The student record stays in the RTO's SMS.
LMS Connector¶
Grid icon label: LMS Connector
Code module: apps/workspace/lms-connector/
Role access: T4 (admin)
Learning Management System integration for regulated delivery. Connects the RTO's existing LMS (Moodle, Blackboard, Canvas), and delivers Studio's SCORM packages out to it, pulling delivery-confirmation and completion data back into the compliance picture. Distinct from Campus: LMS Connector reaches the RTO's own/external LMS; Campus is our gen-ed LMS.
(Future UI note: SMS Connect and LMS Connector may move behind a unified Settings panel with per-platform connector tabs — standard Moodle/Blackboard/Canvas setups the RTO fills in. Captured as a refinement, not yet built; they remain Integration tiles for now.)
Role Reference¶
Roles follow ADR-020: T4 is the client-administrator tier (the RTO manager); T4A is the client-user tier (trainer/author). (T3, the operator tier, is RTOpacks staff and does not appear in the workspace launcher.)
| Role | Intelligence | Course Creation | Learning | Integrations |
|---|---|---|---|---|
| T4 — Client administrator | Full | Full | Full | Full |
| T4A — Client user (trainer/author) | No access | Studio; People (read) | Per module spec when built (Creator authoring expected to parallel Studio) | SMS Connect (read) |
Users can hide apps their role permits; they cannot reveal apps their role does not. Reset snaps back to the role default.
What Is Not In The Workspace¶
Rules and Regs (rulesandregs.com.au) — a separate future product, a standalone compliance-document platform for other regulated industries (accounting etc.). Built after RTOpacks generates revenue. Not to be confused with Record.
Carol — not a product, a persona: any human who chooses to author content manually into the Studio canvas rather than using AI generation. The fill spectrum accommodates Carol.
Mavis — not a grid icon: the AI content engine (and the name for an external human content producer). The handoff target from Studio's fill spectrum.
RTOpacks Workspace Glossary v2.0 · 3 June 2026 "The tool is ours. The output is yours."