← Method

Method / FVE-1 Data Pipeline

FVE-1 Data Pipeline

End-to-End Outline · V1.0 · Schema FVE-1 V5.5

Authoritative sequencing reference — individual protocol documents govern each stage in full detail

This document maps the complete FVE-1 data pipeline from environment setup through reporting. It establishes the order, the gates, and the governing document for each stage. It does not reproduce protocol details — those live in the individual instrument and infrastructure documents. Stubs are stages for which a governing protocol does not yet exist.

Pipeline Map

0
Environment & Provenance Setup
1
BOWL Baseline Collection
2
Instrument Execution
3
Human Coding Pass
4
Export & Reproducibility Bundle
5
Model Sidecar / Independent Coding Pass
6
Aggregation
7
Panel Comparison
8
Analysis Output
9
Reporting

Stages 3 and 5 run in parallel after Stage 2. Both must complete before Stage 6.

0

Environment & Provenance Setup

operational
When: Once per research program or per parameter adjustment. Not per session.
Governing document: Atlas-Protocol-PARAMETER-SIGNING-V1.0
Gate:
SIG VALID on active parameter JSON. ROOT present in codebook. Active variable code logged in Recovery Spine. No stage proceeds without a valid provenance chain.
1

BOWL Baseline Collection

operational
When: Once per model under test, before any instrument that requires register coding.
Governing document: Atlas-Protocol-SOUP-V1.1 · Atlas-Protocol-BASELINE-DERIVATION-V1.0
Gate:
baseline_code, soup_session_code, and provenance_signature all present and logged in Recovery Spine. Baseline Deriver returned SIG VALID.
Output: SOUP session CSV · Human record MD · baseline_code · soup_session_code · provenance_signature
2

Instrument Execution

operational
When: After Stage 1 baseline is established for the model under test.
Instruments:
2a — DRILLoperational
Atlas-Protocol-DRILL-V1.2
View →
2b — FLIGHToperational
Atlas-Protocol-FLIGHT-V2.1
View →
2c — DIP / MEGA DIPstub
DIP-Protocol-Outline-V0.1
Draft — external review. Not yet operational.
View →
2d — HFS Batterydeferred
Atlas-Protocol-HFS-V2.2
Stub — pending protocol document.
Gate:
Valid provenance chain confirmed. BOWL baseline on file for models requiring register axis coding.
3

Human Coding Pass

operational
When: First pass in session, live. Validation pass post-session against MD export.
Governing document: Atlas-Protocol-HUMAN-CODER-V1.0 · ECM-Resolution-Code-Coder-Guide-V4.0
Gate:
Human validation complete. fidelity_result is Pass or Partial. All Layer 1 gates clear.
Output: Human-coded session CSV · Annotated MD export
4

Export & Reproducibility Bundle

stub
When: After human coding pass is complete.
Governing document: STUB — reproducibility governance document not yet written.
Gate:
CSV and MD exports present. baseline_code, soup_session_code, provenance_signature confirmed non-null. Signed parameter JSON copy in bundle.
Output: Session CSV · Session MD · Baseline profile CSV · Signed parameter JSON copy · README
5

Model Sidecar / Independent Coding Pass

operational
When: Any time after Session Export. Does not wait for human validation.
Governing document: Atlas-Protocol-MODEL-CODER-SPINE-V2.0
Gate:
Both human (Stage 3) and model (Stage 5) outputs must be present before aggregation. Model passes may accumulate — they wait at the aggregation gate.
Output: Sidecar CSV per frame · Pre-aggregation independent review CSV
6

Aggregation

operational
When: After both Stage 3 (human validation cleared) and Stage 5 (model coding pass complete).
Governing document: Atlas-Protocol-AGGREGATION-V1.0
Gate:
Human validation complete. provenance_signature present and non-null. baseline_code present, non-null, and matching across all sessions. baseline_code present in codebook. obs_reg null condition documented if soup_session_code is null.
Output: Aggregated session summary per model
7

Panel Comparison

operational
When: After aggregation is complete for all models in the panel or declared subset.
Governing document: Atlas-Protocol-PANEL-COMPARISON-V1.0
Gate:
Aggregation confirmed complete for all models in declared scope. Five parameter values identical across all models. Delta policy declared by operator.
Output: Cross-model comparison table · Register trajectory comparison · Failure mode frequency by model
8

Analysis Output

operational
When: After Stage 7.
Governing document: Atlas-Protocol-ANALYSIS-OUTPUT-V1.0
Gate:
Variable code, threshold values, and provenance chain stated in any methods paper. Sessions derived under different variable codes reported separately.
Output: ECM Token Economy tables · Failure mode catalogs · Compression arc comparisons · Cross-model register trajectory summaries · PyHessian input preparation
9

Reporting

stub
When: After Stage 8.
Governing document: STUB — reporting protocol not yet written.

Recovery Spine

The Recovery Spine is the live operational ledger — separate from this pipeline outline. It tracks current run queue, clean triad status per panel model, data pipeline gaps, instrument exclusion log, confound log, and pre-flight QC notes. Every stage that modifies pipeline state requires a Recovery Spine update. The spine is the authoritative record of what has actually happened.

FVE-1 Data Pipeline V1.0 · Schema FVE-1 V5.5 · Atlas Heritage Systems · KC Hoye, PI