Moving-Throat PDE Derivation Companion Archive Ledger

Norris, Trevor

doi:10.5281/zenodo.19699523

◇ part II · applications

A framework paper for $R(\Omega,w,t)$ , not a solved nonlinear throat theorem

The current moving-throat paper is explicit about its status. It lifts the old collective variables $(a,L)$ to a distributed moving surface, writes a linearized coupled wall/support/gauge problem, and isolates the observables any realized branch must compute. It does not claim a completed first-principles solution of the full nonlinear moving-throat PDE or a finished proof that the canonical passive/outgoing branch has already been realized.

Geometry lift as confinement argumentLinearized wall/support/gauge systemBranch realization4D · Action 4D · Maxwell Prior · throat ontology

◇ geometry lift

The first framework move is to represent the throat as a moving surface

The framework paper's starting point is the geometry lift

◇ geometry lift · confinement argument

The old collective variables

a(t)

and

L(t)

survive only as collective moments of this distributed open interface.

\Sigma(\mathbf X,t) \;=\; r - R(\Omega,w,t)

As a confinement argument,

\Sigma/R

belongs to the exact matter-sector bookkeeping. As an autonomous dynamical wall field, it remains an effective closure unless a throat action

S_\Sigma

is promoted into the parent action. The branch geometry used for realization tests is also open:

R_0(0)=a_0

and

R_0(L_0)>0

, not a hard cap.

◇ what the paper actually fixes

The paper fixes a linearized coupled response language and the branch data it needs

The moving-throat framework is best read as a map from a candidate stationary branch to the reduced data needed for later PN and anomaly tests:

◇ branch data set · operational input

These are frozen branch data, not fit knobs. The paper is explicit that they are not yet supplied by a solved nonlinear theorem.

\begin{aligned} \mathfrak B \;=\; \big\{\ &\text{parent-action status},\ R_0,\ R_{\rm exit}>0, \\ &\text{wall/material data},\ \text{support spectrum}, \\ &\text{mixed/outgoing ports},\ \text{source normalization}\ \big\} \end{aligned}

The framework then organizes those data into conservative operator moments, outgoing-transfer moments, and grouped isotropy diagnostics.

◇ operational outputs

The first two observables are the isotropic normalization test and the weak-axisymmetric slope

◇ first framework outputs

These are the reader-facing observables singled out by the PDE program, in the stated source/port convention.

\hat m_0^{\,2} P_0 \;=\; \frac{54Gc_s^5}{5a^5c^5}, \qquad \Xi_1 \;=\; P_1/P_0

On the isotropic branch, the first quantity is the outgoing quadrupole-normalization target. Around that branch,

\Xi_1

is the first weak-axisymmetric observable. That is the current paper's precise meaning of “what the PDE must compute”.

◇ non-claims

What the current paper explicitly refuses to claim

No complete first-principles solution of the nonlinear moving-throat PDE.
No autonomous parent-level wall PDE unless $S_\Sigma$ is promoted and frozen.
No proof that the passive/outgoing quadrupole branch is already realized on the true defect solution.
No post-residual tuning of wall, material, source, or outgoing coefficients.
No finished ring-down catalogue that can simply be compared to LIGO/LISA data today.

◇ downstream use

Why this still gates so much

Once a real target-blind branch returns the frozen data in

\mathfrak B

, the same output bundle feeds the 2.5PN / 4PN normalization question, the anomaly package, and the mixed-sector finite-profile corrections elsewhere on the site. A stable branch can pass or fail those residuals; it is not repaired after the comparison.

← previous10 · The Post-Newtonian Ledger next →12 · What This Is Not