51-Pipeline Card Template v1.0 | Chapter 1 — Scope of Use & Dependencies

Home ／ Docs-Technical WhitePaper ／ 51-Pipeline Card Template v1.0

Chapter 1 — Scope of Use & Dependencies

I. Scope of Use

• Pipeline types: Batch, Streaming, Near-RT, Hybrid.
• Operating regime: paraxial/small-angle, slowly varying medium, and coherence windows T_coh/L_coh/B_coh hold. For stages involving path quantities (arrival time/phase), the text must explicitly show gamma(ell) and the measure d ell, and the data side must record delta_form ∈ {general, factored}; publication requires p_dim = 1.0.
• Data objects: inbound/outbound contracts aligned with TARR; all references to Parameters/Errors/Protocol use “volume + version + anchor (P/S/M/I)”.
• Applicable scenarios: end-to-end modeling/inference/metrology loops (with replay & recalibration); cross-team delivery and comparative scoring.

II. Pipeline Scenarios Matrix

III. Dependencies

• Core (required): EFT.WP.Core.Terms v1.0, EFT.WP.Core.Equations v1.1, EFT.WP.Core.Metrology v1.0, EFT.WP.Core.DataSpec v1.0.
  Unified arrival/phase forms:
  T_arr = ( 1 / c_ref ) * ( ∫ n_eff d ell ); T_arr = ( ∫ ( n_eff / c_ref ) d ell );
  Phi = ( 2π / λ_ref ) * ( ∫ n_eff d ell ).
• Templates (companion): PTN Template v1.0 (Ch.5/Ch.11), Parameter Registration Card Template v1.0 (Ch.3/Ch.9), Error Budget Card Template v1.0 (Ch.5/Ch.6/Ch.8/Ch.9), Experimental Protocol Card Template v1.0 (Ch.5/Ch.11).
• Runtime & metrology: Metrology.TimeBase v1.0, Metrology.Sync v1.0, Metrology.Instrument v1.0, Metrology.PathCorrection v1.0, Methods.Repro v1.0.

IV. Citations & Versioning

• Fixed syntax: See "<Volume> vX.Y" <Chapter> <Anchor>, prioritize P/S/M/I; anchor coverage ≥ 90%, no external links/aliases.
• Version policy: public releases cite v1.* only; if citing v0.*, mark “draft / non-committal” in text.
• Dependency closure: cross-card/cross-volume citations must be synchronized in see[]/references[] and the artifact manifest.

V. Compliance Prerequisites

• Dimensional closure: pass I70-dim_check and attach check_dim_report.json; p_dim = 1.0.
• Sync freshness: clock_state="locked", |ts_start − calib.timestamp| ≤ τ_calib.
• Path consistency: len(gamma_ell)=len(d_ell)=len(n_eff)≥2, Δell meets sampling constraints; missing path/measure is reject.
• Parameter alignment: all used parameters are registered in the Parameter Card and have passed parameter-level gates (G1–G8).

VI. Gate Mapping (pipeline level)

• G1 Schema completeness | G2 Citation compliance | G3 Path conventions | G4 Dimensional closure | G5 Freshness | G6 Coverage conventions | G7 Covariance consistency | G8 Uniqueness.
• Triggering S1–S5 (dimensional failure/freshness failure/path missing/covariance mismatch/citation non-compliance) blocks stage execution & release; enter [Restricted] if necessary.

VII. Outputs & Interfaces

1. Artifacts: pipeline_graph.json, stage.yaml, param_registry.csv, check_dim_report.json, audit.jsonl, figures (DAG/perf/path profile), report_manifest.yaml.
2. Interfaces:
   • I60-stage_exec(ctx, x) -> y | err
   • I61-validate_gate(card, gates[]) -> report.json
   • I62-export_artifacts(fmt) -> {manifest, checksums}
3. Security: least-privilege access; write endpoints log audit events created|updated|validated|locked.

VIII. Checklist

• Scenarios & dependencies confirmed; see[]/references[] compliant, anchor coverage ≥ 90%.
• For path-related stages: explicit gamma(ell)/d ell in text; delta_form recorded on data side.
• I70-dim_check passed, p_dim = 1.0; clock_state="locked", τ_calib compliant.
• Parameter & Error cards ready (domain/units/coverage/cov_group consistent); covariance & UQ config aligned with Error Budget.
• /validate passed G1–G8; release includes report_manifest.yaml, audit.jsonl, and signature.