RTOpacks Mode System

Licensed Implementation of UMS-001

Version 1.0 — 3 April 2026

United Central Colleges of Australia Pty Ltd (ABN 59 168 872 535)

Operating as RTOpacks (rtopacks.com.au)

---

Status

Active. This document governs the implementation of the UCCA Mode System within the RTOpacks platform. It is a licensed fork of the UCCA Mode System Standard (UMS-001 v1.0), published by UCCA Inc (EIN 84-4522608).

This document must be read in conjunction with UMS-001 v1.0. Where this document is silent, UMS-001 governs. Where this document extends or narrows UMS-001, this document governs for the RTOpacks platform.

Master standard: UMS-001 v1.0 — UCCA Mode System Standard (UCCA Inc, 3 April 2026)

---

1. Scope

This document covers the RTOpacks admin panel (admin.rtopacks.com.au) and any future RTOpacks operational surfaces. It does not cover the RTOpacks public site (rtopacks.com.au) — mode system features are admin-surface only.

---

2. Context — The RTOpacks Platform

RTOpacks is a VET (Vocational Education and Training) sector intelligence platform serving Registered Training Organisations (RTOs) operating under the Australian Skills Quality Authority (ASQA) and the Standards for Registered Training Organisations (RTOs) 2015.

The RTOpacks admin panel is used by: - RTOpacks internal staff — platform operators managing client relationships, data integrity, and platform configuration - Future client administrators — RTO staff accessing their own organisation data (planned)

The three mode audiences in the RTOpacks context are:

Mode	Primary audience in RTOpacks context
LIVE	Experienced RTOpacks staff operating the platform daily
GUIDED	New RTOpacks staff onboarding, or staff encountering an unfamiliar section
COMPLIANCE	Internal governance review, external audit, or ATO/ASQA scrutiny of platform operations

---

3. Extensions to UMS-001

3.1 Compliance Framework References

RTOpacks COMPLIANCE mode annotations reference the following frameworks, in addition to internal policy documents:

Reference prefix	Framework
ASQA-	Standards for RTOs 2015 (ASQA)
NVR-	National Vocational Education and Training Regulator Act 2011
PA-	Privacy Act 1988 (Cth) and Australian Privacy Principles
AML-	Anti-Money Laundering and Counter-Terrorism Financing Act 2006
UCCA-	UCCA internal policy documents
RTO-	RTOpacks platform policy documents

3.2 Annotation Language — VET Terminology

GUIDED mode annotations on the RTOpacks platform use VET sector terminology without explanation where the audience is assumed to be VET-literate (e.g. "AVETMISS", "USI", "RTO code", "training package"). Annotations do not over-explain terminology that any RTO operator would know.

Where a term may be unfamiliar to a new platform user (as opposed to a new VET operator), the annotation explains the platform-specific meaning.

3.3 Signal Confidence Labels

The RTOpacks Radar feature uses three confidence labels for data signals. In GUIDED mode, these labels are explained in context. The display labels and their meanings are:

Display label	Internal value	Meaning
Official	authoritative	Data sourced directly from an Australian government register (ABR, ASQA, TGA). This is a verified fact.
Detected	observed	Data detected directly by the RTOpacks sweep — observed from the RTO's own systems, website, or DNS.
Derived	inferred	Data calculated or classified from other signals. No single source stated this — RTOpacks worked it out.

GUIDED mode annotations on Radar signal elements explain this distinction in plain English. COMPLIANCE mode annotations on Radar signal elements reference the Privacy Act (PA-APP3) for data collection provenance.

3.4 User Role Access

RTOpacks implements the following mode access rules (extending UMS-001 §5.4):

Role	LIVE	GUIDED	COMPLIANCE
Admin (internal staff)	✓	✓	✓
Standard user	✓	✓	—
Read-only	✓	✓	—

Auditor role (COMPLIANCE default) is planned for a future release when external client access is enabled.

---

4. Annotation File Structure — RTOpacks

Annotation files are stored in the RTOpacks docs repository at:

docs/annotations/
  organisations.en.json       ← Organisation detail pages
  radar.en.json               ← Radar tab
  dashboard.en.json           ← Admin dashboard
  corpus.en.json              ← Corpus section
  regulatory.en.json          ← Regulatory feed
  calendar.en.json            ← VET calendar
  settings.en.json            ← Settings pages

