47-PTN Template v1.0 | Chapter 0 — Preface & Reader’s Guide

Home ／ Docs-Technical WhitePaper ／ 47-PTN Template v1.0

Chapter 0 — Preface & Reader’s Guide

I. Abstract
This chapter states the purpose, intended readership, and usage of the PTN Template, and sets the mandatory conventions for citations, symbols, and math expressions. All cross-references must use “volume name + version + anchor (P/S/M/I)”. Inline symbols are wrapped in backticks; any expression with division, integrals, or composite operators must use parentheses and explicitly declare the path gamma(ell) and measure d ell.

II. Scope

• Audience: Authors, reviewers, release owners, and reproducibility leads working with Particle Technical Notes (PTN).
• Coverage: Standardized authoring for abstract & scope, control equations and minimal assumptions, testable predictions and falsification, data & pipeline contracts, implementation bindings, result presentation, and limitations.
• Dependency (citation format): Always cite as See "<Volume> vX.Y" <Chapter> <Anchor>, prioritizing P/S/M/I anchors. Example: See "EFT.WP.Core.Equations v1.1" Ch.2 S20-1.
• Out of scope: Domain-specific derivations and engineering details (covered in later chapters or companion volumes).
• Style & layout: Section headings use Roman numerals in bold; bullet lists use “- space”; ordered lists use “1. space”; do not use Chinese characters in formulas, symbols, or definitions.

III. Version & Stability Line

• Versioned citations: Every citation must include an explicit version (e.g., EFT.WP.Core.Tension v1.0); aliases and short codes are forbidden.
• Stability policy: Public releases reference only v1.*. If a v0.* draft must be cited, mark it explicitly as “draft / non-committal” in the text.
• Numbering system: Axioms Pxx-?, minimal equations Sxx-?, metrology workflows Mx-?, implementation bindings Ixx-?; used consistently across the book.

IV. Quick Start

1. Arrival-time, two equivalent forms (path and measure required):
   • Constant factored out: T_arr = ( 1 / c_ref ) * ( ∫ n_eff d ell )
   • General form: T_arr = ( ∫ ( n_eff / c_ref ) d ell )
     Requirements: Record delta_form in text or data metadata, and attach machine-readable references:
2. see:
3. - "EFT.WP.Core.Equations v1.1:S20-1"
4. - "EFT.WP.Core.Metrology v1.0:check_dim"
5. - "EFT.WP.Core.DataSpec v1.0:TARR"
6. Inline symbols & conflict names: Use T_fil (tension), T_trans (transmittance), n_eff (effective refractive index), c_ref (reference propagation limit); never use bare c, T, or n. Do not mix T_fil with T_trans, or n with n_eff.
7. Fixed in-text citation style:
   • Equations/definitions: See "EFT.WP.Core.Density v1.0" S92-1; See "EFT.WP.Core.Tension v1.0" S72-9.
   • Narrative terms: See "EFT.WP.Core.Terms v1.0" P10-3.
     Use as style exemplars; choose concrete anchors per actual usage.
8. Export manifest (machine-readable): Any PTN-related data/pipeline export must include references: [...] and version: fields to support automated linting and reproducibility.

V. References & Cross-References

• Unified style & layout: See EFT Technical Whitepaper & Tech Memo Templates — Complete Checklist v0.1.
• Citation & cross-reference rules: See EFT Citation & Cross-Reference Specification v0.1.

Deliverables of this Chapter

• Fixed “Reader’s Guide” page (for publication).
• Minimal terms/symbols alignment sheet (with see: pointers and unit/dimension checks).