APPENDIX - Fringe Spacing Geometry Module¶

Purpose: Convert the “interferometry grid / invisible tripod” idea into a quantitative, falsifiable geometry claim. This module does not identify an emitter; it states what the geometry must match.

Outputs: (1) fringe spacing as a function of crossing angle and wavelength, (2) geometry-derived frequency cases for declared feature-to-fringe assignments, (3) explicit assumptions and falsifiers, and (4) the public status of the stronger map-level test.

Status: This appendix carries two model-conditional geometry results: band placement from the ENE / East-Northeast ↔ Erin-sector crossing angle and fringe orientation from the ENE↔Erin-sector bisector. The companion spatial audit tests the stronger claim that a computed fringe map fits the source-identified feature set better than its governing spatial null. Band placement, orientation, and map-level recurrence remain separate claims.

0. Definitions¶

• Crossing angle (\(\theta\)): the angle between the two incoming wave vectors at the target region (equivalently, the angle between the two arrival-direction proxies as seen from the target, under a plane-wave approximation).
• ENE directional proxy: a bookkeeping label for the east-northeast arrival sector at the WTC used by the reconstruction’s geometry (bearing ~79.3° from true north). Site attribution is separate from this geometry result.
• Erin-sector proxy: a bookkeeping label for the reconstruction’s carried Erin-associated Atlantic/SSE arrival sector at the WTC. Its declared nominal reference bearing is ~149.7° from true north. Erin supplies a persistent offshore refractivity/path sector.
• Wavelength (\(\lambda\)): the carrier wavelength of the two phase-related arrival components. Given the declared feature-to-fringe assignments, the crossing angle derives frequency cases spanning ~2.6–10 MHz.
• Fringe spacing (\(d\)): spacing between adjacent maxima (or minima) in the interference pattern in the plane normal to the bisector direction.

1. Fringe spacing for two coherent plane waves¶

For two equal-frequency plane waves with crossing angle \(\theta\), the interference fringe spacing is:

Equivalently:

Implication: once \(\theta\) is fixed, the geometry fixes the ratio \(d/\lambda\).

2. Example ratio for the ENE↔Erin-sector crossing angle (~70.4°, from geodetic bearings)¶

If \(\theta \approx 70.4^\circ\), then:

So, under this assumption:

Important: The crossing angle \(\theta \approx 70.4°\) is derived from geodetic bearings (ENE proxy at 79.3° and Erin-sector proxy at 149.7° from the WTC; difference = 70.4°). The 149.7° input is the bearing from the WTC to the declared offshore proxy point. It defines the Erin-sector arrival-direction proxy used in the geometry; it is not Erin's storm-center bearing or a source attribution. The bearing sweep below shows how the geometric result changes when that proxy is varied.

3. Model-conditional derivation: “What frequency follows if feature scale \(d\) is a fringe interval?”¶

Given an observed feature scale \(d_{feature}\) and a chosen \(\theta\), solve for:

Convert to frequency using a phase velocity \(v_{ph}\) (do not silently assume \(c\) if your propagation model implies otherwise):

3.1 First-order table (\(\theta=70.4^\circ\) from ENE↔Erin-sector bearings; \(v_{ph}=c\) as free-space assumption)¶

With \(d \approx 0.866\,\lambda \Rightarrow \lambda \approx d/0.866\):

“Fringes” across a 100 m scale	Implied fringe spacing \(d\)	Implied \(\lambda\)	\(f\) (if \(v_{ph}=c\))
0.5 fringe	200 m	231 m	1.30 MHz
1 fringe	100 m	115 m	2.60 MHz
1.5 fringes	67 m	77 m	3.90 MHz
2 fringes	50 m	58 m	5.20 MHz
3 fringes	33 m	38 m	7.81 MHz

Interpretation: Once the feature-to-fringe assignment, \(\theta\), and \(v_{ph}\) are declared, the corresponding frequency is mathematically determined rather than freely selected. Interpreting a derived case as an identified operating frequency still requires independent support that the selected dimension represents the assigned fringe interval and that the stated propagation model applies.

