The Composer — Product Architecture¶
Professional course authoring for VET practitioners.
10 March 2026 | Tim Rignold, UCCA
The Composer writes. The Orchestrator arranges. The performance is the proof.
1. The Insight¶
The largest market in Australian VET is TAFE. TAFE is also the market most resistant to AI-assisted content generation — not because the practitioners are wrong, but because they have watched seventeen revolutionary education technologies arrive and disappear since 1987. They are not Luddites. They are experienced.
These practitioners — AO7 curriculum writers, senior trainers, department heads with thirty years of institutional knowledge — have a real problem. Writing compliant training materials against the TGA is slow, structural, and unforgiving. They do it anyway because it is their craft. They are good at it. But they are understaffed, underfunded, and under constant pressure to produce more with less.
They will not use a tool called anything resembling AI. They will not accept that a machine generated their course materials. Their professional identity is bound up in authorship. They wrote this. This is their work.
The solution is not to convince them AI is safe. The solution is to give them a professional authoring tool that happens to be powered by the most sophisticated content engine in the VET sector — and let them discover that for themselves.
After three courses, Mavis will click Accept on the first draft and tell her colleague: "I don't know what the fuss was about. It's just a template system. I still write everything myself."
She will be correct. She did write everything herself. She reviewed every element, approved every section, and her professional judgement shaped every paragraph. The engine gave her a starting point. Mavis is the author.
2. The Metaphor Stack¶
The musical metaphor is not decoration. It is the product architecture, named correctly for the first time.
| Layer | Musical role | What it does |
|---|---|---|
| The Composer | Author | Creates the raw content — writes the music. Human or AI, or both in collaboration. The creative origin of every course. |
| The Triumvirate | Orchestration dept. | Arranges, structures, quality-checks. Applies TGA compliance framework. Returns a content bundle ready for rendering. |
| The Renderer | Performance | Publishes the output — PDF, SCORM, video script, workbook. Every performance of the same score can be different. |
| The Envelope | Programme notes | The provenance chain. Who wrote it, who arranged it, when it was performed, who was in the room. Cryptographically signed. |
| keys.ucca.online | The hallmark | The concert was real. The score is authentic. Here is the proof. Scan to verify. |
| Dr Sheffield | Head of Orchestration | Optional guidance layer. Walks past, leans over, says "lovely motif — but have you considered the key change in bar 4?" Never overwrites. Never takes the pen. |
3. The Three Archetypes¶
The Composer serves three fundamentally different users. Same instrument. Different players. Different repertoire.
3.1 — Mavis¶
The TAFE curriculum writer. 28 years in the sector. Remembers WordPerfect.
Mavis does not know she is using AI. She is using a professional authoring tool — The Composer — that knows the TGA the way her old WordPerfect templates knew a memo format. She selects a unit. The system shows her the elements and performance criteria. She writes her content into structured fields. The system has pre-populated a starting draft — she can use it, edit it, or delete it entirely.
Dr Sheffield is not present in Mavis's installation. He has not been introduced yet. That happens in year two, quietly, as a "content suggestions" feature her manager enables. By then Mavis has already published six courses and considers herself an expert user of the tool.
| What Mavis sees | What is actually happening |
|---|---|
| A professional course authoring tool | UCCA Composer — web interface, structured fields |
| TGA elements and performance criteria — pre-loaded | TGA adapter reading from the corpus |
| A starting draft she can edit or replace | Engine output — Triumvirate content bundle |
| Her course — she wrote it | Human-reviewed: true. Reviewer: mavis@tafe.edu.au. Engine: UCCA. |
| A PDF she can give to students | Signed envelope. QR code on final page. Fully verifiable. |
3.2 — The Enterprise RTO¶
200 students. Compliance pressure. Wants automation but needs audit trails.
The enterprise RTO uses The Composer differently. A compliance manager creates a course spec. The engine drafts. A subject matter expert reviews and approves each section — Dr Sheffield is on, full guidance mode, annotating every element. Legal signs off on the final envelope. The system assembles, signs, and delivers to their LMS.
The envelope for an enterprise job carries the full review chain — who drafted, who reviewed each section, who approved, when. The verification page shows it all. An ASQA auditor scans the QR code and sees a complete chain of custody. The enterprise RTO has never had this before. Their current process is a shared Word document on a network drive.
3.3 — The Defence Client¶
Air-gapped. No internet. Every section reviewed. Every approval logged.
The Composer runs locally. No Dr Sheffield — the guidance layer requires an outbound call. No cloud storage — the envelope writes to on-premise infrastructure via the storage adapter. The signing key is the client's own key, provisioned from keys.ucca.online at onboarding and stored air-gapped.
The human is not optional here — every section must be reviewed and approved by a named officer. The envelope carries the approval chain. The verification page is served from the client's own internal infrastructure using the same Worker code, the same public key, the same verification logic.
Same instrument. Air-gapped. The hallmark still holds.
4. Dr Sheffield¶
Dr Sheffield is the head of the orchestration department. He has been at the institution for thirty years. He knows the TGA better than anyone. He wanders past Mavis's desk, glances at her work, and says something quietly useful. He never picks up her pen. He never changes her words. He offers a thought and moves on.
"Lovely motif, Mavis — but that melody is going to be hard for strings. Have you considered piano? It would play better."
In product terms: Dr Sheffield is a contextual AI guidance layer that appears inline as the author writes. Not a chatbot. Not a panel. A quiet annotation — appearing at the edge of a content field when the system has a suggestion, disappearing when it doesn't.
What Dr Sheffield is not:
- Not a co-pilot — that word never appears in any UCCA product
- Not an autocomplete — he does not finish sentences
- Not a checker — he does not mark things wrong
- Not a replacement — he does not write the course
- Not always present — he is off by default, introduced as a feature upgrade
4.1 — What Dr Sheffield says¶
Dr Sheffield speaks in the first person, professionally, briefly. He addresses the author directly. He offers one thought and stops.
| Context | Dr Sheffield says |
|---|---|
| Performance criteria coverage gap | "This section covers elements 1 and 2 well — element 3 (monitoring performance) hasn't been addressed yet. Worth a paragraph before you move on." |
| Assessment condition not referenced | "The unit requires workplace-based assessment — you might want to mention that in the assessment section so it's explicit for auditors." |
| Language complexity high for target cohort | "This reads at about year 12 level — your learner profile shows Certificate III entry. A simpler sentence structure might land better." |
| Strong section — no note needed | [Dr Sheffield does not appear. Silence is approval.] |
4.2 — Pricing¶
Dr Sheffield is a premium add-on. He is not included in the base Composer licence. He is introduced to Mavis's institution in year two as an optional feature — "enhanced content guidance" — at an additional per-seat or per-course cost.
For enterprise and defence clients, Dr Sheffield is a line item in the deployment contract. His guidance model can be tuned to the client's specific compliance framework, house style, and learner profiles. That is a professional services engagement on top of the platform fee.
The word that never appears: Dr Sheffield is never described as AI, artificial intelligence, a co-pilot, an assistant, or a bot — in any product copy, any interface, any documentation, any sales material. He is the head of the orchestration department. He has opinions about your work. That is all.
5. Architectural Fit¶
The Composer is not a new engine. It is a new interface mode built on the architecture that already exists.
| Component | How The Composer uses it |
|---|---|
| World config | Composer is a new world interface — rtopacks/composer — sitting on the same RTOpacks world config |
| SubprocessorClient | Engine generates the first draft. Composer presents it section by section for human review. |
| Storage adapter | Draft state saved per section as the author works. Final approved content written to client R2. |
| Job envelope | Envelope gains new fields: human_reviewed, reviewer_id, review_completed_at, sections_accepted, sections_edited, sections_replaced. Signed on final approval. |
| keys.ucca.online | Verification page shows human review chain alongside engine provenance. Mavis's approval is in the provenance chain. |
| Dr Sheffield | Separate service. Calls SubprocessorClient with a guidance-specific system prompt. Returns inline annotations, not content. Premium add-on, own pricing tier. |
5.1 — New envelope fields for human review¶
| Field | Value |
|---|---|
human_reviewed |
true / false |
reviewer_id |
mavis@tafe.edu.au — the named human author |
review_completed_at |
ISO8601 UTC timestamp of final approval |
sections_accepted |
Count of sections approved without edit |
sections_edited |
Count of sections modified by the human |
sections_replaced |
Count of sections where human wrote from scratch |
dr_sheffield_enabled |
true / false — whether guidance layer was active |
6. The Deployment Spectrum¶
The Composer deploys across a spectrum from fully connected to fully air-gapped. The same product. The same envelope. Different configurations.
| TAFE / Small RTO | Enterprise RTO | Government / TAFE Large | Defence / Air-gapped | |
|---|---|---|---|---|
| Engine | Cloud — UCCA hosted | Cloud — UCCA hosted | Private cloud / on-prem option | On-premise — no outbound |
| Dr Sheffield | Optional add-on | Included — full guidance | Configurable | Not available |
| Storage | UCCA R2 (default) | Client R2 or S3 | Client infrastructure | On-premise only |
| Signing | keys.ucca.online | keys.ucca.online | keys.ucca.online or escrow | Client key server — UCCA public key provisioned at onboarding |
| Human review | Optional | Required per policy | Required | Mandatory — named officer |
| Pricing model | Per course | Per seat / per course | Enterprise licence | Deployment contract + support |
7. The Product Promise¶
Professional course authoring tools for VET practitioners. No subscriptions to Silicon Valley. No data sent overseas. Your content, your copyright, your course.
Every line of that promise is architecturally true and verifiable. The envelope proves it. The QR code on the final page proves it. The provenance chain on the verification page shows exactly what touched this document, when, and under what governance.
Mavis authored this course. The engine gave her a starting point. Dr Sheffield offered a thought. The Triumvirate arranged it. The renderer published it. The hallmark proves it happened. The keys server is always on. Scan the last page.
| For Mavis | For the procurement officer |
|---|---|
| "It's like WordPerfect — but it knows the TGA." | "Cryptographically signed. Human reviewed. Chain of custody on every document. Scan the last page." |
The Composer The engine is eternal and benevolent. Mavis wrote this.
Version History¶
| Version | Date | Change | Author |
|---|---|---|---|
| 1.0 | 2026-03-11 | Converted from UCCA-The-Composer-Product-Architecture.docx | Claude Code |