Progressive context begins with a compact index of available information. The agent selects relevant sources and loads details incrementally to keep active context focused.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Progressive context gives a system only the context it needs at first and expands it step by step when the task requires more information.
The approach comes from designing information-rich systems and was described for agentic applications as Progressive Context Disclosure. Thoughtworks presents it as a technique for controlling context size and cost according to actual need.
An agent first receives a map rather than the whole archive. When needed, it opens the next drawer, checks relevance, and retrieves further detail. The working context stays focused.
Information is provided in task-appropriate layers.
The task triggers the next context step.
Unneeded detail stays outside the working context at first.
Progressive context reduces overload, latency, and unnecessary processing in knowledge-intensive systems. It fits staged information access; late retrieval can slow decisions or hide important clues.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.