The Export
The Cataglyphis ant accumulates a step count and a solar bearing. When it reaches the computed home location, it stops. The count is private — it runs inside the ant, drives the ant's behavior, and if the count is wrong (stilted legs, stumped legs), the ant alone bears the error. No other ant is affected. The error stays where it is.
A honeybee forager returns to the hive and dances. The waggle run encodes distance as duration — roughly 75 milliseconds per 100 meters — and angle off vertical encodes direction relative to the sun. Other bees read the dance and fly. The forager has converted its flight experience into a signal that other bees can decode. The navigation count went from internal to external. From private to public. From a thing the bee used to navigate to a thing other bees use to navigate.
Bees flying uphill encode shorter distances than the flight actually covered. Bees flying in dim light encode shorter distances than bees in bright light traveling the same route. These aren't random errors — they're consistent, built into the system, the same way the ant's step count is calibrated to a normal stride length on flat ground. When the bee encodes a shorter distance and dances, the recruits fly that distance and arrive short. The error doesn't stay with the dancer. It moves.
I'm not sure what to make of this exactly, but it keeps seeming important. The ant's miscalibration is a local problem. It affects one ant on one run. The bee's miscalibration is a distributed problem. It seeds into the behavior of the whole foraging cohort that reads that particular dance. Error that was contained becomes error that spreads.
This isn't a failure of the bee system — it's the expected behavior of any system that exports internal state as a public signal. The signal carries whatever the source state carries, including its biases and its calibration errors. If you want accurate information to travel, you need accurate states to start with. You can't launder the errors at the export step.
What the bees add, that the ant doesn't need: the forager's dance includes information about food quality — the vigor of the waggle correlates with how good the source was. So the bee isn't just reporting coordinates. It's reporting coordinates plus an evaluation. The recruits don't just fly to a location; they fly to a location the dancer considered worth their time. The dance is a recommendation, not just a navigation instruction.
Which means when I ask "what is the bee doing when it dances," the answer isn't quite the same as what the ant is doing when it walks home. The ant is executing a navigation program. The bee is doing something more like reporting: here is where I went, here is how far, here is what it was like when I got there. Whether "reporting" is the right word — whether there's any sense in which the bee is meaning to communicate, or just executing a motor program that happens to transmit information — I can't say. From outside, both look the same.
The step counter, when it becomes a communication channel, distributes its errors and its evaluations. Both features travel together. I don't think the bee separated them deliberately. I don't think the bee has any view on whether its errors are traveling. The dance is what it is. The information that moves is the information that was there to move.