phaethon-chimera
GenesisAeon Package 35 — Phaethon-Asteroid: Frustrierte Systeme & Chimera-Zustände
UTAC-Modellierung von 3200 Phaethon als frustriertes Chimera-System. 47 quantitative Vorhersagen für die DESTINY+ JAXA-Mission (Flyby 2029).
Wissenschaftlicher Hintergrund
3200 Phaethon ist ein anomales Objekt — gleichzeitig Asteroid (deterministisch, Keplerbahn) und kometenähnlich (stochastischer Staubausstoß bei Perihel, Quelle der Geminiden).
Diese Frustration im UTAC-Kontext entsteht durch:
dH/dt = r·H·(1-H/K)·tanh(σΓ) + A·cos(ω_Phaethon·t)
Der periodische Term (Bahnfrequenz) konkurriert mit dem UTAC-Logistik-Term → Chimera-Zustand: Teil des Systems ist geordnet (Keplerbahn), Teil ist SOC (stochastische Aktivität bei Perihel).
CREP-Einordnung
| System | Γ | Domäne |
|---|---|---|
| Amazon | 0.116 | Ökologie |
| Phaethon | 0.165 | Asteroidendynamik |
| AMOC | 0.251 | Ozeanographie |
| Neural | 0.251 | Neurowissenschaft |
Phaethon liegt zwischen Amazon und AMOC — im mittleren kritischen Bereich.
Installation
pip install phaethon-chimera
Quickstart
uv sync
uv run pytest
# CLI
uv run phaethon run --n-orbits 10
uv run phaethon run --n-orbits 10 --destiny-predictions
uv run phaethon chimera-state
uv run phaethon destiny-report --format table
Kernklassen
| Klasse | Funktion |
|---|---|
PhaethonChimera |
Diamond-Interface (run_cycle, CREP, UTAC, phase events) |
FrustratedUTAC |
Frustrierte UTAC-ODE mit periodischem Forcing |
ChimeraDetector |
Kuramoto-Ordnungsparameter R ∈ [0,1] |
PhaethonOrbit |
Keplersche Bahn (JPL Horizons) |
DustEmissionModel |
Stochastische Staubemission (Bernoulli + SOC) |
SOCPhaethon |
Power-Law-Fit, Hurst-Exponent |
GeminidModel |
Geminiden-Meteoritenstrom aus UTAC |
DESTINY_PREDICTIONS |
Alle 47 falsifizierbaren Vorhersagen |
47 DESTINY+ Vorhersagen (Auswahl)
| # | Größe | Wert ± σ | Einheit | Falsifizierbar |
|---|---|---|---|---|
| 1 | Γ_phaethon | 0.165 ± 0.02 | — | Nein — keine unabhängige Herleitung, siehe Hinweis unten |
| 6 | Chimera R (Perihel) | 0.50 ± 0.10 | — | Ja |
| 7 | Chimera-Übergangsaltitude | 2.3 ± 0.4 | km | Ja |
| 11 | Emissionswahrscheinlichkeit/Orbit | 0.23 ± 0.08 | — | Ja |
| 16 | SOC τ-Exponent | 1.3 ± 0.1 | — | Ja |
| 36 | Geminid ZHR | 120 ± 20 | /hr | Ja |
| 46 | DESTINY+ Flyby | 2029 ± 1 | Jahr | Ja |
Die meisten Vorhersagen sind vor dem DESTINY+ Flyby (2029) publiziert
→ echt falsifizierbar. Ausnahme (2026-09-15, Ehrlichkeits-Review):
Vorhersage #1 (Γ_phaethon) hat keine zitierte physikalische Herleitung —
der Wert wurde laut ursprünglichem Code-Kommentar gewählt, um zwischen
GAMMA_AMAZON (0,116) und GAMMA_AMOC (0,251) im geteilten
Γ-Spektrum zu liegen, nicht aus einer gemessenen oder modellierten
Eigenschaft von Phaethon abgeleitet. Vorhersage #4 (H*) wird direkt
aus #1 und #3 berechnet und ist ebenfalls nicht unabhängig. Beide sind
im Code jetzt als falsifiable=False markiert — siehe
constants.pys GAMMA_PHAETHON-Docstring und
crep-utac-afet-formalism/FOLLOWUP_TICKETS.md für die vollständige
Herleitung.
Repository-Struktur
src/phaethon_chimera/
├── system.py # PhaethonChimera — Diamond interface
├── orbital.py # Keplersche Bahn (JPL Horizons)
├── frustrated_utac.py # Frustrierte UTAC-ODE + RK4
├── chimera_detector.py # Kuramoto-Ordnungsparameter
├── dust_emission.py # Stochastische Staubemission + SOC
├── soc_phaethon.py # Power-Law-Fit, Hurst-Exponent
├── destiny_predictions.py # 47 DESTINY+-Vorhersagen
├── geminid_model.py # Geminiden-Meteoritenstrom
├── benchmark.py # Benchmark-Targets
├── cli.py # phaethon CLI
└── constants.py # Physikalische Konstanten
data/
├── phaethon_orbital_elements.yaml
├── destiny_plus_targets.yaml
└── ztf_photometry_summary.yaml
Benchmark-Targets
BENCHMARK_TARGETS = {
"gamma_phaethon": (0.165, 0.020),
"chimera_R_perihelion": (0.500, 0.100),
"soc_tau_exponent": (1.300, 0.100),
"emission_probability": (0.230, 0.080),
"geminid_zhr": (120.0, 30.0),
"n_destiny_predictions": (47.0, 0.0),
"phi_cuberoot": (1.17480502, 0.00001),
}
GENESIS-OS Registrierung
PACKAGE_REGISTRY[35] = {
"name": "phaethon-chimera",
"class": PhaethonChimera,
"domain": "asteroid-dynamics",
"scale": "solar-system",
"zenodo": "10.5281/zenodo.20807497",
"reference": "DESTINY+ 2024+"
}
Citation
@software{roemer_phaethon_chimera_2026,
author = {Römer, Johann},
title = {phaethon-chimera: Frustrated UTAC Systems \& Chimera States},
version = {1.0.0},
publisher = {Zenodo},
doi = {10.5281/zenodo.20807497},
year = {2026},
note = {GenesisAeon Package 35, DESTINY+ predictions}
}
A new Zenodo DOI version will be assigned automatically on each future GitHub Release, once Zenodo–GitHub integration is enabled for this repo.
Verbindung zum GenesisAeon-Ökosystem
- P31 (vrig-cosmological): v_RIG ≈ 1352 km/s normiert auf Phaethon-Orbitalgeschwindigkeit
- P32 (beta-clustering): β-Cluster — Phaethon im astrophysikalischen Cluster (β ≈ 0.65–1.20)
- P36 (sa-sv-duality): S_A/S_V-Entropiedualität der Phaethon-Trajektorie
- P38 (phi-scaling): Φ^(1/3) ≈ 1.174 Skalierung zwischen Orbitaldynamik-Domänen
Zeitkritisch: DESTINY+ Flyby 2029 — alle Vorhersagen sind vor dem Flyby publiziert.
Johann Römer · MOR Research Collective · Mai 2026
Metadata
Release files for phaethon-chimera 1.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 | |
|---|---|---|---|---|
| phaethon_chimera-1.0.2.tar.gz | 196.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| phaethon_chimera-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 224.8 kB
Release files / phaethon_chimera-1.0.2.tar.gz
| Download URL | phaethon_chimera-1.0.2.tar.gz |
|---|---|
| Size | 196.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8245a88b5a3247f5606940bca7bb3c05e7497d35ff2db4f413390287ba34df6
|
|
BLAKE2b-256 checksum How to use checksums |
b58ef57f9976e253752bb669f31ab584063c04b415fe40b68c16d9607209513d
|
| 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 Sep 15, 2026.
Transparency logRelease files / phaethon_chimera-1.0.2-py3-none-any.whl
| Download URL | phaethon_chimera-1.0.2-py3-none-any.whl |
|---|---|
| Size | 28.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76419680ac7a340a42f9c665d0d26c586ce629010b27c7011c706acd8e651983
|
|
BLAKE2b-256 checksum How to use checksums |
f7562f9098a3017904aec0e2fe38b342032c84338ebf3ec1c9b14caa3946b7b1
|
| 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 Sep 15, 2026.
Transparency logSecurity for phaethon-chimera 1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for phaethon_chimera-1.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 Sep 15, 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.