AXE / RESEARCH / SPEC

SCHEMA v3.2 · EXTRACTION

01 / STATEMENT

Axendale Research · Schema v3.2 · Extraction Specification

Extraction Specification

This specification defines the canonical extraction interface for Axendale Research records. Records may be extracted programmatically by authorized systems from PDF, HTML, and structured-text representations.

02 / SCOPE

Scope

SCOPE · CONFORMANCE REGISTRY

CONFORMANCE TARGET

Axendale Research Schema v3.2

DELIVERY FORMATS

PDF/A-2b, HTML, structured text

RECORD CLASS

Intelligence Record (TYPE: AX)

ACCESS CLASSIFICATION

EXECUTIVE | RESTRICTED | INTERNAL

DELIVERY MODE

Direct distribution; no public endpoint

RETENTION

Permanent, append-only post-finalization

EXTRACTION INTERFACE

Field-level extraction via canonical anchors

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

TYPE:

record.type

RECORD ID:

record.id

PRECEDING RECORD:

record.preceding_id

RECORD SIGNATURE:

record.signature_uuid

VERSION:

record.version

STATUS:

record.status

ISSUED:

record.issued_date

RECORD MODE:

record.mode

RETENTION PERIOD:

record.retention

SCHEMA VERSION:

record.schema_version

ACCESS CLASSIFICATION:

record.access_class

ENTRY ID:

entry.id

INGESTION ID:

entry.ingestion_uuid

ENTITY:

entry.entity

SUBJECT:

entry.subject

SUBJECT CLASS:

entry.subject_class

DOMAIN:

entry.domain

GEOGRAPHY:

entry.geography

FUNCTIONAL DOMAIN:

entry.functional_domain

DEFINITION:

entry.body.definition

STRUCTURE:

entry.body.structure

EFFECT:

entry.body.effect

04 / EXTRACTION RULES

Extraction Rules

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.

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.

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.

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.

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.

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.

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.

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.

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: AX-2026-02-25-V1
PRECEDING RECORD: AX-2026-02-18-V1
STATUS: FINALIZED
SCHEMA VERSION: 3.2
ACCESS CLASSIFICATION: EXECUTIVE
ENTRY ID: AX-2026-02-25-V1-E3
ENTITY: BRIGHTPICK; NAPA
SUBJECT: GOODS-TO-PERSON ROBOTICS NETWORK DEPLOYMENT
SUBJECT CLASS: DEPLOYMENT
DOMAIN: FULFILLMENT AUTOMATION SYSTEMS
GEOGRAPHY: UNITED STATES
FUNCTIONAL DOMAIN: NETWORK STRATEGY AND DESIGN; SYSTEMS AND INTEGRATION
DEFINITION:
Brightpick and NAPA signed a partnership to deploy Brightpick goods-to-person robots across NAPA distribution centers, beginning with a new site using more than 100 robots following a 2025 pilot.
STRUCTURE:
Goods-to-person robotics, standardized warehouse management system interfaces, and repeatable commissioning procedures align to enable network-scale rollout for store replenishment.
EFFECT:
Signals a transition from site-level pilots to network-scale automation, requiring KPI acceptance tests and integration standardization to reduce per-site rework across distribution networks.

EXTRACTION
──────────
record.id                    = "AX-2026-02-25-V1"
record.preceding_id          = "AX-2026-02-18-V1"
record.status                = "FINALIZED"
record.schema_version        = "3.2"
record.access_class          = "EXECUTIVE"
entry[0].id                  = "AX-2026-02-25-V1-E3"
entry[0].entity              = ["BRIGHTPICK", "NAPA"]
entry[0].subject             = "GOODS-TO-PERSON ROBOTICS NETWORK DEPLOYMENT"
entry[0].subject_class       = "DEPLOYMENT"
entry[0].domain              = "FULFILLMENT AUTOMATION SYSTEMS"
entry[0].geography           = ["UNITED STATES"]
entry[0].functional_domain   = ["NETWORK STRATEGY AND DESIGN", "SYSTEMS AND INTEGRATION"]
entry[0].body.definition     = "Brightpick and NAPA signed a partnership to deploy Brightpick goods-to-person robots across NAPA distribution centers, beginning with a new site using more than 100 robots following a 2025 pilot."
entry[0].body.structure      = "Goods-to-person robotics, standardized warehouse management system interfaces, and repeatable commissioning procedures align to enable network-scale rollout for store replenishment."
entry[0].body.effect         = "Signals a transition from site-level pilots to network-scale automation, requiring KPI acceptance tests and integration standardization to reduce per-site rework across distribution networks."

06 / DELIMITER NORMALIZATION

Delimiter Normalization

Several anchors emit values as semicolon-delimited lists. Extraction routines MUST normalize these into array structures.

DELIMITER · NORMALIZATION RULES

ENTITY

Semicolon-delimited list of entity names; normalize to array of strings

GEOGRAPHY

Semicolon-delimited list of ISO regions or jurisdictions; normalize to array of strings

FUNCTIONAL DOMAIN

Semicolon-delimited list of canonical functional domains; normalize to array of strings

SUBJECT CLASS

Single-value scalar; free-form controlled vocabulary; do not enumerate against a fixed set

07 / ERROR HANDLING

Error Handling

ERROR · CONDITION REGISTRY

ANCHOR_NOT_FOUND

A required anchor is missing from the input. Extraction halts; record flagged for review.

UUID_VALIDATION_FAILED

RECORD SIGNATURE or INGESTION ID does not conform to RFC 4122. Record rejected; partial extraction not permitted.

SCHEMA_MISMATCH

SCHEMA VERSION does not match the active handler. Record routed to versioned handler or rejected.

CHAIN_BROKEN

PRECEDING RECORD does not match any known prior RECORD ID. Reported as warning; record not invalidated.

STATUS_INELIGIBLE

Record STATUS is not FINALIZED. Record retained but excluded from active indexing.

ACCESS_VIOLATION

Extraction attempted by a system without authorization for the record's ACCESS CLASSIFICATION. Extraction rejected; access attempt logged.

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 Axendale inquiry channels.

Submit Conformance Review →

09 / CROSS-REFERENCES

Cross-References

Record Index→

Schema Reference→

Record Specimen→

Axendale Research Extraction Specification · Schema v3.2