AUR / RESEARCH / SPEC
SCHEMA v3.2 · EXTRACTION
01 / STATEMENT
Aurigent Research · Schema v3.2 · Extraction Specification
Extraction Specification
This specification defines the canonical extraction interface for Aurigent Research records. Records may be extracted programmatically by authorized systems from PDF, HTML, and structured-text representations.
02 / SCOPE
Scope
SCOPE · CONFORMANCE REGISTRY
03 / CANONICAL FIELD ANCHORS
Canonical Field Anchors
Each extractable field is preceded by a canonical anchor. Anchors are case-sensitive and terminated by a colon. Extraction routines MUST locate fields by anchor and MUST NOT rely on positional offsets.
ANCHOR · FIELD MAPPING
04 / EXTRACTION RULES
Extraction Rules
01
ANCHOR PRECEDENCE
Anchors MUST be matched at line start, with optional leading whitespace not exceeding two spaces. Anchors appearing within entry bodies are treated as literal content, not field markers.
02
VALUE TERMINATION
Field values are terminated by the next valid anchor, by a section divider, or by end-of-record. Multi-line values preserve internal whitespace. Trailing whitespace is stripped.
03
ENTRY DELIMITATION
Entries are delimited by the appearance of the ENTRY_ID: anchor. The first ENTRY_ID: occurrence within a record begins the first entry; each subsequent occurrence terminates the prior entry and begins the next.
04
UUID VALIDATION
RECORD_SIGNATURE and INGESTION_ID values MUST conform to RFC 4122 UUID format. Records failing UUID validation MUST be rejected and flagged for review; partial extraction is not permitted.
05
VERSION CHAINING
PRECEDING_RECORD values establish the issuance chain. Extraction routines SHOULD validate chain continuity by reconciling each PRECEDING_RECORD against a known prior RECORD_ID. Broken chains MUST be reported but do not invalidate the current record.
06
STATUS HANDLING
Only records with STATUS: FINALIZED are eligible for downstream indexing. DRAFT records MUST NOT be extracted. SUPERSEDED records MUST be retained but excluded from active reference sets.
07
SCHEMA CONFORMANCE
Records emitting a SCHEMA VERSION other than the active schema MUST be routed to the appropriate schema handler. Cross-schema extraction is not permitted within a single pipeline pass.
08
ACCESS CLASSIFICATION ENFORCEMENT
Extraction routines MUST honor the ACCESS_CLASSIFICATION field. Records classified RESTRICTED or INTERNAL MUST NOT be redistributed beyond the originating recipient system. Downstream indexing MUST preserve classification metadata.
09
ENTRY COUNT RECONCILIATION
The ENTRY_COUNT value declares the number of entries contained in the record. Extraction routines MUST reconcile ENTRY_COUNT against the number of entries delimited by ENTRY_ID: anchors. A mismatch MUST be reported for review and does not, on its own, invalidate the record.
05 / REFERENCE EXTRACTION
Reference Extraction
The following block illustrates a canonical extraction pass over a record fragment. The example is non-normative and provided for reference only.
REFERENCE · EXTRACTION PASS
INPUT
─────
RECORD_ID: AR-2026-04-01-V1
PRECEDING_RECORD: AR-2026-03-25-V1
STATUS: FINALIZED
SCHEMA_VERSION: 3.2
ACCESS_CLASSIFICATION: EXECUTIVE
ENTRY_COUNT: 5
ENTRY_ID: AR-2026-04-01-V1-E3
ENTITY: APPLIED INTUITION; LG INNOTEK
SUBJECT: SENSOR STACK INTEGRATION WITH SELF-DRIVING SYSTEM
SUBJECT_CLASS: INTEGRATION
DOMAIN: PERCEPTION SYSTEMS
GEOGRAPHY: UNITED STATES; SOUTH KOREA
FUNCTIONAL_DOMAIN: AUTONOMY AND PERCEPTION ENGINEERING; SOFTWARE INFRASTRUCTURE AND DATA OPERATIONS
DEFINITION:
Applied Intuition and LG Innotek agreed to integrate LG camera, lidar, and radar hardware with Applied's Self-Driving System using test vehicles and sensor digital twins.
STRUCTURE:
Fleet data and sensor digital twins establish a closed validation loop for perception development, enabling coordinated hardware-software testing while reducing multi-vendor integration complexity.
EFFECT:
Enables tighter coupling of sensor hardware and autonomy software in validation workflows, while positioning LG within Applied's software stack and advancing bundled sensor and autonomy offerings in automaker sourcing processes.
EXTRACTION
──────────
record.id = "AR-2026-04-01-V1"
record.preceding_id = "AR-2026-03-25-V1"
record.status = "FINALIZED"
record.schema_version = "3.2"
record.access_class = "EXECUTIVE"
record.entry_count = 5
entry[0].id = "AR-2026-04-01-V1-E3"
entry[0].entity = ["APPLIED INTUITION", "LG INNOTEK"]
entry[0].subject = "SENSOR STACK INTEGRATION WITH SELF-DRIVING SYSTEM"
entry[0].subject_class = "INTEGRATION"
entry[0].domain = "PERCEPTION SYSTEMS"
entry[0].geography = ["UNITED STATES", "SOUTH KOREA"]
entry[0].functional_domain = ["AUTONOMY AND PERCEPTION ENGINEERING", "SOFTWARE INFRASTRUCTURE AND DATA OPERATIONS"]
entry[0].body.definition = "Applied Intuition and LG Innotek agreed to integrate LG camera, lidar, and radar hardware with Applied's Self-Driving System using test vehicles and sensor digital twins."
entry[0].body.structure = "Fleet data and sensor digital twins establish a closed validation loop for perception development, enabling coordinated hardware-software testing while reducing multi-vendor integration complexity."
entry[0].body.effect = "Enables tighter coupling of sensor hardware and autonomy software in validation workflows, while positioning LG within Applied's software stack and advancing bundled sensor and autonomy offerings in automaker sourcing processes."06 / DELIMITER NORMALIZATION
Delimiter Normalization
Several anchors emit values as semicolon-delimited lists. Extraction routines MUST normalize these into array structures.
DELIMITER · NORMALIZATION RULES
07 / ERROR HANDLING
Error Handling
ERROR · CONDITION REGISTRY
08 / CONFORMANCE
Conformance
Implementations claiming conformance to this specification MUST extract all fields defined in Section 03, MUST observe the rules in Section 04, MUST normalize delimited values per Section 06, and MUST handle error conditions per Section 07. Formal conformance review may be requested through Aurigent inquiry channels.
09 / CROSS-REFERENCES
Cross-References
Aurigent Research Extraction Specification · Schema v3.2