AEG Shakespeare
Shakespeare is a process-representation library for building and searching compact process presentations.
It is not primarily an ODE solver and does not take eigenvectors, Fourier modes, a preferred coordinate system, or a particular special-function vocabulary as its starting ontology. The project starts from process structure, asks how that structure can be represented compactly, searches alternative presentations, and only then admits the analytic or geometric language forced by a successful presentation.
Process ODE describes computation in a representation; Shakespeare provides machinery for searching for representations in which that computation is cheaper to express.
Status
Latest PyPI release: 0.0.2, a pre-alpha research preview.
Current main release version: 0.0.2.
The package is intended to be installable and useful as an experimental mathematical toolkit, but 0.0.x APIs are not yet covered by backward-compatibility guarantees. Exact certificates, explicit failure modes, and conceptual layer separation take priority over interface stability during this phase.
See docs/34-release-0.0.2.md for this release contract, docs/10-release-0.0.1.md for the first-release contract, and CHANGELOG.md for release summaries.
Install
python -m pip install aeg-shakespeare
For development:
python -m pip install -e '.[dev]'
PyPI distribution: aeg-shakespeare
Python package: aeg_shakespeare
Supported CPython versions: 3.10 through 3.14
SymPy is an algebra/discovery backend. Shakespeare keeps its own process-level semantics and does not define process equality by sympy.simplify().
Public API direction
The public surface is organized as a mathematical pipeline rather than a flat catalog of symbols:
Process -> Presentation -> Discovery -> Analysis
aeg_shakespeare.process
What the process is.
process.history— literal ordered histories and caller-supplied semantics;process.finite— finite parameterized families, characters, actions, and additive process cocycles;process.local— local/infinitesimal realizations such asProcessSystemandProcessFrame.
aeg_shakespeare.presentation
How process history is objectified, quotiented, compressed, and compared.
presentation.history— explicit rewriting, task signatures, and finite history geometry;presentation.construction— construction-history-preserving primitive proposals;presentation.constraints— exact algebraic quotient constraints;presentation.grammar— generated finite process grammars;presentation.relations— exact process relations, factors, kernels, and decompositions;presentation.search— budgets, representation cost, Pareto filtering, and presentation search.
aeg_shakespeare.discovery
How alternative presentations are searched.
The current discovery package contains bounded polynomial invariant/quotient search, structured observer proposals, first-order quotient selection, and explicit coefficient-language extension experiments. These are search procedures, not process ontology.
aeg_shakespeare.analysis
What analytic or geometric language a successful presentation supports.
analysis.module— finite process-function modules;analysis.am— the Addition/Multiplication process calculus;analysis.algebraic— algebraic quotient profiles and Weierstrass calibration;analysis.abelian— lifted histories, Abelian integrals, cycle systems, periods, and normalized history quotients.
A representative import therefore looks like:
from aeg_shakespeare.process.history import ProcessWord
from aeg_shakespeare.presentation.grammar import discover_generated_presentation
from aeg_shakespeare.discovery import discover_polynomial_invariants
from aeg_shakespeare.analysis.am import AMFunctionTheory
The package root is now intentionally only a namespace router:
import aeg_shakespeare as sh
sh.process
sh.presentation
sh.discovery
sh.analysis
Legacy root-level imports from the early 0.0.x research-preview surface remain available lazily during the migration and emit DeprecationWarning; they are no longer part of the declared public root surface. See docs/API.md for the detailed map and migration notes.
Quick start
The smallest runnable examples are deliberately problem-independent:
python examples/quickstart.py
python examples/constraint_quickstart.py
python examples/grammar_quickstart.py
They demonstrate, respectively:
- literal process history, an explicit presentation relation, and A/M resonance;
- exact equality modulo algebraic presentation constraints;
- generated process grammars and return-relation discovery from a seed.
The examples are entry points, not mathematical proofs. Complete classical and research arguments live under tests/classical/ and tests/research/ as cited executable essays.
Reading the source
Shakespeare uses a literate-programming discipline. Mathematically substantial Python modules and tests should explain the mathematical pressure that created an abstraction before presenting its implementation.
classical historical path:
analytic difficulty -> special construction -> geometry/algebra
Shakespeare reconstruction:
primitive process -> history/constraint/invariant -> quotient geometry
-> adequate function language -> classical formula as a shadow
The canonical pendulum calibration therefore begins from constrained position/velocity dynamics rather than from theta, sin(theta), or a preselected elliptic function. Likewise, the A/M layer begins from Addition and Multiplication and their finite/noncommutative process relations before logarithms or familiar harmonic-analysis names are introduced.
A substantial test in tests/classical/ or tests/research/ is expected to be a complete mathematical vignette: question, primitive data, classical lineage, Shakespeare reconstruction, calibration statement, proof map, claim boundary, and bibliographic references.
See:
docs/09-literate-programming-and-mathematical-lineage.mddocs/11-references-and-test-essays.mddocs/REFERENCES.md
Current research boundary
The current implementation supports a bounded loop from declared process structure to evaluated presentations, plus concrete routes from successful presentations toward process-adapted function theory and global geometry.
Recent calibrations have established several deliberately limited layers:
- finite families, scalar characters, family actions, and additive process cocycles live in the process layer;
- rewriting, task quotients, construction histories, grammars, relations, and Pareto cost live in the presentation layer;
- invariant/observer/quotient/language proposals live in discovery;
- A/M calculus, algebraic quotient profiles, Abelian integrals, lifted cycles, period matrices, and normalized history quotients live in analysis.
The separation is intentional. For example, ProcessCocycle is a finite-process object; generic cohomology classes, central-extension groups, projective representations, and an automatic finite-to-infinitesimal bridge are not currently public abstractions. Likewise, the existence of oscillator spectral shadows does not make maximal spectral splitting a universal presentation objective.
Physical and mathematical calibration problems do not define the package API. Pendulum, oscillator, Galilean mechanics, magnetic translations, and related systems live in tests as probes of the common machinery.
Development and release checks
python -m pip install -e '.[dev]'
pytest
python -m build
python -m twine check dist/*
CI tests the same release gate on CPython 3.10 through 3.14, installs the built wheel into a fresh virtual environment, and imports the package from outside the repository source tree. See docs/RELEASE_CHECKLIST.md.
The evolving mathematical story is indexed in docs/README.md.
License and citation
Shakespeare is dedicated to the public domain using the Unlicense public-domain dedication text in LICENSE. The intent is unrestricted use, modification, publication, redistribution, and reuse of both the software and its accompanying mathematical exposition.
Scholarly attribution is separate from software licensing. Mathematical and historical sources are cited in the literate tests and docs/REFERENCES.md; software citation metadata is provided in CITATION.cff.
Metadata
Release files for aeg-shakespeare 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aeg_shakespeare-0.0.2.tar.gz | 80.7 kB | With provenance | Details for aeg_shakespeare-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aeg_shakespeare-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for aeg_shakespeare-0.0.2-py3-none-any.whl |
Total release size: 166.4 kB
Release files / aeg_shakespeare-0.0.2.tar.gz
| Download URL | aeg_shakespeare-0.0.2.tar.gz |
|---|---|
| Size | 80.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccdb289a0c423e8cb8bc315fab445bf7bca4bf5d94d3878aee376e996c6886d9
|
|
BLAKE2b-256 checksum How to use checksums |
ddb34a6249771860ed0f3cbb726b6818b2988cabbb1fc8da35399a640f421f5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 22, 2026.
Transparency logRelease files / aeg_shakespeare-0.0.2-py3-none-any.whl
| Download URL | aeg_shakespeare-0.0.2-py3-none-any.whl |
|---|---|
| Size | 85.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aaa0d1d8fce4b3d7d7ab6ad345d4c8c7475e322f6e3f7bb60ef41f2bbd4c599c
|
|
BLAKE2b-256 checksum How to use checksums |
1c16091813ca819f38d19d42ebd8c05ff0c2d8b167492c1b509d81eb3be6c9ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 22, 2026.
Transparency logSecurity for aeg-shakespeare 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for aeg_shakespeare-0.0.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.