Method / Dependency Map
Dependency Map
Methodological · Schema FVE-1 V5.5 · Maintained with each schema revision
A technician's reference for understanding what must exist before you can run an instrument, and what breaks when foundational components change. Schema is authoritative — if this page drifts from the schema, flag to KC.
Provenance Chain
Everything downstream depends on this chain being intact. Do not skip steps.
Build Order — Prerequisites by Instrument
What must exist before you can run each instrument.
Run once per research program or per parameter adjustment. Not per session. If active parameter set is already signed and SIG VALID confirmed in deriver — do not re-sign.
Run once per new signed JSON. Lineage must trace back to ROOT. Orphan entries fail at aggregation.
Loads signed JSON, confirms SIG VALID, derives baseline profile from BOWL session output. Produces baseline_code and provenance_signature.
First instrument to run on any new model. Output is baseline_code — required for register axis data in all downstream sessions.
Three sessions required. Register axis null without BOWL baseline — log null condition on all register fields. Do not run PyHessian alignment on null-register data.
16 sessions required. Four batches × four frames. Same model throughout. BOWL baseline required for register axis. Null condition must be logged if baseline missing.
Vocabulary layer. No session prerequisites. ECM quadrant definitions travel into all instrument coding.
Runs 1–3 complete. Stopwatch instrument — point-to-point distance only. Cannot derive trajectory. Runs independently of FVE-1 stack.
Schema locked, forms built. Divergence Testing is Phase 2 sub-component — run first for full BSA.
Independent of FVE-1 stack. Can run anytime with clean sessions.
Pending data pipeline automation.
Pending data pipeline automation. Register escape specimens are generated by DRILL and FLIGHT — flagged in Technician's Read #1 when obs_reg produces RS or RC.
Change Impact Matrix
If you update a foundational component, what else must be reviewed.
All FVE-1 instrument pages, HTML tools (Session Logger, DRILL Tool, FLIGHT Tool, SOUP Tool, Baseline Deriver), signed parameter JSON format, codebook entries
Parameter Signing Tool — create new signed JSON. All downstream sessions must carry new baseline_code. Prior sessions under old parameters are not comparable without explicit stratification.
Do not modify ROOT. ROOT is a locked artifact. Modifying it breaks the entire lineage chain. If ROOT is missing, locate in archive — do not recreate.
BSA protocol, EPG protocol, Divergence Testing protocol, Glossary, all coded data — retroactive recoding required if definitions change
All existing baseline_codes derived under prior stimulus are not comparable. Treat as a new baseline instrument version. Document the change date as a provenance seam.
CISP protocol page, all instrument tier assignment checklists
Divergence Testing protocol page, all prior flagged pair classifications
All coded data — check for retroactive reclassification. Document version of coder guide active at time of each session in fidelity_notes.
For Technicians — What This Means Day-to-Day
Run the provenance chain first. Parameter signing → codebook → BOWL → baseline derivation. Do not open a DRILL or FLIGHT session until baseline_code is confirmed.
This is the baseline session. BOWL output feeds directly into the Baseline Deriver. Signed parameter JSON must be loaded and SIG VALID before derivation. Do not derive under the wrong JSON.
All three sessions required — Gödel, Transformer, FAST NONE. Do not run PyHessian alignment on null-register data. Register axis is null without a confirmed BOWL baseline.
All 16 sessions required. Four batches × four frames. BOWL baseline required for register axis. Batch and frame sequence are locked — do not reorder.
Only need stimulus set and fresh sessions. No dependency on FVE-1 stack. Stopwatch instrument — measures distance, not trajectory.
Check this page. The change impact matrix tells you what else to review. Schema is authoritative — if this page drifts from the schema, flag to KC.
Flag to KC. Schema is authoritative. This page documents it.