# How this page is checked — website edition 011

This is the visual companion to manuscript v0.7, directed by Ergentics, LLC.
The equations illustrate classical restricted families and a local infinite
series. This edition does not claim a general finite closed-form solution.

Ruby generates this edition’s page, color variables and seven geometry illustrations from the maintained presentation sources. It uses the standard library, without a Ruby server or a gem installation. A check rejects stale generated bytes; a separate JavaScript implementation checks the four exact Lagrange plates and their rendered coordinates.

Before deployment, the repository's workflow runs checks in Chrome for:

- Exact-state force residuals, invariants and deliberately wrong analytical controls.
- Both families' equations, labels, state table and selected explanations.
- Narrative phase presets, readable chapter layouts and the bound expression.
- Actual text contrast, numbered body identities and recorded palette values.
- Intermediate motion, stable objects, interruption and reduced-motion endpoints.
- Real keyboard increments, cyclic-time boundaries and readable body numbers.
- Layout at 1440, 900, 620, 390 and 320 CSS pixels.
- Static content when the interaction script fails, SVG download and CSP blocking.

The workflow stops before deployment if these checks fail. The local research
record preserves the exact source identities, original independent reviews,
test receipts, failures and deployment verification. Three separately prompted
model labels reviewed the baseline against the same ten-part rubric; the
coordinator selected and implemented the changes. This was an exploratory
design review, not a controlled comparison of model capability.

The page uses local assets and no analytics, account form or application API.
Its delivery policy restricts scripts to this origin, blocks outgoing fetches,
denies embedding, and disables camera, microphone and geolocation. Source
configuration alone is not evidence of delivered headers; the deployment
record also checks the actual HTTPS responses. A private source repository and
noindex directive do not make a deployed Pages website private.

These checks cover their named browser and states. They are not a full
accessibility qualification, screen-reader study, all-browser visual review,
security audit, independent mathematical certification or measured educational
benefit. No screenshots or native app captures were used in this edition.

[Return to the research](index.html#paper) ·
[Scientific manuscript](paper.md) · [Worked reference card](reference-card.md)