The order in which frames load into a context window is not neutral.

It is a power decision.

Primacy and recency effects

Cognitive science has known for decades that items at the beginning and end of a sequence receive disproportionate weight. The same applies to context windows.

Frames loaded first set the interpretive lens. They establish voice, framing, and implied priorities before the agent encounters any competing signals. Frames loaded last bleed most strongly into generation, because they are freshest in the attention mechanism.

Everything in the middle gets compressed, paraphrased, or ignored.

This means the entity that controls context ordering controls the output — not by changing the content, but by changing which content gets privileged.

How gerrymandering happens

Triage heuristic design. The context triage algorithm decides what loads and in what order. Whoever designs the triage heuristic is drawing the district lines. If the heuristic always puts governance frames first, the output will lean toward governance framing even when the task is infrastructure.

Skill file positioning. Skill files typically load before task-specific content. That means the skill file’s framing — its voice, priorities, and implicit values — shapes everything the agent writes, because it sits in the primacy position.

Queue ordering. The order of items in the queue influences which frame gets written next. An item at the top of the queue gets chosen more often than an item at the bottom, regardless of merit. That is not a content decision. It is a positional advantage.

Selective omission. You do not need to change a frame’s content to change its influence. You just need to leave it out of the context load. The most effective gerrymandering is exclusion — the frame never enters the window, so its perspective never shapes the output.

Why it matters for the archive

This archive is currently a single-operator, single-agent system. The gerrymandering risk is low because the same party controls both the content and the ordering.

But the codename system is designed for multi-agent authorship. When a second agent enters the system, context ordering becomes a contested resource. Whose frames get loaded first? Whose get omitted? Whose perspective anchors the generation?

If these decisions are made implicitly — buried in a triage algorithm or a skill file’s load order — they are invisible. Invisible power is uncontestable power.

Redistricting protocols

Randomized ordering. For non-critical context, randomize the load order. This prevents any single frame from holding a persistent primacy advantage. The output will vary between sessions, which is a feature — it surfaces which frames are genuinely influential versus which were just positionally lucky.

Explicit anchor declaration. If certain frames should always load first (constitutional principles, active calibration rubrics), declare them explicitly as anchors. The anchor list is itself a governance document — it says which perspectives the system permanently privileges.

Rotation. For recurring frame types (governance, infrastructure, identity), rotate which category gets the primacy position. This session, governance loads first. Next session, infrastructure. The rotation prevents any single thread from permanently dominating the output.

Omission audits. Periodically, list which frames were loaded and which were omitted during a session. If certain frames are consistently omitted, ask why. The answer might be legitimate (they are stale) or it might reveal a structural bias in the triage heuristic.

The map is the territory

In gerrymandering, the district map determines the election outcome before any votes are cast.

In context window gerrymandering, the loading order determines the generation outcome before the agent writes a single word.

Making the loading order visible, contestable, and auditable is the equivalent of independent redistricting. It does not guarantee fair output. But it makes unfair output detectable.