FER / RESEARCH / SPEC
SCHEMA v3.2 · EXTRACTION
01 / STATEMENT
Feraston Research · Schema v3.2 · Extraction Specification
Extraction Specification
This specification defines the canonical extraction interface for Feraston 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.
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: FR-2026-03-04-V1
PRECEDING RECORD: FR-2026-02-25-V1
STATUS: FINALIZED
SCHEMA VERSION: 3.2
ACCESS CLASSIFICATION: EXECUTIVE
ENTRY ID: FR-2026-03-04-V1-E3
ENTITY: BMW; HEXAGON; FIGURE AI
SUBJECT: HUMANOID ROBOT DEPLOYMENT FOLLOWING BODY-SHOP PILOTS
SUBJECT CLASS: DEPLOYMENT
DOMAIN: ROBOTICS INTEGRATION
GEOGRAPHY: GERMANY; UNITED STATES
FUNCTIONAL DOMAIN: MANUFACTURING ENGINEERING AND INDUSTRIALIZATION; SYSTEMS AND INTEGRATION
DEFINITION:
BMW is deploying Hexagon's AEON humanoid robots at its Leipzig assembly plant after trials with a Figure 02 unit in Spartanburg demonstrated body-shop handling performance.
STRUCTURE:
In the body-shop pilot, Figure 02 removed and positioned sheet metal, moving 90,000 parts and logging about 1.2 million steps over 1,250 operating hours in a constrained production setting.
EFFECT:
Narrows feasible task candidates and informs definition of end-of-arm tooling, safety cases, control interfaces, and deployment boundaries before broader series rollout.
EXTRACTION
──────────
record.id = "FR-2026-03-04-V1"
record.preceding_id = "FR-2026-02-25-V1"
record.status = "FINALIZED"
record.schema_version = "3.2"
record.access_class = "EXECUTIVE"
entry[0].id = "FR-2026-03-04-V1-E3"
entry[0].entity = ["BMW", "HEXAGON", "FIGURE AI"]
entry[0].subject = "HUMANOID ROBOT DEPLOYMENT FOLLOWING BODY-SHOP PILOTS"
entry[0].subject_class = "DEPLOYMENT"
entry[0].domain = "ROBOTICS INTEGRATION"
entry[0].geography = ["GERMANY", "UNITED STATES"]
entry[0].functional_domain = ["MANUFACTURING ENGINEERING AND INDUSTRIALIZATION", "SYSTEMS AND INTEGRATION"]
entry[0].body.definition = "BMW is deploying Hexagon's AEON humanoid robots at its Leipzig assembly plant after trials with a Figure 02 unit in Spartanburg demonstrated body-shop handling performance."
entry[0].body.structure = "In the body-shop pilot, Figure 02 removed and positioned sheet metal, moving 90,000 parts and logging about 1.2 million steps over 1,250 operating hours in a constrained production setting."
entry[0].body.effect = "Narrows feasible task candidates and informs definition of end-of-arm tooling, safety cases, control interfaces, and deployment boundaries before broader series rollout."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 Feraston inquiry channels.
09 / CROSS-REFERENCES
Cross-References
Feraston Research Extraction Specification · Schema v3.2