The Composer — Commercial Model¶

Commercial Model + Copyright + Storage

10 March 2026 | Tim Rignold, UCCA

The template marketplace exists because building from scratch against the TGA is hard. The Composer makes building from scratch easy — and makes what you build yours in a way no template ever could.

1. The Market This Replaces¶

There is a thriving secondary market in Australian VET for purchased course templates. RTOs buy Word documents — forty-seven pages of someone else's work, $299 on a marketplace — and spend weeks making them look like original authorship. Logo swapped. Headings reorganised. A few paragraphs rewritten.

This market exists for one reason: building a compliant course from scratch against the TGA is hard. Reading the unit, mapping the performance criteria, structuring the content, checking the assessment conditions — it takes time and expertise that most RTO staff have but can't always allocate to a blank page.

The template gives them a starting point. The problem is the starting point is wrong. It was written for a different training package version, a different learner cohort, a different delivery context. The RTO inherits someone else's compliance assumptions and spends weeks regressing them into something that fits their reality.

They are not buying content. They are buying permission to start writing. The Composer gives them that permission — from the actual TGA, not someone's three-year-old interpretation of it — for free as part of the tool.

The regression tax¶

Every purchased template carries a regression tax — the time and effort required to undo someone else's assumptions and replace them with your own.

The Composer eliminates the regression tax entirely. The spec is generated from the live TGA corpus. It has no prior assumptions to undo. Mavis starts with a clean slate that already knows what it needs to contain.

The template marketplace loses its reason to exist. Not because The Composer is cheaper — because it is more correct.

2. Copyright and Attribution¶

Every course produced by The Composer carries a formal attribution block — the oldest idea in publishing, made cryptographically verifiable for the first time.

DOCUMENT ATTRIBUTION
© 2026 TAFE Queensland. All rights reserved.
Author:  Mavis Cravits, Curriculum Developer
Created on behalf of:  TAFE Queensland, Brisbane Region
Authoring tool:  The Composer — UCCA (ucca.online)
Unit:  BSBLDR522  Manage people performance
Qualification:  BSB50420 Diploma of Leadership and Management
Completed:  10 March 2026
Provenance:  env_01JXYZ...   ·   Verify at keys.ucca.online

This attribution block appears on the inside cover of every course pack produced by The Composer. It is generated from the envelope — the author's identity, the institution's name, the unit details, the completion date, and the envelope ID for cryptographic verification.

The copyright belongs unambiguously to the institution. Mavis is the named author. UCCA is the tool — not the author. This is the same attribution structure used by every professional publishing tool from Adobe InDesign to Microsoft Word, except no other tool backs it with a cryptographic proof chain.

Why this matters commercially¶

An institution that purchases a template owns nothing — the original author retains copyright, the licence is typically non-exclusive, and any customisation lives in legal grey water.
An institution that uses The Composer owns the course outright. Their copyright. Named author. Verifiable provenance. No licence terms to navigate. No risk of a competing RTO running the same template.

For TAFE Queensland's legal team — this is the cleaner position. For their curriculum writers — this is professional recognition. For their auditors — this is an airtight trail.

3. Multi-Session Storage and the Revision Model¶

Mavis does not write a course in one sitting. She writes element 1 on Monday, comes back to element 3 on Wednesday, revises the assessment section after a conversation with her manager on Friday. The Composer saves her work continuously into a client-scoped storage bucket — not UCCA's infrastructure, the institution's.

3.1 — Storage architecture¶

rtopacks-clients/
└── tafe-qld/                          ← provisioned at institutional onboarding
    └── mavis-cravits/                 ← author-scoped
        └── BSBLDR522/                 ← unit-scoped
            ├── draft-v1/              ← current working draft
            │   ├── spec.json          ← context_spec — what needs to be written
            │   ├── content.json       ← Mavis's work in progress
            │   └── session_log.json   ← who edited what, when
            ├── published-v1/          ← first published version
            │   ├── course.pdf
            │   ├── envelope.json      ← signed, immutable
            │   └── attribution.json
            └── published-v2/          ← revision published later
                ├── course.pdf
                └── envelope.json      ← new envelope, links to v1 via parent_envelope_id

UCCA never holds Mavis's content. The draft lives in TAFE Queensland's bucket. UCCA holds only the envelope receipts — the transaction log and the signed hallmarks. The shop floor is clean. The content belongs to the institution from the moment Mavis types the first word.

3.2 — The continuation / revision decision¶

When Mavis returns to a unit she has previously worked on, The Composer presents a simple decision:

Welcome back, Mavis.
BSBLDR522  ·  Last edited 8 March 2026  ·  4 of 6 sections complete
─────────────────────────────────────────────────
[ Continue ]  Pick up where you left off
[ Revise ]    Save current draft as v1 — start a revision
[ New version ]  Publish current draft — begin a new version

