# Investigating a working system for a single task

First compare the map of the operational documentation with what you already have. This file helps you investigate one scenario, identify gaps, and prepare confirmed content for the appropriate Confluence pages. Code can suggest behavior, but it does not by itself explain the historical reason for a decision.

## Connection to the system documentation

- Documentation home page in Confluence: **[to be completed]**
- Pages we will complete through this investigation: **[to be completed]**
- Who will confirm the content and keep it current: **[to be completed]**
- Where the remaining gaps appear in the existing plan: **[to be completed]**

## Scenario boundary

- User or operational scenario: **[known: … / to be determined]**
- Reference version or state: **[known: … / unknown]**
- Reading scope: **[known: … / to be determined]**
- Out of scope: **[known: … / to be determined]**

## Evidence

| Area | What we found | Evidence: link, version, test, or source person |
| --- | --- | --- |
| Code and behavior | [known / not found] | [to be completed] |
| Tests and their result | [known / not found] | [to be completed] |
| Domain rule and its reason | [known / unknown] | [to be completed] |
| Dependencies | [known / unknown] | [to be completed] |
| Data: input, storage, recipient | [known / unknown] | [to be completed] |

## Stop when something is uncertain

| Contradiction or question | What is missing | Who can confirm it | Status |
| --- | --- | --- | --- |
| [to be completed] | [to be completed] | [to be determined] | open / clarified |

## Record one real discrepancy

If the documentation and the application behavior agree, record the verification result. Do not invent a contradiction just to fill in the table. If you found a difference, the agent should prepare this record:

| Element | What to enter from your investigation |
| --- | --- |
| Documentation | The specific rule, link, and page version |
| Behavior | Input data, action performed, result received, and application version |
| Code | The file and function responsible for this result, after reading it |
| Unknown | Is the current behavior a defect or an undocumented decision? |
| Question and owner | What needs to be resolved, and who knows the rule or its reason |
| Next step | Where we will record the answer and which task needs it |

Unknown fields remain explicitly incomplete. If the application or a test has not been run, code alone is insufficient to mark something as “verified.”

**Finished outcome:** a second practitioner can go through the scenario, show the evidence, and say what they still do not know. Once agreed, the agent prepares content for Confluence or updates the named page only with the appropriate access and instruction.

## Prompt for the investigation

```text
Read this file and only the permitted sources: [links]. Complete the evidence
for one scenario. For every fact, record the source, version, or person
who can confirm it. Separate code, test, documentation, and assumption.
List contradictions and questions; do not resolve them by guessing and do not edit
the source pages. First show the completed text for agreement.
Do not change files, Confluence, accounts, permissions, environments, or external services.
```