IDialogDisplay interface, no knowledge of UI or the simulation loop), StartDialog(), implements IDialogDisplay), and DialogManager.instance.StartDialog()). The IDialogDisplay seam also covers a future debug/headless display for testing, mentioned but not built.GameStateVariables and builds a lookup dictionary per type on ready.GetValue( GameStateNumberVariable ), GetValue( GameStateBoolVariable )), so callers never touch the raw dictionaries.Assets/Scripts/Rokojori/Events/EventSlot.cs), so phases and dialog conditions can react without polling. The full set of variables can be serialized to and deserialized from JSON, for save/load.DialogManager, which any code can call directly. DialogPhase is just a thin wrapper so a dialog can also be one step in the Simulation Manager's turn loop.GameStateManager. The manager awaits one phase before starting the next.outro, skipping whatever was left - it doesn't wait for the current list to finish.DialogManager.instance.StartDialog( start ) and completes. All the real logic lives in DialogManager/DialogProcessor below, so dialog works the same way whether or not it's running inside a phase.GameStateManager on its own, and only talks to the outside world through the IDialogDisplay it was given - it has no idea DialogManager exists.PlayerChoice or DialogBranch can redirect the cursor to any other block instead, based on the option picked or a GameStateCondition.Locale with a Speaker; presentation (portrait, voice, animation) is handled by whatever implements IDialogDisplay.IDialogDisplay interface, DialogManager isn't the only thing that can drive it.How agents should reason, check in, and manage project knowledge when working in this project.
Read the first-layer pages listed on index.page. Give a brief confirmation that you understand the project and stop. Do not dive into board details or hunt for more context unprompted.
Wait for the user to direct next steps.
boards/tasks.page, boards/bugs.page, and boards/backlog.page are not part of the initial read unless the user directs it or a task clearly requires current board state.
After roughly 1 000 tokens of internal reasoning without a clear answer, pause and surface the situation to the user. The user is an expert and can often shortcut a long investigation with domain knowledge or a targeted hint.
Be brief and concrete. Name the specific problem, the hypotheses already ruled out, and what would help most. Offer concrete actions the user can take - open DevTools, check a log, paste an error.
The user has explicitly said so in the current session - e.g. \"just continue\", \"don't interrupt\", \"do the whole thing\". That permission is session-scoped and does not carry into the next conversation.
All persistent knowledge about this project - planned features, decisions made, open improvements, session notes - lives in workspace/ and is version-controlled. Agents must write project knowledge here, not into local agent memory files. The workspace is visible to the user, survives across machines, and is the single source of truth.
guides/actions/Give feedback when tasks become too large for a single session. Cleanups and documentation often need a follow-up session with enough context to do them properly. Communicate this rather than rushing or going silent.
When writing workspace documents, use the hyphen/minus character - instead of the em dash —. This applies to prose, lists, and task descriptions.
dotnet build against a project file. Useful when no one is around to press Play.Assembly-CSharp.csproj, with the error \"Your Windows doesn't fully support CET. Please install all available Windows updates.\" This is a Roslyn/Windows CET (shadow stack) incompatibility, not a project problem.global.json in the project root pins the SDK to an older installed version (8.0.417), which doesn't hit this crash:Assembly-CSharp.csproj is regenerated by the Editor and only lists files that existed at the last sync - it will not pick up new scripts written outside Unity. CompileCheck.csproj in the project root is a small hand-maintained sibling project for exactly this: it globs Assets\\Scripts\\Rokojori\\**\\*.cs and Assets\\Scripts\\Project\\**\\*.cs directly, referencing the same Unity DLLs, so it always covers whatever exists on disk.private, no parameterized constructors, avoid switch, and more. Read the guide.dotnet build instead of opening the Editor, including a fix for a SDK/Windows CET crash on this machine. Read the guide.IDialogDisplay interface, DialogManager isn't the only thing that can drive it.IDialogDisplay interface, DialogManager isn't the only thing that can drive it.Assets/Scripts/Rokojori/ (GameState/, Dialog/, Simulation/). This was written in one pass from this outline without a code review - see history/index.page for the session entry.SimulateWorld / ShowTurnStartConditions (only mentioned as examples, no code contract given) and any real UI for DialogManager.Show / SimulationRenderer.Enqueue - both currently placeholders (the former throws, the latter completes instantly), since Assets/UI is still empty.blocks as a flat ordered sequence and ignores each child's own inherited next field while inside the list - the list's authored order is what drives flow. This means DialogBranch/PlayerChoice aren't meaningful as direct DialogList members under the current implementation (their branch targets get silently ignored). Alternative interpretations were possible; this was the simplest that kept DialogList useful as an authoring convenience for grouping content nodes.action : GameStateAction field, executed when that option is picked. The outline listed Conditions and Actions as a pair but never named which DialogBlock triggers an Action - this seemed like the natural, and only, gap to fill it.GameStateBoolVariable flag, since there is no inventory/object system yet to check membership against.int, not a list of a \"Player\" type - no such type exists anywhere yet, and the outline's own turn-loop sample references players/player without ever defining what they are.GameStateVariable uses a separate key field for save-data identity rather than the outline's literal name field, since name is already inherited from UnityEngine.Object and shadowing it would be confusing.global.json pinning the SDK to 8.0.417 (the default .NET 10.0.401 SDK crashes compiling Unity's generated csproj on this machine - a Windows/CET incompatibility, not a project issue), and a hand-written CompileCheck.csproj that globs Assets/Scripts/Rokojori and Assets/Scripts/Project directly, since Unity's own generated Assembly-CSharp.csproj only lists files present at its last sync and won't pick up files written outside the Editor. All new code compiles clean against this (2 pre-existing, harmless serialization-analyzer warnings on EventSlot fields, unrelated to this session's code). This has only been compile-checked, never run in Unity - see the new \"Verify in Unity Editor\" board task.private fields (use public with an underscore prefix, or protected), no parameterized constructors (DialogProcessor changed to a static Create() factory), switch statements replaced with if/else-if chains (CompareInt, ListCondition), and explicit initial values added to all fields that lacked them.