3.2 Geometry-derived frequency cases for the declared feature assignments¶

If one treats certain feature scales as candidate “boundary spacings” (e.g., ~100 m knife-edge boundary scale, ~63 m tower face width, ~25 m WTC 6 principal sub-aperture / WTC 3 bisection features), then the reverse-calculation produces the following frequencies:

Frequency (if \(v_{ph}=c\))	Fringe spacing \(d\)	Candidate feature scale
2.6 MHz	100 m	WTC 4 boundary-scale spacing (1 fringe across 100 m)
4.1 MHz	63.5 m	Tower face width (~63 m)
5.2 MHz	50 m	“2 fringe” boundary-scale spacing across 100 m
10.0 MHz	26 m	WTC 6 principal dark-core / sub-aperture lateral scale and WTC 3 bisection-scale features (~25-26 m)

Interpretive status: The table is a model-conditional geometric derivation, not a free frequency guess. It narrows the frequency cases implied by the declared feature assignments; identifying an event-time operating frequency or a complete spatial map requires separate support.

4. Sensitivity and evaluation workflow¶

Because \(d/\lambda = 1/(2\sin(\theta/2))\), changes in \(\theta\) shift the inferred \(\lambda\) and therefore the inferred \(f\).

Workflow note: angle-sensitivity sweeps and full reporting of derived-band variation are routed to the companion spatial-analysis bundle built on top of this geometry module.

4.1 Computed sensitivity: ±5° in \(\theta\) (65°–75°)¶

Using \(v_{ph} = c\) and the four candidate feature scales from Section 3.2:

Feature scale	\(\theta=65°\)	\(\theta=68°\)	\(\theta=70.4°\) (central)	\(\theta=72°\)	\(\theta=75°\)	Spread
WTC 4 boundary (~100 m)	2.79 MHz	2.68 MHz	2.60 MHz	2.55 MHz	2.46 MHz	±6.3%
Tower face width (~63 m)	4.43 MHz	4.26 MHz	4.13 MHz	4.05 MHz	3.91 MHz	±6.3%
2-fringe / WTC 6 sub-aperture scale 2× (~50 m)	5.58 MHz	5.36 MHz	5.20 MHz	5.10 MHz	4.93 MHz	±6.3%
WTC 6 principal sub-aperture / WTC 3 strip (~26 m)	10.74 MHz	10.32 MHz	10.01 MHz	9.82 MHz	9.48 MHz	±6.3%

Key observations:

1. Low sensitivity: ±5° in \(\theta\) shifts all implied frequencies by only ±6.3%. The multi-feature alignment is not a fine-tuned result — it survives substantial angle uncertainty.
2. Referenced HF-class overlap check: At the angle extremes, the 100 m feature drops just below 2.8 MHz (at \(\theta=75°\): 2.46 MHz) and the ~26 m feature scale just grazes above 10 MHz (at \(\theta=65°\): 10.74 MHz). The middle two features (63 m and 50 m) remain solidly in-band regardless of angle choice.
3. Implication for the dossier: the geometry is not a knife-edge construction; its sensitivity is evaluated across the declared bearing range.

5. Assumptions (must be stated)¶

This module requires explicit assumptions, but they do not all govern the same claim level.

• Baseline geometry-bookkeeping layer: arrival-direction proxies, crossing angle, bisector orientation, and model-conditional band placement under stated propagation assumptions.
• Stronger quantitative fringe-map layer: phase-related arrival components, path dominance, valid local crossing-angle mapping, and a threshold model under which damage boundaries can plausibly track fringe intensity.

If the stronger layer fails, the strongest quantitative fringe-map explanation fails even if weaker band-placement or orientation constraints remain as conditional geometry observations.

