FIELD MANUAL · OPERATING LOGIC
ML-002C · Field manual
The Algorithm Game is played inside a system that already knows how to move attention. It uses the same feed, metrics, comments, and repetition, then changes the question.
The objective is not to make the audience watch harder. It is to give a person one bounded chance to notice the system, act inside it, and leave a consequence that the next Player can inherit.
Read the ground beneath the Game →Operating sequence
The rule must be bounded enough to follow and exact enough to judge. A mood is not a mission. A mission changes what can count for the duration of the round.
A view does not enter the Game. A visible choice, comment, proof, refusal, or completed action does. The return signal is the point where an audience member becomes a Player.
The first version may fail. The crowd may ignore it, misunderstand it, exploit it, or reveal that the requested proof cannot exist. The failure remains attached to the round.
A passed rule can open a level. A failed rule can be revised. A Player response can become the next instruction. The consequence is what prevents participation from ending as engagement alone.
The Game is the live edge. The Atlas names the forces around it. The Codex keeps stable findings. The Chronicle preserves order. The Hall records people through witnessed acts.
System language
The language is functional. Each term names a different part of the event so the audience, the Game, and the archive do not collapse into one vague idea.
Interpretive layer
These are not commandments issued before the Game. They are propositions drawn from what the public rounds placed on record.
Start with evidence