Architecture overview (5.0)

GridBuilding 5.0 is best understood as a node-first plugin with a composition-container / injector integration style.

Boundary (5.0)

• Godot nodes + scripts
  • Own most runtime behavior.
  • Public API is primarily node exports + signals.
• Composition container + injector
  • Wiring layer that assigns settings/services/state into nodes.
• State-first coordination
  • Many listeners consume state directly (polling or state references in signals).
  • 5.0 does not consistently separate event payloads from state.

High-level shape

1
2
3
4
5

Godot nodes / scripts
  ↓
Composition container + injector
  ↓
Backend state + (legacy) bridge patterns

What 5.0 optimized for

• Fast adoption: add nodes to a scene, connect signals, configure exports.
• Direct debuggability in the editor: follow node references in the inspector.

What 5.0 did not standardize (later improved in 5.1/6.0)

• A strict, explicit split between:
  • service-owned state
  • event payloads
  • diagnostics snapshots

5.1/6.0 improve this by introducing a clearer boundary where:

• signals/events carry small payload objects (EventData)
• snapshots exist for diagnostics/tests
• internal state stays private to services