44-EFT.WP.Data.ModelCards v1.0 | Chapter 2 Terms & Dependencies

Home ／ Docs-Technical WhitePaper ／ 44-EFT.WP.Data.ModelCards v1.0

Chapter 2 Terms & Dependencies

I. Chapter Position & Coverage

II. Terminology Sources & Version Pinning

• General terminology: Follow EFT Technical Whitepaper & Notes — Comprehensive Template v0.1; this volume adds Model-Card-specific terms only. Citations must include “Volume + Version + Chapter/Anchor”. Example: See "EFT.WP.Core.Equations v1.1" Ch.2 S20-1.
• Pinned minimal dependency set: Core.Terms v1.0, Core.Metrology v1.0, Core.Equations v1.1, EFT.WP.Data.DatasetCards v1.0. If higher versions are needed, declare explicitly in the Model Card metadata.
• Clause-level citations: Prefer P/S/M/I anchors; avoid whole-volume generic cites and aliases.

III. Unified Symbols & Notation (Model-Card additions)

• Inline symbols: Always wrap with backticks (e.g., f_θ(x), p(y|x,θ), L(θ), ŷ, z, T_arr, c_ref, n_eff). Any expression with division/integral/composite operators must use parentheses and explicitly declare path gamma(ell) and measure d ell; no Chinese in formulas/symbols/definitions.
• Training/eval params: η (learning rate), B (batch size), s (seed), M_param (parameter count), FLOPs, T_inf (per-sample latency).
• Probability & calibration: ECE, Brier, q(y|x) (post-calibration distribution).
• Robustness/shift: δ (perturbation), ‖δ‖_p, τ (threshold).

IV. Field Naming Style & Reserved Keys

• Style: Keys use snake_case; arrays denote plural entities.
• Reserved (do not repurpose): model_id, version, task, io_schema, architecture, training_data, preprocess, optimization, hyperparams, evaluation, calibration, robustness, fairness, safety, deployment, resources, export_manifest.

V. Cross-Volume Dependency Map (minimal set)

• Terms/definitions: EFT.WP.Core.Terms v1.0.
• Metrology/units/uncertainty: EFT.WP.Core.Metrology v1.0 (check_dim, error-budget workflows).
• Path-dependent equations: EFT.WP.Core.Equations v1.1 (Ch.2 S20-*: arrival time; minimal path-integral forms).
• Data facts/splits/quality: EFT.WP.Data.DatasetCards v1.0 (reference data sources and frozen splits).

VI. Citation & Anchor Rules

• Fixed format: See "<Volume> vX.Y" Ch.<n> <Anchor>; anchor types: Postulates Pxx-?, Minimal equations Sxx-?, Metrology workflows Mx-?, Implementation bindings Ixx-?.
• Machine-readable references: Use "Volume vX.Y:Anchor" in see[]; export_manifest must include version and references[].
• Prohibitions: No shortcodes/aliases/missing versions.

VII. Arrival Time T_arr Dependency Posture (if applicable)

1. Two equivalent expressions:
   • T_arr = ( 1 / c_ref ) * ( ∫ n_eff d ell )
   • T_arr = ( ∫ ( n_eff / c_ref ) d ell )
2. Registration: Whenever T_arr appears, record in Model Card metadata: delta_form, path="gamma(ell)", measure="d ell", and pass check_dim.

VIII. Conflict Names & No-Mix Rules

IX. Machine-Readable Dependencies & Implementation Binding

• see[] example:
• see:
• - "EFT.WP.Core.Equations v1.1:S20-1"
• - "EFT.WP.Core.Metrology v1.0:check_dim"
• - "EFT.WP.Data.DatasetCards v1.0:EXPORT"
• export_manifest requirements:
• version: "v1.0"
• references:
• - "EFT.WP.Core.Equations v1.1:S20-1"
• - "EFT.WP.Core.Metrology v1.0:check_dim"
• - "EFT.WP.Data.DatasetCards v1.0:Ch.11"

(Format aligns with Citation & Cross-Reference Spec v0.1.)

X. Chapter Compliance Checklist

• All citations include “Volume+Version+Chapter/Anchor,” preferably to P/S/M/I.
• Math uses backticks and parentheses; path and measure are explicit; no Chinese appears.
• Units/dimensions pass check_dim; if T_arr appears, delta_form/path/measure are registered.
• Keys use snake_case; reserved names are not repurposed; see[] and export_manifest.references[] use the fixed format.