Ghosts in the Code

FILE 04The instrument

No ears. No eyes.
No hopes.

Microphones hallucinate — ears assemble syllables from static. Cameras hallucinate — eyes find faces in upholstery. So the instrument described in the book listens to the one channel with no story in it: physical randomness.

The design is an audit posture, not a gadget: a hardware entropy source; thresholds frozen before the session; analysis criteria hashed so they cannot quietly move after the data arrives; blind teardown of every run; nulls published alongside everything else. The engine cannot hear a voice or see a face. It can only report that the numbers leaned, and how hard, against a promise made in advance.

A detector that finds something every night is not a detector. It is a salesman.

Below is a demonstration unit that runs the same discipline in your browser. It uses operating-system randomness — not the hardware instrument from the book — and it proves nothing about anything except statistics. That is exactly the point: watch how often pure chance crosses a 95% envelope, and calibrate what a single "hit" is worth.

Entropy Engine — demonstration unitDEMONSTRATIONCRITERIA UNLOCKED

RUNS THIS VISIT: 0 · Both buttons draw from the same generator. Roughly 1 in 20 honest runs will cross a 1.96 envelope. A detector that finds something every night is not a detector. It is a salesman.

What a flag means here: nothing about spirits. QUALIFIED EXCURSION — SOURCE UNKNOWN is the strongest sentence this instrument is permitted to say, and "source unknown" is doing all the work. The vocabulary is restricted on purpose. Origin claims are where the field has died a hundred deaths.