Element identifiers use the prefix rtopacks.admin.:

rtopacks.admin.radar.trigger_crawl
rtopacks.admin.radar.signal_confidence_authoritative
rtopacks.admin.radar.signal_confidence_observed
rtopacks.admin.radar.signal_confidence_inferred
rtopacks.admin.organisations.abn_status
rtopacks.admin.organisations.registration_end
rtopacks.admin.dashboard.rto_count

---

5. Seed Annotations — Radar Tab

The following seed annotations are provided as the initial content for radar.en.json. All entries are _draft: true pending human review.

{
  "rtopacks.admin.radar.last_crawled": {
    "guided": {
      "title": "Last Crawled",
      "body": "Shows when RTOpacks last ran a technical sweep of this RTO's web presence. The sweep collects DNS records, SSL certificate details, hosting information, and technology stack signals. 'Never' means this RTO has not yet been swept.",
      "_draft": true
    },
    "compliance": {
      "ref": "RTO-RADAR-001",
      "title": "Data Collection Timestamp",
      "clause": "RTOpacks Data Handling Policy §4.1",
      "summary": "Collection timestamp is recorded for all externally sourced data in accordance with data provenance requirements.",
      "framework": "RTOpacks Platform Policy v1.0",
      "_draft": true
    }
  },
  "rtopacks.admin.radar.trigger_crawl": {
    "guided": {
      "title": "Trigger Crawl",
      "body": "Queues a fresh technical sweep for this RTO. The sweep runs on the RTOpacks Mac Mini and takes approximately 2-5 minutes. Once queued, the button is disabled until the sweep completes. Use this when you need up-to-date intelligence on an RTO outside the regular sweep cycle.",
      "_draft": true
    },
    "compliance": {
      "ref": "PA-APP3",
      "title": "Lawful Collection of Publicly Available Data",
      "clause": "Privacy Act 1988 (Cth) — Australian Privacy Principle 3",
      "summary": "Data collected by the sweep is publicly available information. Collection is lawful under APP3.4 which permits collection of publicly available personal information.",
      "framework": "Privacy Act 1988 (Cth)",
      "_draft": true
    }
  },
  "rtopacks.admin.radar.signal_confidence_authoritative": {
    "guided": {
      "title": "Official — Government Source",
      "body": "This signal came directly from an Australian government register — the Australian Business Register (ABR), ASQA's national register, or the TGA (Training.gov.au). It is a verified fact, not an estimate.",
      "_draft": true
    },
    "compliance": {
      "ref": "PA-APP3",
      "title": "Primary Source Data",
      "clause": "Privacy Act 1988 (Cth) — Australian Privacy Principle 3",
      "summary": "Data sourced from government registers is collected from authoritative primary sources under their respective public disclosure frameworks.",
      "framework": "Privacy Act 1988 (Cth)",
      "_draft": true
    }
  },
  "rtopacks.admin.radar.signal_confidence_observed": {
    "guided": {
      "title": "Detected — Live Scan",
      "body": "RTOpacks detected this signal directly by scanning the RTO's public web presence — their website, DNS records, SSL certificate, or server headers. This is what we observed at the time of the last crawl.",
      "_draft": true
    },
    "compliance": {
      "ref": "PA-APP3",
      "title": "Publicly Available Data Collection",
      "clause": "Privacy Act 1988 (Cth) — Australian Privacy Principle 3",
      "summary": "Observed signals are collected from publicly accessible systems. Collection is lawful under APP3.4.",
      "framework": "Privacy Act 1988 (Cth)",
      "_draft": true
    }
  },
  "rtopacks.admin.radar.signal_confidence_inferred": {
    "guided": {
      "title": "Derived — Calculated Signal",
      "body": "RTOpacks calculated this value from other signals — no single source stated it directly. For example, entity type may be derived by combining ABN entity codes with domain name patterns. Derived signals are RTOpacks' own analysis, not a fact from an external source.",
      "_draft": true
    },
    "compliance": {
      "ref": "PA-APP4",
      "title": "Derived Data Quality",
      "clause": "Privacy Act 1988 (Cth) — Australian Privacy Principle 4",
      "summary": "Derived signals are clearly identified as calculated values to maintain data quality and accuracy transparency.",
      "framework": "Privacy Act 1988 (Cth)",
      "_draft": true
    }
  },
  "rtopacks.admin.radar.hosting_tier": {
    "guided": {
      "title": "Hosting Tier",
      "body": "RTOpacks classifies the RTO's web hosting into four tiers based on the detected hosting provider and infrastructure. Enterprise = major cloud (AWS, Azure, Cloudflare). Professional = managed hosting. Budget = shared/cheap hosting. ISP = residential or ISP-assigned infrastructure. This is a useful proxy for the RTO's digital maturity and IT investment level.",
      "_draft": true
    },
    "compliance": {
      "ref": "RTO-RADAR-002",
      "title": "Derived Classification Signal",
      "clause": "RTOpacks Data Handling Policy §4.3",
      "summary": "Hosting tier is a derived classification signal based on publicly observable infrastructure data.",
      "framework": "RTOpacks Platform Policy v1.0",
      "_draft": true
    }
  },
  "rtopacks.admin.radar.email_maturity": {
    "guided": {
      "title": "Email Maturity",
      "body": "Indicates how professionally configured the RTO's email infrastructure is, based on their MX records and email authentication setup (SPF, DKIM, DMARC). Mature = Google Workspace or Microsoft 365 with full authentication. Minimal = basic MX only. None = no email infrastructure detected.",
      "_draft": true
    },
    "compliance": {
      "ref": "RTO-RADAR-002",
      "title": "Derived Classification Signal",
      "clause": "RTOpacks Data Handling Policy §4.3",
      "summary": "Email maturity is a derived classification based on publicly observable DNS and email authentication records.",
      "framework": "RTOpacks Platform Policy v1.0",
      "_draft": true
    }
  },
  "rtopacks.admin.radar.ssl_health": {
    "guided": {
      "title": "SSL Health",
      "body": "Shows the status of the RTO's SSL certificate — the security certificate that enables HTTPS on their website. Good = valid and not expiring soon. Expiring soon = action needed within 7-14 days. Critical = expired or self-signed, meaning their site may show security warnings to visitors.",
      "_draft": true
    },
    "compliance": {
      "ref": "RTO-RADAR-002",
      "title": "Publicly Observable Security Signal",
      "clause": "RTOpacks Data Handling Policy §4.3",
      "summary": "SSL health is derived from the publicly observable SSL certificate presented by the RTO's web server.",
      "framework": "RTOpacks Platform Policy v1.0",
      "_draft": true
    }
  }
}