1. Coherence: the two arrival components are sufficiently phase-related over the relevant interval to produce an interference structure.
2. Path dominance: other paths or fields do not wash out the pattern or dominate coupling.
3. Propagation model: the mapping from source vectors to a local crossing angle at ground/structure scale is valid (waveguide / refraction / multipath must be bounded).
4. Coupling threshold model: “damage boundaries” correspond to crossing a coupling threshold that can plausibly track a fringe intensity gradient.

6. Falsification protocol (minimal)¶

1. Lock inputs: specify source coordinates/timing and compute \(\theta\) from the stated geometry.
2. Pick a band: select candidate frequencies from the reverse-calculation for evaluation.
3. Compute a map: generate a fringe/node intensity map across the WTC complex (with stated approximations).
4. Define “match”: declare what constitutes a match before running the test (e.g., boundary alignment within X meters across Y source-identified features).
5. Fail fast: if the predicted map does not correlate with the damage boundary features beyond chance, reject the quantitative claim that the fringe map explains boundary placement. Band placement and orientation are evaluated under their own stated assumptions and tests.

7. Where this is referenced¶

• White Paper: prediction-facing summary and test protocol (to avoid burying falsifiability in appendices).
• Bridge Mechanism Physics Appendix, Section J: carries the associated physical and collateral constraints.
• Companion spatial audit: reports the map-level recurrence and sensitivity tests referenced here.

8. Notes on band statements (avoid overclaim)¶

The geometry-derived frequency range (2.6–10 MHz) overlaps with a known 2.8–10 MHz high-power HF operating class (see also Bridge Appendix, Section I for facility-scale parameters). That overlap is a capability-consistency result, not source attribution:

• The geometry module can at most constrain "if interference geometry explains boundary placement, then candidate \(f\) lives near 2.6–10 MHz under stated propagation assumptions and crossing angle."
• Whether any real-world HF facility (HAARP or otherwise) can supply the required power-at-target, coherence, and collateral containment is a separate link-budget and feasibility question handled elsewhere (see Bridge Appendix, Section J).

8.1 Interpretive note: the band-placement finding¶

The finding¶

The ENE↔Erin-sector crossing angle (\(\theta \approx 70.4°\)) places the four geometry-derived frequency cases at 2.6–10 MHz — overlapping a known high-power HF operating class (2.8–10 MHz) very closely:

Frequency	Fringe spacing \(d\)	Feature matched
~2.6 MHz	~100 m	WTC 4 damage boundary scale (knife-edge at ~⅔ of building length)
~4.1 MHz	~63 m	Tower face width (63 m square cross-section)
~5.2 MHz	~50 m	WTC 4 boundary at 2-fringe spacing; WTC 6 principal sub-aperture scale at 2×
~10 MHz	~26 m	WTC 6 principal dark-core / sub-aperture lateral scale (~25-30 m); WTC 3 bisection strip width (~25 m)

The feature scales span a 3.85× bandwidth ratio (100 m / 26 m). The referenced HF operating class spans a 3.57× ratio (10 MHz / 2.8 MHz). These match to within 8% — close enough that the feature cluster overlaps that HF class with only slight overflow at both edges (2.60 MHz just below 2.8; 10.01 MHz just at 10.0).

How the crossing angle controls band placement¶

The fringe equation (\(f = c / 2d\sin(\theta/2)\)) means the crossing angle acts as a tuning knob — it slides the entire feature cluster up or down the frequency axis without changing its bandwidth:

Crossing angle \(\theta\)	\(f\)(100 m)	\(f\)(26 m)	Cluster lands at
40°	4.38 MHz	16.85 MHz	above the referenced HF class
70.4° (ENE↔Erin-sector)	2.60 MHz	10.01 MHz	overlaps the referenced HF class
120°	1.73 MHz	6.66 MHz	below the referenced HF class

The ENE↔Erin-sector angle places the cluster in a close-fit position, with nearly symmetric overflow around the referenced HF class.

Methodological precision: what the null does and does not test¶

