Skip to content

SOP-ID Schema

Document SOP-ID Schema
Version 1.0
Effective 19 March 2026
Last reviewed 24 March 2026
Owner compliance@rtopacks.com.au
Status In development

Every resource produced by the RTOpacks platform is assigned a SOP-ID — a permanent, structured identifier that records the provenance of that resource at the moment it was produced. The SOP-ID is the primary mechanism for independent verification.

What a SOP-ID records

A SOP-ID captures the following at the moment of export:

Field Description
sop_id Unique identifier for this resource instance. Format: RTP-{qual_code}-{unit_code}-{timestamp}-{hash}
qual_code The qualification code from the National Register (e.g. SIT30222)
unit_code The unit of competency code (e.g. SITTTVL001)
unit_title Official unit title at time of export — locked from National Register
unit_release Release version of the unit from training.gov.au
nr_sync_date Date of the most recent National Register sync used for this resource
content_type Resource type (assessment tool, learning guide, observation checklist, etc.)
m_a_ratio Ratio of Manual (human-edited) to Agentic (AI-drafted) content blocks at export
produced_at UTC timestamp of resource export
produced_by RTO identifier (anonymised in public records)
processing_domicile Cloudflare region where processing occurred — always AU-SYD or AU-MEL
schema_version Version of this SOP-ID schema applied

Format

SOP-IDs are issued as signed JSON records and embedded in the exported resource as metadata. They are also recorded in the RTOpacks provenance ledger.

{
  "sop_id": "RTP-SIT30222-SITTTVL001-20260319T142200Z-a3f9c2",
  "qual_code": "SIT30222",
  "unit_code": "SITTTVL001",
  "unit_title": "Access and interpret product information",
  "unit_release": "1",
  "nr_sync_date": "2026-03-18",
  "content_type": "assessment_tool",
  "m_a_ratio": "0.72",
  "produced_at": "2026-03-19T14:22:00Z",
  "produced_by": "RTO-XXXXX",
  "processing_domicile": "AU-SYD",
  "schema_version": "1.0"
}

Verification

Any RTO, auditor, or third party can verify a SOP-ID by:

  1. Noting the sop_id value from the resource metadata or header
  2. Visiting https://rtopacks.com.au/verify/{sop_id} — the provenance record is publicly accessible without login
  3. Confirming the unit_code and unit_title against training.gov.au
  4. Confirming the nr_sync_date is within the 7-day maximum sync window (Engine Rule 1)

Relationship to Engine Rules

The SOP-ID schema enforces Engine Rule 5 (M Promotion Rule) at the record level. The m_a_ratio field reflects the proportion of content blocks that have been promoted from Agentic (A) to Manual (M) status through human substantial edit or manual verify. A resource with m_a_ratio: 1.0 has been fully human-verified. A resource with m_a_ratio: 0.0 has received no human editing beyond the initial generation — RTOpacks does not permit export of resources at this ratio.

In development

The SOP-ID ledger and /verify/ endpoint are in active development. The schema above represents the v1.0 specification. The first public ledger entries will be created when the first RTOpack resource is exported to a customer.

High contrast