neural-avalanche-utac
GenesisAeon Package 20 (P20) — Brain Criticality & Neuronal Avalanches as UTAC System
Neuronal avalanches at criticality modelled as UTAC system.
Key result: Γ_brain ≈ 0.251, a rescaling of the η = 50% homeostatic
setpoint through the shared GenesisAeon σ=2.2 default. Its numeric match
to amoc-utac's Γ_AMOC is a verified construction artifact of that shared
constant (both packages use the identical formula and coincidentally
equal η), not an independent cross-domain physics finding — see
constants.py's GAMMA_BRAIN docstring for the full derivation.
Installation
pip install neural-avalanche-utac
For local development:
pip install -e ".[dev]"
Quickstart
neural-utac run --duration 3600
neural-utac criticality-check
neural-utac gamma-universality
Integration in genesis-os
from genesis_os import GenesisOS
os = GenesisOS()
neural = os.load_package(20)
results = neural.run_cycle(duration_seconds=3600)
Benchmark
Validated against Hengen & Shew (2025).
On the "50% setpoint → Γ ≈ 0.251" claim
This is NOT a falsifiable prediction as stated: for ANY system with an
η = 50% efficiency/homeostatic setpoint, arctanh(0.50)/σ gives exactly
this value at σ=2.2 by pure algebra — the formula guarantees the match
regardless of the underlying domain's physics. A genuine test of
cross-domain universality would need σ independently derived per domain
against real dose-response data, which has not been done here or in any
other GenesisAeon UTAC package sharing this default. See
constants.py's GAMMA_BRAIN docstring for the full reasoning.
Role in the GenesisAeon Ecosystem
neural-avalanche-utac is GenesisAeon Package P20 (domain: neuroscience
/ cortical criticality). It models neuronal avalanches at criticality as a
UTAC dynamical system, giving Γ_brain ≈ 0.251 — a rescaling of the η=50%
homeostatic setpoint through the shared σ=2.2 default (see above for why
this is not independent cross-domain evidence).
Citation
See CITATION.cff for the package citation and the GenesisAeon whitepaper
DOI badge above.
License
MIT
Metadata
Release files for neural-avalanche-utac 1.0.1
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 | |
|---|---|---|---|---|
| neural_avalanche_utac-1.0.1.tar.gz | 110.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neural_avalanche_utac-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 139.2 kB
Release files / neural_avalanche_utac-1.0.1.tar.gz
| Download URL | neural_avalanche_utac-1.0.1.tar.gz |
|---|---|
| Size | 110.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9810b92c670cfebf4a7a67840c2af84795948e9b910ad5bc92d150118be59c26
|
|
BLAKE2b-256 checksum How to use checksums |
66c3c29ce4e9249a9327d0ef8f821aacaf193545e4beb7c2cb5efde11e4bf5bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / neural_avalanche_utac-1.0.1-py3-none-any.whl
| Download URL | neural_avalanche_utac-1.0.1-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
17594a49d74c3910ca0bd3c2b3c56edde6ff142be0e0b2a641a0bda33104740e
|
|
BLAKE2b-256 checksum How to use checksums |
51d5c8aea906e416d42f753d30bbf92cec6f3f848e50aaf5a064d88c4715e3c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for neural-avalanche-utac 1.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.