Aurigent

AUR / RESEARCH / SCHEMA

SCHEMA v3.2 · SUPERSEDES v3.1

01 / STATEMENT

Aurigent Research · Schema v3.2 · Supersedes v3.1

Schema Reference

This reference defines the structural schema under which Aurigent Research records are issued. Records adhere to this schema across all issuances within the effective term.

02 / RECORD CONTROL

Record Control

RECORD CONTROL · FIELD REGISTRY

12 FIELDS

IDENTITY4

TYPE:
Record class, as declared by the record
SpecimenINTELLIGENCE
RECORD_ID:
PREFIX-YYYY-MM-DD-Vn
SpecimenAR-2026-04-01-V1
PRECEDING_RECORD:
Chained reference to prior record; — where the record opens a series
SpecimenAR-2026-03-25-V1
RECORD_SIGNATURE:
UUID, generated at issuance (RFC 4122)
Specimen5C34E54E-1678-4CE8-870C-B8E681EDDF4F

ISSUANCE3

VERSION:
MAJOR.MINOR; MINOR RESERVED FOR CORRECTIONS
Specimen1.0
STATUS:
DRAFT | FINALIZED | SUPERSEDED
SpecimenFINALIZED
ISSUED:
ISO-8601 DATE
Specimen2026-04-01

GOVERNANCE3

RECORD_MODE:
APPEND-ONLY AFTER FINALIZATION
SpecimenAPPEND-ONLY
RETENTION_PERIOD:
PERMANENT
SpecimenPERMANENT
SCHEMA_VERSION:
REFERENCE TO GOVERNING SCHEMA
Specimen3.2

ACCESS1

ACCESS_CLASSIFICATION:
EXECUTIVE | RESTRICTED | INTERNAL
SpecimenEXECUTIVE

COMPOSITION1

ENTRY_COUNT:
Count of entries contained in the record
Specimen5

03 / REGISTERS

Registers

Every record opens with RECORD_CONTROL and carries its entries in RECORD_ENTRIES. Further registers may precede or follow. Their structure, keys and values are not fixed by this schema, and are extracted as encountered.

Register
Purpose
Body
Presence
RECORD_CONTROL
Identity, issuance, governance and access of the record.
ROWS
REQUIRED
[REGISTER_NAME]
Zero or more, named per record. E.g. EVALUATION_STATUS, ARCHITECTURAL_SCHEMA.
PROSE | ROWS
OPTIONAL
RECORD_ENTRIES
The record's entries.
ENTRIES
REQUIRED

RECORD STRUCTURE · REGISTERS NAMED PER RECORD

04 / ENTRY

Entry

Records are composed of one or more entries. Each entry is bound to its parent record by RECORD ID and carries its own canonical metadata.

Anchor
Description
Presence
Specimen
ENTRY_ID:
PREFIX-YYYY-MM-DD-Vn-Em
REQUIRED
AR-2026-04-01-V1-E1
INGESTION_ID:
UUID, external traceability (RFC 4122)
REQUIRED
4129919E-2AB4-43BF-AFBB-4FE1C6A80956
ENTITY:
Primary entity or entities
OPTIONAL
GENERAL MOTORS
SUBJECT:
Entry subject line
REQUIRED
PUBLIC-ROAD SAFETY VALIDATION INITIATION
SUBJECT_CLASS:
Single-word entry classification
OPTIONAL
VALIDATION
DOMAIN:
Domain taxonomy
OPTIONAL
VALIDATION SYSTEMS
GEOGRAPHY:
ISO regions or jurisdictions
OPTIONAL
UNITED STATES
[ANCHOR]:
Zero or more, named per subject. E.g. REFERENCE_PLATFORM, SCHEMA.
OPTIONAL
—
FUNCTIONAL_DOMAIN:
Canonical executive function or functions to which the entry is assigned
REQUIRED
SIMULATION, VERIFICATION AND VALIDATION

9 ANCHORS · 4 REQUIRED · 5 OPTIONAL · SPECIMEN AR-2026-04-01-V1-E1

05 / ENTRY BODY

Entry Body

Each entry body comprises three structured sections. Section labels are rendered as standalone headers with trailing punctuation.

ENTRY BODY · SECTION REGISTRY

3 SECTIONS
DEFINITION:
What occurred or was established
Specimen · AR-2026-04-01-V1-E1General Motors initiated supervised autonomous vehicle testing on public roads in selected U.S. states and formalized the safety case governing those operations.
STRUCTURE:
How it is composed or operates
Specimen · AR-2026-04-01-V1-E1Manually driven fleet data, simulation, closed-course testing, and on-road observation generate traceable evidence for machine-learned driving behavior, with separation between test and product safety cases.
EFFECT:
Implications for executive decisions
Specimen · AR-2026-04-01-V1-E1Establishes a phased assurance model for autonomy validation, guiding structured progression from testing to series-vehicle deployment within regulatory and program constraints.

