Results and evidence
| Term | Meaning |
|---|---|
| Run | A recorded implementation attempt associated with a task and working location. |
| Worker report | The model’s account of its work. Read it alongside changes and observed checks. |
| Command outcome | What a launched process reported, including its exit and available output. |
| Build result | Evidence from the selected build operation and its recorded inputs. |
| Artifact/output | The files produced by that operation. Supporting files may be essential. |
| Needs review | A completed result without a later explicit result review. |
| Result review | A decision about the displayed result, not an automatic merge or issue closure. |
| Simulated | Example data used to demonstrate the interface, with no real worker or engine execution. |
Current, changed and missing
Section titled “Current, changed and missing”A recorded result belongs to particular inputs and output. If either changed, the earlier evidence remains useful history but cannot silently represent the new files.
Before Open result, GDE checks the recorded location and output. A missing sidecar can make a player incomplete even when the executable exists. A changed artifact should be rebuilt or inspected through a new result rather than attributed to an old successful check.
For Unreal, an Editor target and a packaged player are different deliverables. Godot may use an external PCK; Unity uses a data folder and runtime files. See Engine capabilities.
Completion has several meanings
Section titled “Completion has several meanings”An issue can be Done while its latest result still needs review. A model turn can finish while a required test was not run. A build can succeed while input, visuals or gameplay remain untested.
Read the individual observations. Do not infer acceptance from a green command, a closed card or an available launch button.
Unknown delivery
Section titled “Unknown delivery”When a request may have reached a provider but its outcome is unknown, GDE keeps that uncertainty and the pending writing. Check the authoritative outcome before resending. This prevents an interrupted reply from becoming two issues, comments or implementation requests.
For a practical sequence, use Review an implementation.