# answers.md · dara/icarus

[View on GitCafe](https://git.cafe/dara/icarus/blob/capture-shared-client-fix/answers.md)

Repository: [dara/icarus](https://git.cafe/dara/icarus)

Visibility: public

Requested revision: refs/heads/capture-shared-client-fix

Commit: 088055b051a05710ea8e2f68673963bc7f1b7e03

Blob: 9c7266fd6f9916b45b69f2a66d0c16412818bbb0

Size: 1144 bytes

[Immutable source](https://git.cafe/dara/icarus/blob/088055b051a05710ea8e2f68673963bc7f1b7e03/answers.md?format=markdown)

```
# Reporting investigation results

After an audit, investigation, or substantial testing run, explain the outcome
directly in your reply to Dara. Give enough context to understand the result
and decide what to do next without opening a file.

Before ending the reply, answer:

- What did you find, what supports it, and why does it matter?
- What changed, what did you verify, and what do those checks establish?
- What remains uncertain, unfinished, or blocked, and why?
- What should we do next, in what order, and why do you recommend that path?
  Identify any decision or information needed from Dara.

Separate confirmed findings from hypotheses. Distinguish a working test tool
from evidence that the application or game behaves correctly.

Use plain language. Include technical details and numbers when they help explain
the result or choose the next action. Match the explanation to the complexity
of the work.

Keep the essential explanation in the conversation. Link reports, logs, images,
and videos as supporting evidence. The reply is complete when Dara can understand
what happened and what happens next without reading a README.

```