The fringe equation has an important property: for any two feature scales \(d_1\) and \(d_2\), their frequency ratio is \(f_1/f_2 = d_2/d_1\), which is independent of \(\theta\). This means:

• What this appendix does not carry as evidence by itself: any crossing angle preserves the same inter-feature frequency ratios, so the mere existence of a four-scale cluster is not the carried claim. Random-angle screening is used as a methodological guardrail for exactly that reason: it prevents the scale cluster alone from doing argumentative work it cannot carry.
• What this appendix does carry as the non-trivial geometry claim: where on the frequency axis the cluster lands, whether the ENE↔Erin-sector angle places it in the referenced HF class, whether the geometrically distinct bisector/orientation relation is simultaneously satisfied, and whether a declared fringe/node audit fits observed boundaries better than its governing null.

The null question (stated precisely)¶

The proper null question is: "Given the observed building dimensions in the WTC complex, how likely is it that their max/min scale ratio (\(\approx 3.85\times\)) approximates the bandwidth ratio of a referenced HF operational class (\(\approx 3.57\times\)) to within 8%?" This depends on the distribution of building dimensions and the number of candidate transmitter windows in the RF spectrum. That probability is routed to the companion spatial-analysis bundle rather than left implicit.

Bottom line¶

The carried test has three claim units: ENE↔Erin band placement, the geometrically distinct bisector/orientation relation, and the computed fringe map evaluated against its governing spatial null. The map-level test governs the quantitative explanation of boundary placement; band placement and orientation retain their own assumptions and evaluation criteria.

8.2 Fringe-orientation derivation — no phase or frequency fitted¶

The finding¶

The fringe node lines run parallel to the bisector of the two arrival-direction proxies — at 114.5° from true north (roughly ESE–WNW). The WTC complex was rotated approximately 29° east of true north, so the buildings' "east-west" faces run at 119° from north.

The offset is 4.5°.

This means fringe node lines are nearly parallel to the buildings' E-W faces. Damage boundaries within individual buildings would appear as strips or divisions running roughly E-W — dividing buildings into north and south portions. This matches the FEMA 403 observations:

• WTC 4: knife-edge boundary dividing the south wing (destroyed) from the north wing (intact) — consistent with a node line running parallel to the E-W building axis.
• WTC 3 (Marriott): bisection strip running roughly along the E-W building axis — consistent with a node line passing through the building in the same direction.
• WTC 6: scalloped vertical void / aperture complex — no preferred orientation at the feature-scale level (consistent with any fringe direction).

What this depends on¶

The 114.5° bisector follows directly from the specified arrival-direction proxies. No phase or frequency is fitted in this orientation calculation. It depends on:

1. ENE proxy bearing from WTC: 79.3° (geodetically determined)
2. Erin-sector proxy bearing from WTC: 149.7° (the bearing to the declared offshore proxy point; carried as a declared nominal reference bearing and assessed across the ~140°–160° sector sweep)
3. WTC complex rotation: ~29° from true north (from site plans / NIST NCSTAR 1)

It does not depend on: phase offset (φ₀), exact building coordinates, frequency choice, or any fitting or optimization.

Geometric alignment note¶

The public result carried here is the reproduced 4.5° offset. No standalone orientation p-value is assigned: its statistical weight depends on whether one architectural axis or either orthogonal axis was declared in advance, as well as source-pair and comparison accounting. Those choices belong to the governing spatial-audit protocol.

Sensitivity to the Erin-sector proxy bearing¶

The orientation match holds to within 10° for Erin-sector proxy bearings from ~140° to ~160° (a ±10° range). The tightest observed match, 4.5°, occurs near the 149.7° proxy bearing.

Why this is a second geometrically distinct relation¶

The band-placement finding (§8.1) depends on the crossing angle (Erin-sector proxy bearing − ENE proxy bearing = 70.4°). The orientation finding depends on the bisector angle ((Erin-sector proxy bearing + ENE proxy bearing) / 2 = 114.5°). They are algebraically distinct—the difference and sum of the two bearings—but that distinction is not, by itself, proof of statistical independence. Both relations can therefore be reported affirmatively without multiplying their probabilities.

