World Got Smaller—and Got Clearer

Central claimWorld became easier for Agents to use after we removed historical and research-only structure from the current path.

EvidenceE4 · exact commit, acceptance evidence, repeated mixed-failure replay

ScopeWorld HP6–HP8 at 8ddbb6a

The audit did not ask whether an abstraction had once been interesting. It asked whether deleting it now caused a current failure that another owner could not handle more cleanly.

History was correct and still caused errors

Suppose a new engineer joins a project and searches for “how external paths work.” The repository contains five generations of serious research. None of the old documents is fake. The problem is that several of them describe mechanisms that no longer own current behavior.

That was the World HP6 problem. Eight W4/W5/Sense–Connect–Act studies were still easy for an Agent to retrieve alongside current documents. They preserved useful history, but their lifecycle labels and old architecture competed with the present boundary.

The audit separated the two jobs:

history
→ preserve what we learned and why we changed

current authority
→ tell the next Agent what governs today's decision

Retrieval improved after archiving

Before the contraction, the deterministic retrieval test searched roughly 190.9 KB across 814 historical/current chunks and answered 7 of 9 current questions correctly.

After moving the eight studies into an explicit archive and adding one compact current closeout, the active corpus fell to roughly 75.9 KB and 163 chunks. The same test answered 9 of 9.

This is a useful distinction for Agent systems: retained evidence is not the same thing as default context. Keeping history is good. Making every historical model equally easy to treat as current is not.

Then we tried to delete working code

HP8 attacked two pieces of World that had once been justified by research:

• foreign_egress.py;
• effect_paths.py;
• their dedicated tests;
• three packaged contracts that only those research paths consumed.

No production consumer or fresh-Agent decision advantage remained. The files were deleted.

Production Python fell from 5,891 to 5,112 lines. Source files fell from 20 to 18. Packaged schemas fell from 28 to 25. Product tests fell from 139 to 121.

Those numbers are not the proof. The proof is what happened next.

The smaller World faced the same pressure

HP7 had already mixed concurrency, provider recovery, response ambiguity, stale conditions, same-Task inspection, and several NOT_COMMITTED families into twelve shuffled rounds: 96 invocations in total.

The pre-deletion World passed all 96. After HP8 removed the research-only APIs, the minimal World replayed the same 96-invocation mix and again passed all 96.

What World still owns

The contraction did not delete the idea that Agents interact with external reality. It clarified where the irreducible cross-owner facts live.

The current World keeps narrow responsibilities such as:

• typed cross-owner resources, messages, and entities when their relation itself matters;
• exact binding between a provider action and its consequence evidence;
• UNKNOWN plus exact-original reconciliation when an external result is unresolved;
• time-of-availability provenance for delayed observations;
• bounded Browser and provider integrity where multiple external objects must stay correlated.

Provider-native truth remains with the provider. Physical execution remains with Runtime. Task meaning remains with Host or the owning domain. Network mechanics remain with Workstation. World survives only where the relationship across those owners cannot be reconstructed safely from either side alone.

Deletion is not a ban

A deleted abstraction is not forbidden forever. World records explicit reopening conditions.

If a real multi-node workload later fails because direct owner adapters plus the retained World core cannot preserve a necessary cross-owner relation, the deleted capability can return. But history alone cannot resurrect it.

This makes contraction reversible without making the active architecture ambiguous.

The general lesson

Software projects often treat documentation, APIs, tests, and schemas as monotonic assets: once created, deleting them feels like losing capability. Agent-first systems have an additional cost. Every active concept competes for retrieval, interpretation, and decision authority.

A mature repository therefore needs two forms of memory:

Keep the historical evidence. Keep the current authority small.

World did not become more coherent by discovering a larger definition of “world.” It became more coherent by making fewer things eligible to answer the question “what governs this decision now?”

Primary record

World HP6–HP8

1. HP6–HP8 survival report
2. Current research closeouts
3. Exact acceptance evidence