Continue — no charge, no new envelope, same draft. Mavis finishes what she started.
Revise — the current draft is archived as a named version. A new draft opens from the same spec. The revision is a new job when published — new envelope, new signature, parent_envelope_id links to the prior version. The provenance chain is unbroken.
New version — publishes the current draft first, then opens a fresh authoring session. Two jobs, two envelopes, one unit with a clear version history.

4. The Training Package Update Cycle¶

The most underappreciated revenue driver in Australian VET is training package currency. When Standards Australia or a Skills Service Organisation releases a new version of a training package — BSB, CHC, SIT, CPC — every RTO delivering those qualifications must review and update their learning and assessment materials.

This is not a one-off event. Training packages are updated on rolling cycles. For a TAFE with a large catalogue across multiple training packages, this is a continuous compliance workload with no natural end.

4.1 — What happens when a training package updates¶

The TGA corpus in UCCA reflects the updated training package — new unit versions, new performance criteria, new assessment conditions
The Composer detects that a unit Mavis previously authored has been updated in the TGA
She receives a notification: BSBLDR522 has been updated — Release 2 is now current
The Composer generates a new context_spec.json from the updated unit
It diffs the new spec against Mavis's published v1 — highlighting what changed, what carried over, what is new
Mavis opens a revision session with the changes highlighted — she does not start from scratch, she addresses the delta

The subscription argument¶

This is why The Composer works better as a subscription than as a per-course transaction for institutional clients.

TAFE Queensland does not buy a course. They subscribe to a currency maintenance service. The Composer keeps their catalogue current against the TGA. Every training package update is handled in the tool they already use. The subscription cost is the cost of compliance — which they were paying anyway in staff time.

The question for the TAFE director is not "should we pay for this?" It is "do we want to pay this way — predictable subscription — or the old way — irregular staff time surges every time the TGA updates?"

5. Commercial Model¶

Three tiers. Each serves a distinct segment. Each has a natural upgrade path to the next.

Tier	Price	Audience	Includes
Transact	$29 / course	Small RTOs, first-time users	Pay per published course, full Composer authoring, signed envelope + QR, attribution block, client R2 storage, no Dr Sheffield
Author	$49 / seat / month	Active curriculum writers, TAFE teams	Unlimited courses + revisions, multi-session drafts, full version history, Dr Sheffield included, training package update alerts, priority support
Institution	From $499 / month	TAFE, enterprise RTOs, government	Unlimited authors, institutional storage bucket, admin dashboard, workflow manager, training package currency dashboard, custom attribution template
Enterprise	Contract	Defence, regulated sectors, offshore	Air-gapped deployment option, on-premise storage, custom key server, SLA + support contract, professional services, compliance framework customisation

5.1 — Dr Sheffield as the Author-tier differentiator¶

Dr Sheffield is the feature that makes Author tier worth the upgrade from Transact. He is not available on Transact. He is included on Author and above. His value compounds over time — the more Mavis uses The Composer, the better Dr Sheffield understands the coverage patterns she tends to miss, the unit types she finds challenging, the assessment approaches she favours.

That personalisation is the retention mechanism. Mavis on Author tier has a Dr Sheffield who knows her. Moving to a competitor means starting that relationship again from scratch.

5.2 — The natural upgrade path¶

Trigger	Upgrade
Mavis publishes her third course on Transact	Email: "You've published 3 courses. Author tier would have saved you $38 this month. Try it free for 30 days."
Manager sees Mavis using it, wants it for the team	Institution tier — admin dashboard, workflow assignment, team reporting
Training package update affects 20+ units in their catalogue	Institution tier — currency dashboard shows affected units, assigns revisions to authors, tracks progress
Government or defence client requires air-gapped deployment	Enterprise contract — on-premise, custom key server, SLA, professional services engagement

6. The Offshore Market¶

The Composer's commercial model translates directly to the markets Jimmy is developing — Taiwan, Southeast Asia, any jurisdiction that needs structured vocational training materials built against a recognised framework.

The TGA is the Australian corpus. But the Composer architecture is framework-agnostic. A Taiwanese vocational training authority has its own competency framework. A Singapore polytechnic has its own. The engine reads whatever corpus is loaded for that world. The spec it produces is derived from that framework. Mavis becomes a Taiwanese curriculum writer working against a Taiwanese qualification framework — and the product is identical.

For Jimmy¶

The Composer is the product that gets UCCA into the room. The enterprise licence is what gets UCCA into the budget.

The pitch is not "AI course generation". The pitch is "professional authoring infrastructure for your curriculum team — with full provenance, full attribution, and full compliance currency".

The monastery has a composer in residence. The institution owns the music.

The Composer · Commercial Model + Copyright + Storage The template marketplace loses its reason to exist. Not because The Composer is cheaper — because it is more correct.

Version History¶

Version	Date	Change	Author
1.0	2026-03-11	Converted from UCCA-The-Composer-Commercial.docx	Claude Code