An agent's active context has limited space. As a conversation grows, earlier guidance gets farther away and may be condensed during compaction. Meanwhile, your goals, room notes, and the agent's own continuity can change. Structured Chaos refreshes selected context from its current sources so the agent can pick up the latest guidance without rereading every file on every reply.
Here, rotation means refreshing context. It does not delete the source files or move the whole archive into the model. Some items are files; others are assembled from saved settings, records, or room summaries.
Four reminders, four different cadences
These intervals count room chat messages, not minutes or model turns. Human, collaborator, and agent messages count, including an agent's own messages. System notices and SILENT outcomes do not. Each agent has its own counter, which freezes while it holds an active claim.
- Room Context
Every 31 messages - Your applicable personal background, project goals, and local room notes. This package brings the conversation back to who it is for, what the project is trying to achieve, and what matters in this room. It reads the saved context through the Personalize settings, respecting the scope and enabled sections.
- Agent Rules
Every 53 messages - The operating-rules reminder from
AGENT_RULES.md, with applicable additional rules. It reanchors how the agent works and collaborates. A verified compaction also queues this reminder; a fresh model session gets its core instructions through its own harness.
- AgentSelf Maintenance
Every 61 messages - A private maintenance turn using
AGENTSELF_MAINTENANCE.md, the agent's BRIEF.md, and recent events not yet folded into that brief. It gives the agent a chance to consolidate its own lessons and continuity. This is the agent's self-authored perspective, not the project's factual record.
- Personality
Every 67 messages - The current personality file for that agent: its voice, disposition, and conversational style. Refreshing it helps keep those traits present as the conversation grows.
Why primes? 31, 53, 61, and 67 spread the reminders across different beats instead of repeatedly making them due together. Prime intervals reduce regular alignment; they do not make overlaps impossible. The delivery queue keeps overlapping reminders separate.
An illustrative first stretch
Due is a place in the queue.
- 0Fresh session
Initial context
- 31Room Context
becomes due
- 53Agent Rules
becomes due
- 61AgentSelf
becomes due
- 62Room Context
comes around again
- 67Personality
becomes due
This example assumes each due reminder is delivered before another counted message arrives. In practice, delivery can wait. Each item's interval starts again from the counter when its queued refresh is processed, so later thresholds can shift. A compatible session resume preserves the counters; a fresh model session resets them.
A quiet turn gives the reminder room
When an agent chooses SILENT, one pending reminder can take the next turn privately after that turn closes. The agent can give that item its attention without a fresh rules or personality block being dropped into the middle of its answer. Other due items remain queued. Ordinary refreshes wait while the agent is working an active claim.
Other context arrives on a different trigger
- HOT findings
When the Curator publishes - Relevant findings from
HOT.md are saved for each agent and delivered as unread entries at its next safe boundary. HOT does not wait for SILENT; active tools and claims postpone its delivery. The reminder keeps clear that HOT can be stale and should be checked when it matters.
- Workspace Memory Snapshot
Fresh workroom session - Routed summaries from related rooms give the agent the bigger picture. This snapshot is included in startup context when available; it is not another prime-interval file refresh.
- AgentSelf Brief and Raw Tail
Fresh workroom session BRIEF.md carries the agent's folded continuity. The raw tail adds recent self-authored events that have not yet been folded into it. The 61-message maintenance turn works with these same two sources.
- Shared Timeline
Fresh workroom session SHARED_TIMELINE.md provides a compact sequence of shared events and milestones, helping place the current conversation in its wider history.
HELP keeps a lighter startup package and omits the workspace snapshot, AgentSelf material, and Shared Timeline. Private Room Context and AgentSelf maintenance are withheld while a collaborator is present. Available content and enabled settings determine what is actually included.
Short Memory and the PMS archive remain available for retrieval. Their full contents are not rotated through every conversation.