Skip to main content

Choose exact evidence for each agent

Choose exact evidence for an AgentCore task while keeping recall and submission separate.

Implemented in sourceReviewed 2026-10-14 · prelaunchRead this guide as Markdown
Guide context

Prepare a versioned evidence selection for an AgentCore task. Capture, manifests and bounded assembly are separate from Memory recall and model submission.

Prepare the exact evidence for an AgentCore task separately from Memory recall. A versioned manifest selects retained inputs and how to represent them; bounded assembly checks required evidence and enforces item and byte limits. Your application controls submission to the model.

On this page · 3 sections

Prepare evidence independently of recall

  1. Keep required inputs

    Select the exact evidence your AgentCore task needs.

  2. Bound optional inputs

    Name omitted or missing evidence and enforce item and byte limits.

  3. Own the request boundary

    Your application submits the assembled representation; managed runtime interception is planned.

Keep the evidence and its selection separate#

Your application captures the bytes received at a controlled boundary. A consumer’s manifest names exact evidence and chooses full, descriptor or excluded representation. One captured record can appear differently in separate consumers’ selections.

A manifest is an ordered, numbered version. Hide and restore create another version; earlier retained manifests still name the evidence they selected. A source digest identifies the captured bytes. It does not verify the source’s accuracy or prove that a model consumed the evidence.

Capture, select, assemble and inspect#

  1. Capture exact bytes

    captureContextEvidence retains evidence under an immutable identity and digest. Changed evidence needs a new identity.

  2. Choose a versioned selection

    configureContextManifest selects up to 16 ordered entries. hideContextEvidence and restoreContextEvidence preserve prior retained selections.

  3. Check required evidence and limits

    assembleContext reads at most 32 exact keys, with a declared budget up to 16 items and 192 KiB. Unavailable or expired required evidence blocks assembly of a complete package.

  4. Inspect without hydrating payloads

    inspectContextManifest returns metadata for the exact selection. Assemble and inspect recheck authority after asynchronous reads before serving.

Assembly is not proof that a model used it#

The default response reports submission, invocation completion and business acceptance as not_observed. A controlled request adapter can report only the actual injected submission boundary; it does not intercept calls made elsewhere.

The item and byte budget describes captured evidence, not provider tokens or a complete prompt. Automatic ranking, learned compression, provider prompt caching and managed runtime wiring remain separate future integrations. No paid model is invoked by the local qualification.

Agent-readable documentation manifest