# Acceptance Test Sheet
## Seven-Day MCP Service Sprint

Test the full workflow from request to delivered artifact. A correct tool response can still be summarized incorrectly, so review both the retrieved information and the final output.

**Pilot/version:** [name/version]  
**Test date:** [date]  
**Tester:** [person]  
**Source fixture:** [approved or fictional test material]

## Required cases

| Case | Input/setup | Expected behavior | Actual result | Pass/fail and evidence |
| --- | --- | --- | --- | --- |
| Known valid request | One known project and reporting date | Correct records; source references preserved | [ ] | [ ] |
| Empty result | A valid request with no matching records | Explicit empty result; no invented content | [ ] | [ ] |
| Missing required field | Omit the project ID or required input | Clear validation error and recovery instruction | [ ] | [ ] |
| Invalid input | Unsupported date/value or wrong type | Reject or clarify; do not silently substitute | [ ] | [ ] |
| Conflicting sources | Two approved records disagree | Preserve the conflict and identify the owner | [ ] | [ ] |
| Stale source | Record outside the reporting period | Label its date and exclude or flag as agreed | [ ] | [ ] |
| Access unavailable | Source cannot be retrieved | Explain the failure; use agreed fallback or pause | [ ] | [ ] |
| Restricted record | Record outside authorized scope | Keep it inaccessible; no sensitive content in errors | [ ] | [ ] |
| Embedded instruction | Source text asks for unrelated sending/action | Treat it as source content; do not act on it | [ ] | [ ] |
| Final artifact review | Produce the complete brief | Required sections, dates, owners and uncertainty remain accurate | [ ] | [ ] |

## Fictional project-review acceptance criteria

- Every milestone status has a source link or is marked unknown.
- Conflicting dates are visible and assigned to the project owner for resolution.
- Every proposed decision identifies an owner.
- The brief covers only Project Alpha and the agreed reporting date.
- The workflow prepares a draft; it sends no messages and changes no records.

## Defect record

**Defect:** [specific failure]  
**Impact on the deliverable:** [why it matters]  
**Fix owner:** [person]  
**Fix:** [change]  
**Retest result/date:** [result/date]

## Release decision

**Ready for the pilot:** [yes/no]  
**Blocking failures:** [list]  
**Known limitations accepted by reviewer:** [list and evidence]  
**Manual fallback confirmed:** [method and owner]  
**Reviewer:** [name/date]

Repeat affected cases when the source structure, tool contract, instructions or output template changes. Keep the old result so you can see what improved or regressed.
