ARDS-SPEC-001 · First Edition

ARDS v1.0 Specification

The normative reference for the AxiomOrdo Regulatory Data Standard. This document defines all artefact types, required metadata, conformance levels, and extension rules.

Status: PUBLISHED Version: 1.0.0 Published: May 2026 Licence: AOSL-1.0
Contents

1. Scope & Purpose

This document constitutes the normative specification of the AxiomOrdo Regulatory Data Standard (ARDS), Version 1.0.0. It is identified by the document reference ARDS-SPEC-001.

ARDS defines the schema language, metadata model, artefact taxonomy, conformance framework, and extension rules for machine-readable regulatory compliance artefacts. It is designed to enable interoperability between compliance software systems, regulatory authorities, auditors, and data intermediaries operating across multiple regulatory regimes.

Normative Language: The key words SHALL, SHALL NOT, SHOULD, SHOULD NOT, MAY, and MAY NOT in this document are to be interpreted as described in RFC 2119. All requirements using SHALL are mandatory for the relevant conformance level.

2. Normative References

ReferenceTitleRelevance
RFC 4122A Universally Unique IDentifier (UUID) URN NamespaceartefactId format
ISO 8601Date and time formatAll date/datetime fields
RFC 2119Key words for use in RFCs to Indicate Requirement LevelsNormative language
JSON Schema Draft-07JSON Schema: A Media Type for Describing JSON DocumentsAll ARDS schemas
SemVer 2.0.0Semantic Versioning SpecificationardsVersion, schemaVersion
AOSL-1.0AxiomOrdo Open Standard LicenceLicence for this specification

3. Terms & Definitions

TermDefinition
ArtefactA discrete, structured data object conforming to an ARDS schema, representing a defined unit of compliance information.
Artefact TypeOne of the six normative categories: ROR, EA, CV, TB, UCA, AP (see §4).
ards:metaThe required top-level metadata envelope present in every ARDS artefact.
Conformance LevelOne of six progressive tiers defining the depth of ARDS compliance for an artefact or tool (see §7).
Domain PackA published set of ARDS extension schemas for a specific regulatory domain (e.g., FuelEU, CBAM).
ProducerA system or organisation that creates ARDS artefacts.
ConsumerA system or organisation that ingests and processes ARDS artefacts.
Schema URIThe canonical identifier for an ARDS schema, following the pattern https://schema.axiomordo.com/ards/{version}/{family}/{name}.schema.json.
Certification TokenA machine-readable, cryptographically signed JSON document issued by AxiomOrdo attesting conformance at a specific level.
Regulatory ContextThe metadata block identifying the regulation, regulatory body, jurisdiction, and applicable period for an artefact.
Provenance ChainThe linked sequence of artefacts from obligation through evidence to verdict, maintained in a Trace Bundle.

4. Artefact Model

ARDS defines six normative artefact types. Each type has a canonical schema, a defined role in the compliance lifecycle, and specific field requirements beyond the common ards:meta envelope.

CodeFull NamePrimary RoleKey Relationships
RORRegulatory Obligation RecordDefines a specific regulatory obligation for an entity/periodReferenced by EA, CV
EAEvidence ArtefactCarries structured evidence supporting a compliance claimReferences ROR; referenced by TB, CV
CVCompliance VerdictRecords the compliance outcome for an obligationReferences ROR, EA; referenced by UCA, AP
TBTrace BundleMachine-readable provenance graphReferences ROR, EA, CV; referenced by AP
UCAUnified Compliance ArtefactPortable submission-ready compositeEmbeds ROR, EA, CV
APAudit PackageSealed, signed archive for regulatorsEmbeds all types; carries digital signature

5. The ards:meta Envelope

Every ARDS artefact SHALL contain a top-level key "ards:meta" whose value is an object containing the fields defined in this section. The presence of this envelope is mandatory for L2 Core Conformance and above.

FieldTypeRequiredDescription
ardsVersionstring (SemVer)SHALLARDS version this artefact conforms to, e.g., "1.0.0"
schemaIdURI stringSHALLCanonical URI of the ARDS schema for this artefact
schemaVersionstring (SemVer)SHALLVersion of the declared schema
artefactTypestring (enum)SHALLOne of: RegulatoryObligationRecord, EvidenceArtefact, ComplianceVerdict, TraceBundle, UnifiedComplianceArtefact, AuditPackage
artefactIdURN (UUID v4)SHALLGlobally unique artefact identifier. Format: urn:uuid:{uuid-v4}
producedAtstring (ISO 8601)SHALLTimestamp of artefact creation
producerIdentityobjectSHALLIdentifies the producing system and organisation
regulatoryContextobjectSHALLIdentifies the regulation, regulatory body, jurisdiction, and period
certificationIdstringSHOULDAxiomOrdo certification token ID if the producer is certified
previousVersionURNMAYartefactId of the artefact this supersedes

