Recent Decisions
Last reviewed: 2026-06-30
| Date | Decision | Reason | Source references |
|---|---|---|---|
| 2026-06-30 | Document Unity renderer docs under docs/core and operational maps under docs/state. |
Mirrors Anuva implementation-doc pattern while separating durable architecture from current repo state. | This documentation generation pass. |
| 2026-06-30 | Treat PresentationController as the current main runtime integration boundary. |
It owns config loading, playback, capture, bot motion, camera, and Python render handling in code. | Assets/Anuva/Scripts/PresentationController.cs |
| 2026-06-30 | Treat PresentationConfig.cs as a partial consumed model, not the full sample JSON schema. |
Sample config contains fields not represented in the C# model. | Assets/Anuva/Scripts/PresentationConfig.cs, Assets/StreamingAssets/PresentationConfig.json |
| 2026-06-30 | Cross-check Unity protocol docs with Python Server UnityProtocolMap.md. |
Protocol ownership spans Unity and Python; drift breaks render orchestration. | C:/Anuva/dev/anuva-python-server/docs/state/UnityProtocolMap.md, Assets/Anuva/Scripts/AnuvaPythonServerCommunication.cs |
| 2026-06-30 | Mark production scene/build entry as a known gap. | Build settings enable SampleScene, while Anuva renderer scenes live under Assets/Anuva/Scenes/. |
ProjectSettings/EditorBuildSettings.asset, Assets/Anuva/Scenes/ |
| 2026-06-30 | Document both legacy Vuplex/Reveal and generated virtual-screen paths. | Both are present in source/assets; only one would be misleading. | VuplexRevealBridge.cs, AnuvaVirtualScreensPlaybackController.cs, AnuvaScreenHtmlBuilder.cs |
| 2026-06-30 | Do not document dynamic bot/set loading as implemented. | Config fields exist, but runtime prefab selection by IDs was not confirmed. | PresentationConfig.cs, scene serialized assets |
| 2026-06-30 | Treat C:\Anuva\Capture as current default, not a portable contract. |
It is hardcoded/serialized but should be overridden for worker environments. | PresentationController.cs, Anuva scene YAML |