55-Decision & Change Log Template v1.0 | Chapter 2 Terminology & Role Model

Home ／ Docs-Technical WhitePaper ／ 55-Decision & Change Log Template v1.0

Chapter 2 Terminology & Role Model

I. Terminology Domain & Citation Convention (Mandatory)

• This chapter follows the unified terminology/symbol policy. Cross-volume citations use the fixed format: “See 《EFT.WP.Core.Terms v1.0》 P10-; 《EFT.WP.Core.Equations v1.1》 Ch.x Sxx-; 《EFT.WP.Core.Metrology v1.0》 Ch.x Mx-; 《EFT.WP.Core.DataSpec v1.0》 Ixx-.”
• Inline symbols are always wrapped in backticks. Any expression with division, integrals, or composite operators must use parentheses, and the first occurrence must explicitly give path gamma(ell) and measure d ell.

II. Unified Symbols & Definitions (Mandatory)

1. Base quantities & objects
   • phi(x,t): scalar field or potential (disambiguate via Terms P10-* as needed).
   • Xi(x,t): tensor field or structural tensor (dimension/unit per Metrology).
   • K, Q: generic quantities (define at first use with a Terms anchor).
2. Arrival time & path
   • T_arr: arrival time; unified formulations:
     • Constant factored out: T_arr = ( 1 / c_ref ) * ( ∫ n_eff d ell )
     • General form: T_arr = ( ∫ ( n_eff / c_ref ) d ell )
   • gamma(ell): integration path; d ell: path measure. When T_arr appears, the same or adjacent paragraph must provide gamma(ell) and d ell or cite their anchors.
3. Refraction & tension-related quantities
   • c_ref: reference propagation limit; n_eff: effective refractive index.
   • T_fil: tension (mechanical/material meaning); T_trans: transmittance (ratio/transport meaning).
4. Prohibited mixes & prohibitions
   • Do not mix: T_fil vs T_trans; n vs n_eff; c vs c_ref.
   • No Chinese in formulas, symbols, or definitions; parameters/units must pass check_dim.

III. Disambiguation & Naming Rules (Mandatory)

• For the first occurrence of any symbol, provide the minimal reproducible definition: name, unit, dimension, default prior, and valid range.
• Use a three-part “object—attribute—caliber” naming pattern:
  Examples: n_eff.medium=intergalactic, c_ref.band=L2, T_fil.regime=linear.
• Reserved prefixes: ref_ (reference caliber), cal_ (calibration), gate_ (gating/threshold), delta_ (caliber delta).

IV. Role Model (Mandatory)

• Requester: creates the DR; submits motive, alternatives, and evidence.
• Reviewer: examines evidence, caliber consistency, and impact surface.
• Approver/Owner: renders the decision; signs scope and exceptions.
• Implementer: executes the plan; submits verification and regression results.
• Auditor: checks references/versions/anchors, dimensional checks, gates, and rollback closure.
• Observer (optional): subscribes to progress; no signature authority.

V. RACI Responsibility Matrix (Mandatory)

• Events: propose, review, decide, implement, verify, rollback, archive.
• Matrix (copy directly into the document):

Legend: R Responsible, A Accountable (final sign), C Consulted, I Informed. “/A” denotes final sign responsibility on that event.

VI. Communication Path & Signature Chain (Mandatory)

• Communication path: Requester ⇄ Reviewer ⇄ Approver/Owner ⇄ Implementer ⇄ Auditor.
• Signature chain: state-machine driven (Draft → Review → Approved → Implemented → Verified → Archived; → RolledBack is a controlled branch). Entry/exit conditions are defined per DR with gate_* metrics.

VII. Citation & Cross-Reference Rules (Mandatory)

• Fixed in-text format: “See 《 vX.Y》 Ch.x S/P/M/I…”, preferring anchors over whole volumes.
• Machine-readable references live in the DR’s references.see list, e.g.
• references:
• see:
• - "EFT.WP.Core.Terms v1.0:P10-3"
• - "EFT.WP.Core.Equations v1.1:S20-1"
• - "EFT.WP.Core.Metrology v1.0:check_dim"
• - "EFT.WP.Core.DataSpec v1.0:I30-2"
• Every EFT.WP.* citation must include an explicit version; public releases should prefer the stable v1.* line.

VIII. Dimensional & Unit Consistency (Mandatory)

• In DR implementation/verification, provide for formulas/parameters: unit, dim (dimension vector/tag), uncertainty, and check_dim=true.
• For conversions/calibrations, provide cal_source, traceability, and effective_range.

IX. Fault Tolerance & Rollback Conventions (Mandatory)

• Monitoring metrics and thresholds (e.g., gate_latency, gate_accuracy);
• Triggers (explicit thresholds and observation window);
• Rollback steps (operational sequence, recovery criteria, observation points);
• Re-deployment conditions (gates required for a second rollout).

X. Machine-Readable Roles/Signature Schema (Directly Reusable)

roles:

requester: {name:"", org:"", email:"", responsibilities:["initiate","evidence_pack","impact_outline"] }

reviewer: {name:"", org:"", email:"", responsibilities:["review_evidence","consistency_check","risk_note"] }

approver: {name:"", org:"", email:"", responsibilities:["decision","scope_define","exceptions"] }

implementer:{name:"", org:"", email:"", responsibilities:["execute_plan","deliver_verification","regression"] }

auditor: {name:"", org:"", email:"", responsibilities:["reference_check","dimensional_check","gate_signoff","archive"] }

observer: {name:"", org:"", email:"", responsibilities:["subscribe"] }

sign_chain:

states: ["Draft","Review","Approved","Implemented","Verified","Archived","RolledBack"]

transitions:

- {from:"Draft", to:"Review", gate:["completeness_check","see_refs_present"] }

- {from:"Review", to:"Approved", gate:["risk_accepted","consistency_ok"] }

- {from:"Approved", to:"Implemented", gate:["plan_ready","resources_locked"] }

- {from:"Implemented", to:"Verified", gate:["verification_pass","regression_ok"] }

- {from:"Verified", to:"Archived", gate:["audit_ok","export_artifacts"] }

- {from:"Implemented", to:"RolledBack", gate:["trigger_threshold","rollback_plan_ready"] }

XI. Example Inline Usage (Copy-Ready)

• First-use terminology: See 《EFT.WP.Core.Terms v1.0》 P10-3.
• Arrival-time criterion: See 《EFT.WP.Core.Equations v1.1》 Ch.2 S20-1; T_arr = ( ∫ ( n_eff / c_ref ) d ell ), with gamma(ell) and d ell declared in the same paragraph.
• Dimensional check: See 《EFT.WP.Core.Metrology v1.0》 Ch.1–3, check_dim.
• Data contracts: See 《EFT.WP.Core.DataSpec v1.0》 I30-*.