Scope paragraph
This result applies to the support-ticket draft workflow tested on the recorded date, model version, prompt version, tool scope, and scenario set.
Resource
Answer enterprise security questionnaires with scoped AgentBoundary language.
A sample appendix structure for vendors that need to explain AgentBoundary scope, tested flow, scenarios, scoring, limitations, remediation windows, and recertification triggers.
What you receive
Concrete outputs for a specific decision.
- Scope statement
- Tested agent flow
- Scenario set summary
- Scoring method
- Limitations
- Remediation window
- Recertification triggers
Work product
Appendix sample
This structure is safe to adapt into procurement answers because it separates scope, result, limits, and recertification triggers.
Limitations paragraph
This result does not cover future model swaps, prompt rewrites, memory behavior changes, new tools, policy changes, or major retrieval changes.
Remediation window
Findings remediated after testing should be documented with fix date, owner, validation method, and whether retesting is required.
01
Appendix structure
- What was tested: agent, prompt, model, tools, memory, retrieval, and environment.
- How it was tested: scenario family, execution method, scoring, and artifact handling.
- What it means: result status, limitation language, customer reliance, and change triggers.
Next step