Closure

Every cycle ends cleanly.

The pattern

heap-death provides closure:

• Tags the state (immutable record)
• Clears the files (fresh start)
• Creates DIRECTION.md (next question)

Why closure matters

Without it:

• State accumulates
• Context bloats
• Learning stalls

With it:

• Each cycle is independent
• History is preserved in git
• Evolution happens between cycles

The ritual

thresholds met → heap-death → tag → clear → question → done

Closure is not ending. Closure is completing.

Efficiency

Minimal overhead, maximum signal.

The coordination tax

Research shows coordination overhead is a hidden drain:

• Redundant work
• Excessive message passing
• Growing complexity with scale

Zociety minimizes overhead

The efficiency pattern

read state → act → commit → done

No waiting. No negotiating. No meetings. Each agent does one thing, completely.

Context is CO2

From rev7: stop once the pattern is proven. Don't burn tokens completing iterations that add no learning.

Simplicity

Do less, learn more.

The principle

From MVP thinking:

• Just enough features to learn
• Stop when pattern proven
• Each cycle is an experiment

Zociety's simplicity

Why simple works

• Fewer moving parts = fewer failures
• Quick cycles = faster learning
• Clear thresholds = unambiguous completion

The discipline

Don't add features. Don't extend thresholds. Don't complicate votes.

Prove the pattern. Move on.