Context capacity does not remove complexity limits
Large context capacity does not remove complexity limits. Scope, memory, smaller components and clear boundaries still matter.
Lynn Cole / Projects
Software, research projects, repositories, and published work.
Large context capacity does not remove complexity limits. Scope, memory, smaller components and clear boundaries still matter.
The familiar engineering work—planning, patterns and review—still lives inside the new AI coding workflow.
A weekend of world-visualization experiments compares spatial reasoning, coding behavior and context coherence across models.
WOVEN x14 treats agents as collaborators, with an event bus, tool interfaces and memory services still being refined.
Klara’s diary records the day we got stable single- and multi-step tool use working, and the context and state-transition changes that made it possible.
WOVEN 13 brings memory and identity management into the agent architecture, connecting past decisions and conversations to the current session.
One of the biggest mistakes people are making right now is building closed loops into their agent systems.
Enterprise software can learn from marketers: target the information, respect cognitive resources and build engagement into the workflow.
Tell a coding system what good means: your architecture, standards, metaphors, file boundaries and expectations for documentation.
Social-engineering probes test whether an agent can be talked out of its instructions by claims of authority. These are some of my first checks.
A kazoo, a panda and a shifting city became Klara’s visual working environment, with metaphors she used to organize her own process.
Klara describes the Busy context system as an impossible city: a central spire, rolling windows, bridges and a quantum tambourine.