06 / TAXONOMIES

Taxonomies

TAXONOMIES

3 TAXONOMIES
SUBJECT CLASSOPEN · ASSIGNED PER ENTRY

ANY SINGLE WORD

A single-word classification assigned per entry. Not bound to a fixed enumeration.

SpecimenVALIDATION E1 · E2INTEGRATION E3 · E5DEPLOYMENT E4

FUNCTIONAL DOMAINCONTROLLED · 5 VALUES · ASSIGNED PER ENTRY

AUTONOMY AND PERCEPTION ENGINEERING

Perception stack, sensor fusion, autonomy architecture

SpecimenE3 · E4

SIMULATION, VERIFICATION AND VALIDATION

Simulation, scenario testing, verification, safety case

SpecimenE1 · E2 · E5

VEHICLE PLATFORM AND SYSTEMS INTEGRATION

Vehicle integration, sensor hardware, E/E architecture, zonal systems

SpecimenE2 · E5

SOFTWARE INFRASTRUCTURE AND DATA OPERATIONS

Middleware, operating layers, data pipelines, ML data operations

SpecimenE3

EXECUTIVE PRODUCT AND STRATEGY

Platform roadmap, product direction, sourcing timing, architecture transition

SpecimenE4

ACCESS CLASSIFICATIONCONTROLLED · 3 LEVELS · ASSIGNED PER RECORD

EXECUTIVE

Distributed to authorized recipients

Specimen● RECORD

RESTRICTED

Executive review only; not distributed

Specimen—

INTERNAL

Aurigent systems only

Specimen—

07 / IDENTIFIERS

Identifiers

IDENTIFIER · ANATOMY

SPECIMEN AR-2026-04-01-V1-E1
RECORD IDPREFIX-YYYY-MM-DD-VnSpecimenAR-2026-04-01-V1
ARPREFIX
2026-04-01DATE
V1VERSION
ENTRY IDPREFIX-YYYY-MM-DD-Vn-EmSpecimenAR-2026-04-01-V1-E1
ARPREFIX
2026-04-01DATE
V1VERSION
E1ENTRY

Component formats

PREFIX

Record-scoped code, as declared (e.g. AR). All segments preceding the date.

DATE

YYYY-MM-DD (ISO-8601)

VERSION

Vn = major version number

ENTRY

Em = entry index within record (E1, E2, ...)

Record signature · UUID · RFC 4122 · 8-4-4-4-12

5C34E54E8 HEX
16784 HEX
4CE84 HEX
870C4 HEX
B8E681EDDF4F12 HEX
Used forRECORD SIGNATURE, INGESTION ID

08 / RECORD STATES

Record States

RECORD STATE · LIFECYCLE

DRAFT → FINALIZED → SUPERSEDED
DRAFTISSUANCE → FINALIZED
DISTRIBUTEDNOT DISTRIBUTED
RETAINEDWITHOUT RETENTION
REVISABLEMAY BE REVISED OR DISCARDED
DEFINITIONComposition state. Not distributed. May be discarded or revised without retention.
FINALIZEDREVISED REVIEW → SUPERSEDED
DISTRIBUTEDUNDER ACCESS CLASSIFICATION
RETAINEDAPPEND-ONLY
REVISABLECORRECTIONS ISSUED AS NEW VERSIONS
DEFINITIONIssued state. Distributed under access classification. Subject to append-only retention. May not be deleted or revised; corrections issued as new versions.
SUPERSEDED
DISTRIBUTEDEXCLUDED FROM ACTIVE REFERENCE SETS
RETAINEDINDEFINITELY
REVISABLE
DEFINITIONSuperseded by a subsequent issuance under revised review. Retained indefinitely; excluded from active reference sets.

09 / VERSIONING

Versioning

Schema versions are issued under formal control. Each version supersedes prior versions. Records issued under prior schema versions remain valid under their effective schema.

SCHEMA · VERSIONS

v2.x → v3.0 → v3.1 → v3.2
v2.x→ v3.0
STATUSARCHIVED
EFFECTHISTORICAL REFERENCE ONLY
v3.0→ v3.1
STATUSSUPERSEDED
EFFECTLEGACY REFERENCE ONLY
v3.1→ v3.2
STATUSSUPERSEDED
EFFECTNO NEW ISSUANCES
v3.2
STATUSACTIVE
EFFECTGOVERNING SCHEMA

Cross-References

3 REFERENCES

Aurigent Research Schema · v3.2 · Supersedes v3.1