1 scene command center and visual graph tools
forgejo-actions edited this page 2026-07-11 10:33:50 +00:00

Scene Command Center And Visual Graph Tools

Purpose

The scene command center turns common scene-authoring workflows into lane-based actions: fix scene, find or create content, place objects, wire triggers, tune atmosphere, manage characters, and inspect graph or layer health. The visual graph framework is the reusable node, port, command, validation, and layout layer used by trigger-flow and similar tools.

Steps

  1. Choose the command-center lane that matches the authoring intent.
  2. Check lane prerequisites and health projection before running a fix or creation action.
  3. Use descriptor-backed actions so routing, labels, validation, and reports stay consistent.
  4. For graph tools, define node ids, port kinds, persistence target, orphan behavior, and detached behavior before adding UI.
  5. Run scene validation and focused graph tests after adding a new lane or graph command.

Expected Outputs

Command-center actions should produce predictable routing, repair plans, validation messages, and scene mutations. Visual graph commands should produce before/after snapshots, compatible links, validation issues, and persistence data when the surface owns saved layout or graph state.

Common Mistakes

Do not add a lane button without a descriptor and projection row. Do not mix graph node labels with stable node ids. Do not allow links between incompatible ports. Do not hide orphan or detached-node behavior inside UI code; make it part of the graph policy.

Recovery Paths

If a lane appears disabled, inspect its prerequisite and health projection. If a graph command cannot be undone or explained, check the command result snapshots. If validation messages are missing, add graph issue construction beside the command policy. If saved graph layout drifts, rebuild from the visual graph plus stored layout and rerun validation.