constConfigPhase
plain-language theorem explainer
Constant phase-space point on the two-slot hypersurface: configuration and momentum are the constant maps with values q and p. Used when killing strong HKT rigidity, so the gradient term drops and the balanced quartic reduces to a pure momentum identity. Construction is the pair of constant functions into PhaseSpace 2.
Claim. For real numbers $q,p$, the constant configuration phase point is the element of two-slot phase space whose configuration field is the constant map $x\mapsto q$ and whose momentum field is the constant map $x\mapsto p$.
background
Module Wave C2 gap5 targets the strong point-split HKT rigidity claim and a repaired CanonicalMom class (binding design D-qg-hkt-rigidity-route-20260722). Session A inhabits the strong dynamical target at $N=2$ by a balanced quartic falsifier and proves the strong rigidity statement false; no ledger flag is flipped.
Phase space here is the two-component object (configuration field, momentum field) on the hypersurface deformation setup. A constant configuration means every spatial slot carries the same $q$ and the same $p$, so spatial gradients vanish identically.
Upstream ledger and balance notions (balanced event lists, signed-orbit balance) sit behind the balanced quartic densities used as the falsifying target; this definition only packages the evaluation point those densities are read at.
proof idea
Definitional one-liner: return the pair of constant functions (fun _ => q, fun _ => p) as an element of PhaseSpace 2. No lemmas or tactics.
why it matters
Feeds not_HKTRigidityStatementPointSplitDynN2Strong, the theorem that strong-class rigidity fails. That proof applies the strong rigidity hypothesis to the balanced quartic target, then evaluates the forced form at constant configuration (gradient term vanishes) and three momenta, obtaining $p^4 = c_{\mathrm{Kin}} p^2 + c_{\mathrm{Vac}}$ at three values and a contradiction.
In the gap5 program this is the evaluation probe that separates the strong (over-rigid) class from the repaired CanonicalMom class banked as DEFINED-only for later sessions. It is scaffolding for the rigidity kill, not a physics law claim; the eight-tick and $D=3$ forcing chain are not invoked here.
Switch to Lean above to see the machine-checked source, dependencies, and usage graph.