Pith. sign in
module module moderate

IndisputableMonolith.Verification.RecognitionStabilityAudit.BackEnd

show as:
view Lean formalization →

Back-end half of the Recognition Stability Audit: a holomorphic Schur-bounded map Ξ on a preconnected open set Ω that hits the unit-circle boundary must be identically 1. Analysts citing RSA use this as the maximum-modulus pinch that kills nontrivial boundary contact. The module packages four lemmas that reduce boundary hits to constancy via classical complex analysis.

claimIf $\Xi$ is holomorphic and Schur-bounded ($|\Xi|\le 1$) on a preconnected open region $\Omega\subset\mathbb{C}$, and $\Xi$ attains modulus $1$ at any interior point, then $\Xi\equiv 1$ on $\Omega$. Equivalently: a nontrivial such $\Xi$ never hits the boundary of the unit disk.

background

The Recognition Stability Audit (RSA), formalized in the Core interface and the companion paper Recognition_Stability_Audit.tex, treats stability of recognition maps as a compiler from analytic hypotheses to rigidity conclusions. Core supplies the RL-friendly vocabulary (Schur bound, boundary hit, preconnected open sets); this BackEnd module is the analytic engine behind that interface.

Schur-bounded means $|\Xi|\le 1$ on $\Omega$. A boundary hit is an interior point where $|\Xi|=1$. Preconnectedness of $\Omega$ is the connectedness hypothesis that lets the identity theorem and maximum-modulus principle globalize a local constancy statement. The classical fact in play is: a holomorphic function into the closed unit disk that touches the circle inside a connected open set is constant.

Upstream Core only declares the interface; the actual pinch lives here so that the umbrella RSA module can re-export a single import path without exposing the complex-analysis scaffolding.

proof idea

Four sibling lemmas form a short chain. First, a boundary hit forces the value at that point to have modulus one (and, under the Schur normalization used here, value exactly 1). Second, maximum modulus plus identity on a preconnected domain upgrades that pointwise hit to $\Xi\equiv 1$ everywhere on $\Omega$. Third, the contrapositive: a Schur-holomorphic nontrivial map has no boundary hit. Fourth, the packaged back-end statement: Schur-holomorphic and nontrivial implies the back-end audit predicate (no pinch failure). The argument is standard one-variable complex analysis; Lean only has to wire the hypotheses to Mathlib's maximum-modulus and identity theorems.

why it matters in Recognition Science

RSA splits into front-end bookkeeping and this back-end pinch. Downstream, the umbrella module RecognitionStabilityAudit re-exports Core and depends on BackEnd so consumers can import IndisputableMonolith.Verification.RecognitionStabilityAudit and obtain the full audit. Without the pinch, a Schur-bounded recognition map could graze the unit circle without being forced to the constant-1 fixed point that RSA treats as the stable attractor.

In the broader Recognition framework the constant-1 conclusion is the analytic counterpart of a rigidity step: once the map is pinned to 1 on a connected open set, discrete ladder and forcing-chain constraints (phi self-similarity, eight-tick structure) inherit a unique stable background rather than a continuum of near-boundary deformations. The module does not itself invoke T5–T8; it supplies the complex-analytic lemma those discrete arguments rely on when they pass through RSA.

scope and limits

used by (1)

From the project-wide theorem graph. These declarations reference this one in their body.

depends on (1)

Lean names referenced from this declaration's body.

declarations in this module (4)