3.8 — Progressive Discovery vs Monolithic Context

CCAR-P Domain 3 · Task 3.8

What You Need to Know

Two ways to load tools, procedures and knowledge:

• Monolithic — load everything upfront (simplest; best for small stable surfaces; cacheable)
• Progressive discovery — load each piece on demand (Skills, deferred tool loading, agentic retrieval)

Progressive Disclosure Mechanisms

• Skills — metadata always; body on trigger; resources on read
• Deferred tool loading — catalogue behind search; only discovered schemas enter context
• Agentic exploration/retrieval — keep lightweight identifiers; load content as questions arise

Four Decision Cues

1. Surface-to-slice ratio — large surface, small per-request slice → discovery
2. Frequency — nearly every session → upfront (cache); long tail → discovery
3. Latency — each discovery hop is a round trip; tight budgets cap hops
4. Stability — stable content upfront compounds with caching; volatile content behind discovery

The Hybrid Is Usually the Answer

Small, stable, hot core monolithic and cached. Long tail behind discovery (tool search, skills, retrieval). Vendor-documented default: keep the handful of most-used tools loaded, defer the rest.

Key Concept: Capacity is not a strategy. Decide by the four cues, never by “the window is big enough”.

Exam Traps

• Loading everything because the window is big enough
• Keeping every tool/runbook in the prompt and relying on a cache breakpoint
• Capping tool count permanently when the surface must grow
• Deferring everything, including tools nearly every session uses