Principia Orthogona  ·  Book 6  ·  Working Papers · Series Notes & Applications
WP-14 EMMEs WP-25 No-Go-as-a-Service Ch DE-1 The Cosmic No-Go
GET /nogo?limit=−2  →  deSitter_possible: false
the theorem, called like a function

No-Go-as-a-Service

the contact no-go theorem's parameter, served behind an API — product spec and working prototype

Book 6's job, per its own charter, is finding uses and turning ideas into products. The Cosmic No-Go chapter (Ch DE-1) proves something with a genuinely portable shape: given a system's transverse stability rate, a locked identity (c = H′) forces a hard exclusion on what the system's expansion behavior can do. That shape — feed in a measured rate, get back a hard yes/no on what's excluded — is exactly the shape of a useful API call. This working paper is both the product spec and a working prototype of it.

What actually ships

Four endpoints, each a thin numeric wrapper around a specific theorem in HelixToyModel.lean, not a black box:

RouteBacking theoremReturns
/trichotomy?z=neutral_line_trichotomy — fully proved, no sorryrepelling / neutral / attracting classification
/epsilon?eps0=&z0=&t=epsSol — closed form (issue #H1)the transverse deviation ε(t)
/lyapunov?eps0=&z0=&t=lyapunov_exponent_eq — issue #H2numerical Lyapunov rate, converging to −2
/nogo?limit=nogo_attractor_not_deSitter + attractor_excludes_deSitter — issue #H3/#H3bwhether a claimed transverse-rate limit excludes any positive finite (de Sitter) expansion rate
Verified this session (Flask test client, no server round-trip skipped): /trichotomy?z=1.5 -> transRate=-1.5537... classification=attracting /trichotomy?z=-1.5 -> transRate=+6.9634... classification=repelling /trichotomy?z=0 -> transRate=0.0 classification=neutral /lyapunov numerical convergence to the proved limit -2, eps0=0.01, z0=0: t=10 -> rate=-1.80000908 (error 2.0e-1) t=50 -> rate=-1.96000000 (error 4.0e-2) t=500 -> rate=-1.99600000 (error 4.0e-3) t=50000 -> rate=-1.99996000 (error 4.0e-5) t=1e7 -> rate=-1.99999980 (error 2.0e-7) Monotone convergence across 6 orders of magnitude in t -- not a single lucky sample. /nogo?limit=-2 -> deSitter_possible=false (genuine attractor, excluded) /nogo?limit=0.5 -> deSitter_possible="not excluded by this result" (theorem's precondition, limit<0, not met -- correctly declines to overclaim in the other direction)

One real bug was caught and fixed in building this: the naive implementation of /lyapunov computed ε(t) directly and then took its log, which underflows to exactly 0.0 in floating point once t is more than a few hundred, throwing a math domain error on log(0). The fix computes log|ε(t)/ε0| directly from the closed-form exponent (−2t + 2e−z0(1−e−t)) instead of exponentiating and then re-taking the log — the kind of numerical-stability bug that only shows up when a proof gets turned into running code, not when it stays a theorem statement.

The product angle

What it's for A researcher or engineer with a system exhibiting some measured or modeled transverse contraction rate can query whether a target steady-state behavior is structurally excluded — without needing to read the contact-geometry paper first. The API is the theorem, packaged as a single HTTP call with a plain-language verdict attached. This is the same "AXLE as a service" model already running for the differential-equations working papers (WP-21/WP-22), applied to a result that happens to produce a crisp binary answer rather than a numeric estimate — a better shape for metering per call.

Fit with existing distribution: the membership tiers already on Gumroad ($25–$250/year, per-repo access) are built for humans reading chapters. An API is a different buyer — a script, not a person — and the natural model is metered or flat-fee API-key access layered on top of the existing tiers, not a replacement for them. No pricing number is committed here; that is a decision for after the prototype has real callers, not before.

What this chapter does not claim

The underlying Lean file still carries three tracked sorries (#H1, #H2, #H3/#H3b) — the closed-form ODE check, the Lyapunov limit, and the no-go integral are stated precisely but not machine-verified in Lean yet, only numerically verified in Python above and derived on paper in helix_toy_model.tex. The API is honest about this: every response names the theorem it implements, sorry-status included, so a caller can tell the difference between "kernel-checked" and "numerically checked, paper-derived" without reading the Lean source. Selling access to a numerically-verified-but-not-yet-kernel-checked result is fine as long as it is labeled as such, which is why every JSON response carries its own theorem citation rather than a bare number.

ComponentStatusNotes
4 endpoints, running prototypebuilt + testedFlask, tested via test client; see AXLE/nogo-api/
Numerical stability (large-t underflow)fixedCaught this session; see bug note above
Underlying Lean proofspartialTrichotomy proved; #H1/#H2/#H3/#H3b remain sorry
Auth, rate limiting, deploymentnot startedPrototype 0.1 is local-only, no production hardening
Pricing modeldeliberately undecidedMetered API-key layer proposed; no number committed
← Book 6 index The Cosmic No-Go →