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

TYPE:
INTELLIGENCE RECORD
RECORD_ID:
AR-YYYY-MM-DD-Vn
PRECEDING_RECORD:
Chained reference to prior record
RECORD_SIGNATURE:
UUID, generated at issuance (RFC 4122)
VERSION:
MAJOR.MINOR; MINOR RESERVED FOR CORRECTIONS
STATUS:
DRAFT | FINALIZED | SUPERSEDED
ISSUED:
ISO-8601 DATE
RECORD_MODE:
APPEND-ONLY AFTER FINALIZATION
RETENTION_PERIOD:
PERMANENT
SCHEMA_VERSION:
REFERENCE TO GOVERNING SCHEMA
ACCESS_CLASSIFICATION:
EXECUTIVE | RESTRICTED | INTERNAL
ENTRY_COUNT:
Count of entries contained in the record

03 / 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.

ENTRY · FIELD REGISTRY

ENTRY_ID:
AR-YYYY-MM-DD-Vn-Em
INGESTION_ID:
UUID, external traceability (RFC 4122)
ENTITY:
Primary entity or entities
SUBJECT:
Entry subject line
SUBJECT_CLASS:
Single-word entry classification
DOMAIN:
Domain taxonomy
GEOGRAPHY:
ISO regions or jurisdictions
FUNCTIONAL_DOMAIN:
Canonical executive function or functions to which the entry is assigned

04 / 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

DEFINITION:
What occurred or was established
STRUCTURE:
How it is composed or operates
EFFECT:
Implications for executive decisions

05 / TAXONOMIES

Taxonomies

SUBJECT CLASS

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

FUNCTIONAL DOMAIN · CONTROLLED VOCABULARY

AUTONOMY AND PERCEPTION ENGINEERING
Perception stack, sensor fusion, autonomy architecture
SIMULATION, VERIFICATION AND VALIDATION
Simulation, scenario testing, verification, safety case
VEHICLE PLATFORM AND SYSTEMS INTEGRATION
Vehicle integration, sensor hardware, E/E architecture, zonal systems
SOFTWARE INFRASTRUCTURE AND DATA OPERATIONS
Middleware, operating layers, data pipelines, ML data operations
EXECUTIVE PRODUCT AND STRATEGY
Platform roadmap, product direction, sourcing timing, architecture transition

ACCESS CLASSIFICATION

EXECUTIVE
Distributed to authorized recipients
RESTRICTED
Executive review only; not distributed
INTERNAL
Aurigent systems only

06 / IDENTIFIERS

Identifiers

IDENTIFIER · FORMAT REGISTRY

RECORD ID FORMAT
AR-YYYY-MM-DD-Vn
PREFIX
AR = Aurigent Research
DATE COMPONENT
YYYY-MM-DD (ISO-8601)
VERSION COMPONENT
Vn = major version number
ENTRY ID FORMAT
AR-YYYY-MM-DD-Vn-Em
ENTRY COMPONENT
Em = entry index within record (E1, E2, ...)
UUID FORMAT
RFC 4122
UUID USAGE
RECORD SIGNATURE, INGESTION ID

07 / RECORD STATES

Record States

LIFECYCLE STATES

DRAFT
Composition state. Not distributed. May be discarded or revised without retention.
FINALIZED
Issued state. Distributed under access classification. Subject to append-only retention. May not be deleted or revised; corrections issued as new versions.
SUPERSEDED
Superseded by a subsequent issuance under revised review. Retained indefinitely; excluded from active reference sets.

08 / 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 Version
Status
Effect
v3.2
ACTIVE
GOVERNING SCHEMA
v3.1
SUPERSEDED
NO NEW ISSUANCES
v3.0
SUPERSEDED
LEGACY REFERENCE ONLY
v2.x
ARCHIVED
HISTORICAL REFERENCE ONLY

09 / CROSS-REFERENCES

Cross-References

Extraction Specification→
Record Specimen→

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