6. Core Schema Set

All canonical ARDS schemas are published at https://schema.axiomordo.com/ards/. The URI pattern is:

https://schema.axiomordo.com/ards/{ardsVersion}/{family}/{schema-name}.schema.json

The following schema families are defined in ARDS v1.0:

FamilyArtefact TypeDomainStatus
obligation-recordRORCoreGA
evidence-artefactEACoreGA
compliance-verdictCVCoreGA
trace-bundleTBCoreGA
unified-compliance-artefactUCACoreGA
audit-packageAPCoreGA
fueleu/*ROR, EA, CV, APFuelEU MaritimeGA
cbam/*ROR, EA, CV, APEU CBAMGA
metaAllCoreGA

7. Conformance

ARDS defines six conformance levels. Each level subsumes all levels below it. Self-declaration is sufficient for L1–L2; AxiomOrdo certification is required for L3–L6.

LevelCodeNameKey Normative Requirements
L1 ARDS-SV Schema-Valid The artefact SHALL validate against the JSON Schema identified by ards:meta.schemaId without errors.
L2 ARDS-CC Core Conformant The artefact SHALL include all required ards:meta fields. All field values SHALL meet the format and enumeration requirements of this specification.
L3 ARDS-EC Extended Conformant The artefact SHALL implement provenance links (Trace Bundle), domain-specific extensions, and all SHOULD requirements of this specification.
L4 ARDS-CG Certified Generator A tool that produces ARDS artefacts at L3, passes the AxiomOrdo conformance test suite, and holds a valid Certification Token.
L5 ARDS-CS Certified Consumer A tool that ingests ARDS artefacts from any certified generator, validates provenance, and correctly processes all normative artefact types.
L6 ARDS-CP Certified Platform An end-to-end platform that both generates and consumes ARDS artefacts, maintains a live registry, and satisfies all L4 and L5 requirements.

8. Extension Model

ARDS provides a structured extension mechanism. Extensions SHALL follow these rules:

  • All extension fields SHALL be namespaced using a registered prefix, e.g., fueleu:vesselIMO, cbam:installationId.
  • Extension namespaces SHALL be registered in the ARDS Extension Registry at registry.axiomordo.com.
  • Extension schemas SHALL be published at a resolvable URI following the canonical pattern.
  • Unofficial extensions MAY use any prefix that does not conflict with registered namespaces and SHALL use the x- convention, e.g., x-vendor:customField.
  • An artefact that uses registered domain-pack extensions SHOULD declare the domain pack version in ards:meta.domainPacks.
Domain packs (FuelEU, CBAM, PFAS, ETS) are maintained by AxiomOrdo domain working groups and published under AOSL-1.0. Any party may propose a new domain pack via the RFC process.

9. Versioning

ARDS follows Semantic Versioning (SemVer 2.0.0):

  • Patch releases (e.g., 1.0.1): clarifications, editorial corrections. No schema changes.
  • Minor releases (e.g., 1.1.0): new optional fields, new domain packs, new artefact types. Backward-compatible.
  • Major releases (e.g., 2.0.0): breaking changes to required fields or the artefact model. At least 24-month deprecation notice required.

All published versions of the specification and schemas are permanently archived at schema.axiomordo.com/ards/{version}/.

10. Governance

ARDS is maintained by the AxiomOrdo Standards Board, supported by:

  • Technical Advisory Group (TAG) — reviews RFCs and schema proposals
  • Domain Working Groups — one per domain pack; open membership
  • Certification Committee — oversees certification programmes
  • User Council — industry representatives with advisory votes

Changes to this specification require an accepted RFC. See the RFC Process for details.

Annexes

Annex A — Normative Schema URIs

Complete list of all canonical schema URIs defined in ARDS v1.0, including core and domain-pack schemas.

Annex B — Field Semantics by Artefact Type

Detailed field-level requirements, cardinalities, and allowed values for each of the six artefact types.

Annex C — Conformance Test Matrix

The normative test cases used in AxiomOrdo certification assessments, mapped to specification requirements.

Annex D — AOSL-1.0 Licence Text

Full text of the AxiomOrdo Open Standard Licence under which this specification is published.

Changelog

VersionDateChange
1.0.0May 2026First published edition. Defines six artefact types, six conformance levels, FuelEU and CBAM domain packs, and ards-validate CLI reference implementation.