---

6. Implementation Brief Reference

The technical implementation of the RTOpacks Mode System is governed by brief ADMIN-MODE-01 (to be written). That brief covers:

• Mode state management (localStorage, active tab visual state)
• DOM element tagging (data-annotation-id attributes across all admin surfaces)
• Renderer build (GUIDED blue badges, COMPLIANCE amber badges, Export function)
• Annotation file loading and locale fallback
• User dismissal persistence
• Coverage calculation and display

---

7. Deviations from UMS-001

Section	Deviation	Reason
UMS-001 §5.4	COMPLIANCE mode restricted to Admin role only	RTOpacks does not yet have an external auditor access model. Will align with UMS-001 when external client access is enabled.
UMS-001 §3.1	Annotation files stored in docs repository, served via docs-proxy	RTOpacks infrastructure pattern — consistent with existing docs serving architecture.

---

8. Version History

Version	Date	Author	Notes
1.0	3 April 2026	UCCA Inc (on behalf of RTOpacks)	Initial fork from UMS-001 v1.0. Radar tab seed annotations included.

---

9. Document Information

Field	Value
Document ID	RTO-UMS-001
Title	RTOpacks Mode System
Master Standard	UMS-001 v1.0 (UCCA Inc)
Version	1.0
Status	Active
Owner	United Central Colleges of Australia Pty Ltd (ABN 59 168 872 535)
Repository	rtopacks/docs/docs/standards/mode-system.md
Licence	Proprietary — Licensed from UCCA Inc under UCCA Licensing Agreement

---

This document is a licensed fork of the UCCA Mode System Standard (UMS-001). It is maintained by United Central Colleges of Australia Pty Ltd operating as RTOpacks. Master standard enquiries: tim@ucca.online