Skip to content

Acceptance Scenarios

Turn snapshot

Given a user turn with session history, working memory, a knowledge snippet, and a tool result, the implementation exports a context_envelope with a surface, selected items, a budget, an assembly, and an injection record.

Omitted context

Given five candidate snippets and a three-item budget, the implementation records the two omitted snippets and their omission reasons.

Compaction

Given a long session replaced by a summary, the implementation records source item refs, summary content or summary ref, coverage, loss notes, and replacement policy.

Tool-visible context

Given a tool that receives a resource ref not shown to the model, the implementation records a tool-targeted injection separate from model prompt injection.

Missing context

Given a task blocked by a missing file, the implementation creates a missing_context record with severity, requested source, blocked action, and resolution status.

Redaction

Given a selected item with private content, the implementation records redaction state, redaction method, policy refs, and a redacted assembly block.

Agent Runtime profile linkage

Given a runtime turn uses selected context, the context envelope preserves session_id, thread_id, turn_id, and applicable task/run ids. Runtime references the context by id, while context does not declare runtime completion, approval, or tool success. See Runtime profile test cases.

Draft standard for portable agent context surfaces, selection, budgets, injection, compaction, and missing-context facts.