TASK
Prepare a discovery brief for a client-file collection service, using only these notes.

[D1] Each request specifies six required files and a named internal owner.
[D2] In request R204, three files are accepted, two are missing and one needs clarification.
[D3] The client should know exactly what remains and whether a replacement was accepted.
[D4] Staff currently rename attachments and update a tracking spreadsheet.
[D5] A reviewer decides whether evidence satisfies a requirement. An upload is not approval.
[D6] The team has not agreed how to handle a requirement that changes mid-request.

OUTPUT
1. The business outcome and the evidence that would show progress.
2. A table separating enduring policy, current workflow and local workaround,
with note IDs and unresolved questions.
3. A capability map: capability, responsible role, authoritative record and
first useful delivery slice. Keep it independent of technology choices.
4. Acceptance examples for R204: what the client sees and what the owner can decide.

BOUNDARIES
Do not assume six uploaded files completes the request. Do not automatically
turn attachment renaming or a spreadsheet column into a product requirement.
Ask which file-handling rules have a business or legal reason before preserving them.