Repository navigation
Simulation Guide
ASH simulations are deterministic reference tools for finite-state behavior. They are useful for checking implementation semantics, controlled ablations, and artifact generation. They are not external physical validation by themselves.
python tools/generate_artifacts.py
python tools/run_proof_suite.py
python tools/check_generated_outputs.py . --include-manuscriptpython simulation.py
python src/simulate.py --agents 1000 --ticks 250 --noise 0.01 --seed 20260624Tracked ablations compare:
| Condition | Purpose |
|---|---|
| Uniform starts | Confirm uniform-hypercube baseline behavior |
| Zero starts | Test convergence behavior from concentrated initial condition |
| ASH transforms | Reference transform behavior |
| No transforms | Control without code action |
| Random weight-four transforms | Matched finite transform control |
| Bit-flip noise | Noise sensitivity check |
The proof certificate records that the binomial Hamming-weight envelope is the marginal of uniform occupancy. A bell-shaped Hamming histogram is therefore a finite-hypercube baseline unless a separate test proves stronger structure.
python tools/reproduce_sector_mixing.py --output-dir .
python -m pytest tests/test_sector_mixing.py -qpython tools/run_background_bridge_validation.py
python -m pytest tests/test_background_bridge_remediation.py -qflowchart LR
A["Simulation command"] --> B["Data output"]
B --> C["Figure output"]
C --> D["Artifact manifest"]
D --> E["Repository verification"]
A simulation output can support implementation correctness only within its configured scope. It cannot replace proof obligations, external data likelihoods, or prediction-lock discipline.
ASH Model wiki. Source-of-truth files live in the flynn33/ASH-Model repository.
- Mathematical Framework
- Finite-Observer Physics
- Evidence and Artifacts
- Hypercube and Adinkra Guide
- Visual Model Atlas
- Simulation Guide