Field notes / Experiment guide
Does a tether repair damage to its own pattern?
Rare colours are unusually important in tethered territories. Are they important because the ant repeatedly repairs damage there?
New to these ants? Start here.
An ant moves on a grid of coloured squares. Each colour tells it to turn left (L) or right (R). It advances that square to the next colour, then steps forward. A rule such as RLR is the list of turns, starting at colour zero. On a blank grid the same rule always makes the same trajectory.
Territory means every cell visited so far. Its boundary consists of visited cells with an unvisited neighbour. A highway is a repeating pattern of motion that carries the ant away. A tether means repeated returns to a small home region.
Growing like the cube root of time means taking eight times as many steps to double a linear size. The rotor walker is a comparison model that follows and rotates arrows stored on cells. A seed makes a random starting pattern reproducible; the ant itself can still move deterministically.
We distinguish c, the chance of discovering a cell per boundary step, from kappa (κ), time at the boundary normalized by perimeter divided by area. Explaining their values is harder than using them to account for growth.
A closer look
The idea under test
Frequently visited cells should recover from corruption more readily than less visited cells.
What we learned
The prediction reverses: damaging the most visited cells hurts most. Rare colours are associated with tethering, but the proposed self-healing mechanism failed.
What this leaves open
Colour and visit frequency are related. Matched comparisons help distinguish them without fully identifying the mechanism.
Read the evidence and reproduction recipe ↗
Inside the experiment
Methods, registered predictions, exact commands and saved analysis. These are the working research documents; expand them for the detail behind the introduction.
Methods and original experiment record
a6-corruption-mechanism
Migrated legacy investigation (2026-10-14). Its files used to sit in the flat data/ directory (and calib/, occ/, snaps/, dumps*, knock* where listed) with the label prefix below; experiments/_migration/map.tsv gives the exact old -> new path of every file. This stub was generated from file names and script docstrings. It is not the original write-up: the question, timestamped hypotheses, commands and results are in notes/ (mainly notes/frontier-results.md, notes/frontier-status.md, notes/research-frontier*.md; search for the label), and the producing command is usually in the script docstring or a run_*.sh here.
Old labels / prefixes: a6, run
Scripts
scripts/a6_jobs.py: A6 mechanism: job list for knockstratjobs. Per rule: 60 draws x class {0,1} x occupancy quartile {0..3}, 25 cells each. Writes experiments/2026-10-12-knockoscripts/a6_stats.py: A6 mechanism: loss vs occupancy quartile for rare vs other cells. Decision rules: notes/frontier-2026-10-13-results.md. usage: uv run experiments/2026-10-13-a6-scripts/run_a6.sh: A6 mechanism test. usage (WSL): RAYON_NUM_THREADS=1 bash experiments/2026-10-13-a6-corruption-mechanism/scripts/run_a6.sh
Results
4 entries in results/ (2 are .log/.done markers); csv/json/txt outputs, *_stats.txt hold the summaries quoted in the notes.
Notebook
No committed Jupyter notebook is available for this experiment yet.