08-EFT.WP.Core.Sea v1.0 | Preface

Home ／ Docs-Technical WhitePaper ／ 08-EFT.WP.Core.Sea v1.0

Preface

I. Scope and Positioning

• This volume codifies engineering methods and norms at the Sensing / Environment / Acquisition layer: from sensor registration and calibration, through fs setup and anti-aliasing filter design H(f), to PSD/feature extraction, environmental correction corr_env(x; RefCond), arrival-time estimation T_arr, quality and drift monitoring, and lossless persistence via fmt/manifest—an end-to-end, reproducible loop.
• It is the “minimal reproducible specification” for the EFT Core sensing domain, bound to implementation interfaces I80-, and interoperable with the concurrency/execution domain **Core.Threads (I70-)**, the metrology domain Core.Metrology, and the data domain Core.DataSpec.
• Out of scope: domain inference and business semantics, model-training internals, domain-specific control laws, UI and operational playbooks. See Core.Models, Core.Control, Core.Operate, and the companion white paper Energy Filaments for those topics.

II. Audience and Use Cases

1. Intended readers
   • Platform / systems engineers: sensing platforms, data paths, traceability and compliance.
   • Algorithm / metrology engineers: spectral/statistical robustness, u(x) and expanded uncertainty U = k * u_c.
   • Field engineers: multi-device synchronization, interference hardening, drift and re-calibration strategy.
2. Representative scenarios
   • High-fidelity laboratory acquisition (high ENOB, narrow BW, strict corr_env).
   • Long-horizon field monitoring (multi-sensor, controlled jitter J, explicit missingness mask m).
   • Online streaming capture (high fs, rolling PSD/features, fast persistence and tracing).

III. Design Principles

• Reproducibility. Any derived quantity must disclose source signal, filters, and windowing; ts (UTC) is used for publication and audit, tau_mono for timing math and timeout budgets.
• Composability. Each stage exposes an Mx-* workflow and I80-* primitive, allowing drop-in composition with channel semantics (chan/cap/q_len) from Core.Threads.
• Metrologically sound. Dimensional closure and uncertainty propagation are mandatory; check_dim(expr) must pass. Joint estimation of u(alpha_i), u(beta_i) for clock sync is reported explicitly.
• Traceability. Persist using fmt ∈ {"jsonl","csv","parquet","nc","tfrecord"} with a companion manifest capturing sid/model/serial/cal_id, fs, H(f), RefCond, and version fingerprints.

IV. Terminology and Notation

1. Variables and formulae are in English plain text; inline symbols are back-ticked, e.g., fs, ENOB, H(f), S_xx(f), offset, skew, q_score, m ∈ {0,1}.
2. Any division, integral, or composite operator is parenthesized and, when path-dependent, carries explicit path and measure: gamma(ell), d ell. Examples:
   • Constant-factored: T_arr = ( 1 / c_ref ) * ( ∫ n_eff d ell )
   • General form: T_arr = ( ∫ ( n_eff / c_ref ) d ell )
3. Unified numbering: postulates P8x-, minimal equations S8x-, metrology/acquisition workflows Mx-, implementation bindings I80-. Cross-volume cites use the fixed style: “see companion white paper Energy Filaments, Chapter x S/P/M/I…”.
4. Conflict naming (strict): T_fil vs. T_trans must not be mixed; n vs. n_eff are strictly distinct.

V. Normative Assumptions

• Sampling & anti-aliasing. fs >= 2 * f_max is a hard constraint. If fs < 2 * f_max, you must provide anti-aliasing specifications for H(f) and a residual aliasing estimate.
• Synchronization model. For device i, ts_i(t) = alpha_i * tau_mono + beta_i, where alpha_i is skew and beta_i is offset; attach u(alpha_i) and u(beta_i).
• Arrival-time consistency. Any use of T_arr must co-report gamma(ell), d ell, c_ref, n_eff, and the dual-form gap:
  delta_form = | ( 1 / c_ref ) * ( ∫ n_eff d ell ) - ( ∫ ( n_eff / c_ref ) d ell ) |.
• Quality closed-loop. Missingness and anomalies are marked via m and q_score; any derived statistic must declare whether it assumes approx independence and which window function is used.

VI. Interfaces to Sibling Volumes

• Core.Threads. I80-* acquisition/sync/filter operators are executable thr units in G = (V,E); backpressure and limiting rely on chan/cap/q_len and bp policies (see Mx workflows and I70-*).
• Core.Metrology. Reuse its specifications for propagate_uncertainty, combined standard uncertainty u_c, and expanded uncertainty U = k * u_c—including parameterization and reporting.
• Core.DataSpec. Field dictionary, enumerations, and manifest templates are aligned; use bind_to_parameters to register RefCond, fs, H(f), etc.
• Core.Equations. Physical modeling of medium-equivalent parameters n_eff(x,t), path gamma(ell), and reference speed c_ref shall follow its S-series entries for values and calibration.

VII. Compliance Levels and Implementation Grades

1. Sea / Basic
   • Required: register_sensor, configure_sampling, fft/psd, serialize, export_manifest.
   • Outputs: ts/tau_mono, fs/ENOB/DR, window parameters, and H(f) summary.
2. Sea / Full
   • Adds: sync_clocks, measure_skew_offset, apply_env_correction, propagate_uncertainty, monitor_drift, estimate_toa.
   • Outputs: u(alpha_i), u(beta_i), dual forms of T_arr and delta_form.
3. Sea / RT
   Requires: streaming PSD/features, online q_score with raise_alert, rolling persistence and tracing.

VIII. Structure and Reading Path

• Ch.1–2: device spectra and sampling/quantization; establish baselines for fs/ENOB/DR and anti-aliasing.
• Ch.3–4: synchronization model and signal conditioning; secure timing and dynamic range.
• Ch.5–6: spectral analysis and uncertainty; build comparable, reproducible analysis surfaces.
• Ch.7–8: data path and T_arr; complete end-to-end traceability and cross-volume alignment.
• Ch.9–10: quality/drift and reference pipelines; support long-run operations and benchmarking.

IX. Versioning and Change Management