8.3 Statistical status¶

The orientation and band-placement relations are reproduced geometric results. Their joint statistical weight is not assigned here because the governing null, axis-selection rule, feature-selection accounting, and spatial metric remain part of the companion audit.

8.3.1 Orientation finding null model¶

Evaluation baseline: The bisector direction of the two specified arrival-direction proxies is evaluated against the architectural axes of the WTC complex.

Local reference only: If a match to either of two orthogonal architectural axes is allowed, a uniform undirected-orientation reference gives a 10% chance of landing within 4.5° of either axis. A 5% value applies only if one specific axis was declared in advance. Neither value is presented as final significance.

What the tolerance \(\delta\) means: The 4.5° value is the observed offset between the bisector (114.5°) and the nearest building face axis (119°). That observed offset is the orientation-match quantity to be scored.

Evaluation handling: The orientation test is treated as a single bisector-versus-building-face comparison. Source-pair handling, feature-set handling, and any broader multiple-comparison accounting are reported by the companion spatial audit.

8.3.2 Band-placement null model¶

The public result is the model-conditional placement of the declared feature scales in the 2.6–10 MHz range and its overlap with the referenced operating class. Statistical weight depends on feature-selection and comparison-class accounting and is not assigned here.

8.3.3 Joint statistical treatment¶

No joint p-value is assigned. The crossing angle and bisector are algebraically distinct functions of the same two arrival-direction proxies, and the band result also consumes selected feature scales. Their probabilities therefore cannot be multiplied without a governing joint null that accounts for those shared selections.

8.4 Registration status¶

This module does not assign an event-time operating frequency or claim a complete propagation solution. The 10 MHz value is one conditional case produced by the declared feature mapping, not a measured carrier. Band placement and bisector orientation are Narrowed; stronger fine-registration claims remain Data-limited.

8.5 Spatial-audit result and status¶

The current coordinate package contains nine primary points—five vehicle loci and four structural loci—and four geometry-derived frequency cases. Phase is optimized separately within each case under the declared d/4 proximity criterion.

The executable audit reproduces:

• Per-case hits: 7/9, 8/9, 8/9, and 7/9 at 2.6, 4.1, 5.2, and 10.0 MHz.
• Cross-case total: 30/36.
• Recurrence: all 9 primary points hit at least three cases; 3/9 hit all four.
• WTC 7: 3/4 under phases fitted only on the primary nine-point set.

The phase-optimized counts are reproducible, but the structural points also participate in defining the frequency cases. Their recurrence is therefore an internal-consistency result rather than an independent spatial test. WTC 7 remains a secondary phase-held-out consistency check.

The companion audit now fits phase on the structural set and scores the five vehicle points separately; all five hit at least three cases under the fixed coordinates, and the result is stronger than the four implemented sensitivity nulls. Because that design follows exploratory inspection and is sensitive to the current coordinate-jitter assumptions, it remains an internal narrowing result rather than map-level confirmation. Coordinate uncertainties and broader selection accounting are not yet fully bounded.

Current status: band placement and orientation are Narrowed. Fixed-coordinate recurrence is Narrowed within the declared protocol; stronger coordinate-robust and fine-registration claims remain Data-limited.

9. How this connects to the feasibility choke points¶

This module most directly constrains:

• Emitter spec (geometry-constrained): geometry-derived frequency cases under the declared feature and propagation assumptions.
• Control/coherence: if boundaries are sharp, coherence/stability requirements must be consistent with propagation variability.
• Collateral containment: a computed node map must explain why adjacent structures sit in “safe zones” (anti-nodes) rather than being indiscriminately exposed.

By design, this module does not settle facility identity or bridge physics. It is a falsifiable geometry test, not a standalone replacement for the rest of the reconstruction.