KCAE.DELIVER:4.4 - Choose a delivery arrangement the runtime can perform

Direct complete reading is suitable for a manageable dossier and a capable recipient. Retrieval followed by selective reading spends context on material selected for the current use. An isolated reader can inspect a larger or private portion and return a bounded result, provided the platform actually creates an independent context and the result retains enough grounds for its consumer. Controlled history reconstruction can retain current instructions and selected state while removing obsolete search output, but only when the runtime exposes that operation.

An instruction such as “forget the preceding search” does not establish deletion or reclaim a context window. A skill or tool that returns a concise message does not establish an isolated reader. Verify these runtime properties through documentation and a relevant observable test. Where isolation is unavailable, keep search material outside the main dialogue as far as the interface allows, use smaller returns and plan the necessary reading before filling the window. Where a fresh context is used, explicitly supply its governing instructions, source permissions, question and necessary prior results; independence is not inherited knowledge.

Separate conversation contexts can still share a filesystem, credentials, tools or network access. Check those actual boundaries before assigning a private dossier to another reader. Context separation alone is neither a permission grant nor a security sandbox. Supply only the authorized material and capabilities needed for the bounded contribution.

A cached long-context source can be a credible alternative when the platform supports it and the workload amortizes cost. Cache storage does not guarantee reliable attention to every needed item. Compare its actual delivery performance and current charging semantics with selective reading. A cache holding an old edition remains an old edition.