Core idea

An attention density envelope marks how much interaction the system can keep live and meaningful before visibility, simulation detail, or decision quality begins to degrade.

It is a limit model for relevance, not a claim that everything outside the envelope stops existing. The question is which events, actors, and spaces can still be tracked with enough clarity to support good decisions before the system starts drowning in noise, backlog, or fake precision.

In worldbuilding and simulation, this matters because scale is often broken by overexposure. Designers add every frontier, convoy, institution, and crisis to the same active layer, then wonder why none of them feels legible. The envelope forces a harder distinction between what stays ambient and what must become immediate.

Trace the live envelope before you add detail

Threshold 1Mark the always-live zone

Identify the actors, routes, and spaces that must remain visible every turn, scene, or planning cycle.

Threshold 2Define escalation triggers

Specify which disruptions, attacks, or shortages force distant systems into immediate relevance.

Threshold 3Compress passive detail

Turn low-priority activity into summaries, background drift, or delayed updates rather than pretending it is fully live.

Threshold 4Test overload behavior

Check what happens when crises stack faster than the system can surface them coherently.

Axis	Question	Signal
Spatial threshold	How much surrounding space can remain actively relevant?	Radius, neighboring nodes, corridor depth, theater width
Interaction threshold	How many concurrent events can be handled coherently?	Combat count, convoy density, civic incidents, alert bursts
Update threshold	How much fine detail can be simulated now?	Tick rate, administrative refresh, visibility granularity, event backlog
Escalation threshold	What forces a distant event into the active envelope?	Gateway loss, depot strike, capital threat, corridor collapse

When attention collapses

Attention collapses when distant events enter the active layer faster than the system can meaningfully sort them. At that point, visibility becomes clutter, updates lag behind reality, and urgent signals are buried among events that should have remained summarized or deferred.

This is why bottleneck sites matter so much. A depot strike, capital threat, or corridor closure can yank a remote slice into the live envelope because the disruption is no longer local. The envelope therefore depends as much on escalation logic as it does on map size.

Relation Map

Attention-density adjacencies

Control Surface Matrix

Shows how different actors may have differently sized awareness and response envelopes.

Cross-Slice Dependency Map

Shows how local attention must still respect dependencies crossing slice boundaries.

Storage Node

Identifies the places whose disruption most often forces distant events into immediate relevance.

Transfer value

The reusable lesson is that relevance has structure. Good systems decide what stays live, what stays latent, and what kinds of failure force a change in attention state.

Use the attention density envelope whenever a world, simulation, or strategy surface needs to scale without pretending that every corridor and every institution can be actively processed at once.