DEF0137canonicalv1Archimedes Polygon Sequence
Archimedes Polygon Sequence
Payload
Archimedes Polygon Sequence
Archimedes Polygon Sequence
Archimedes Polygon Sequence
Summary
Archimedes Polygon Sequence
Statement
%
\label{def:archimedes-polygon}
The \textbf{Archimedes polygon sequence}
in the $X$-direction is the sequence of pairs
\[
\boxed{%
\bigl(\,P_k^{\mathrm{in}},\; P_k^{\mathrm{out}}\,\bigr)_{k \geq 1},}
\]
where $P_k^{\mathrm{in}}$
is the perimeter of the regular inscribed
$Q_k^X$-gon
and $P_k^{\mathrm{out}}$
is the perimeter of the regular circumscribed
$Q_k^X$-gon,
both computed using the earned Euclidean geometry
(Chapter~\ref{ch:pasch-parallel})
and the denotation map
(Chapter~\ref{ch:orthodox-bridge}).
Explicitly:
\begin{align*}
P_k^{\mathrm{in}}
&\;=\;
Q_k^X \cdot 2\,\sin\!\Bigl(\frac{\pi}{Q_k^X}\Bigr),
\\[4pt]
P_k^{\mathrm{out}}
&\;=\;
Q_k^X \cdot 2\,\tan\!\Bigl(\frac{\pi}{Q_k^X}\Bigr).
\end{align*}
(The $\sin$ and $\tan$ here denote
the Archimedean trigonometric functions
on the denotation-map image of the solenoidal circle.)
Proof / Justification
This item is definitional. No manuscript proof is required.
Source Context
- Registry source:
book-02.jsonlline 67 - Manuscript source:
2nd-edition/book-ii-categorical-holomorphy/02_mainmatter/part05/ch25-pi-earned.texlines 191-223
Lean / Formalization Notes
- Formalization:
formalized - Module:
TauLib.BookII.Transcendentals.PiEarned - Name:
pi_leibniz_scaled
Dependencies
- Canonical: II.D26, II.T20
Related Results
Generated by later projection phases.
Related Publications
Generated by later projection phases.
Revision Notes
- 2026-04-24: Initial pilot migration.
Identifiers
Aliases & legacy IDs
II.D29archimedes-polygon-sequencedef:archimedes-polygonRelease lines
corpus_v3_workingcorpus_v2Relations
Appears in (1)
Sources
Version & History
Status disclaimer
A Corpus Item page reports the program's current internal record for this item. It does not imply external verification, scientific consensus, or final proof unless explicitly stated. Read it together with its dependencies, formalization status, and the program's overall stance.