GraphOS Skill: graph-world

Design world logic in GraphOS with a node-first architecture for any game or application.

This skill depends on graph-management for graph inspection and transaction apply APIs.

Use graph-world-ts after graph validation is complete whenever the task moves into npm/TypeScript project bootstrap, generated code integration, or runtime implementation of Systems and EventSystems.

Node Semantics

• World: Single root context of the whole model. The World node name is fixed to World.
• Context: Hierarchical domain/data model node under World or Context. Context belongs to the logical/data layer, not the presentation layer, but should expose the state that the View layer needs to observe. Context also has built-in storage semantics, so logic should prefer reusing existing Context instances/state before creating new ones.
• Variant: Typed variable definition under World or Context. Variant is the default design surface for persistent/stored runtime data.
• System: Lifecycle logic node under World or Context. Temporary cache or ephemeral working state should be handled inside the owning System rather than modeled as stored graph data.
• Event: World-level event definition. Event naming must encode its layer boundary: names starting with On represent presentation-layer events and should keep payloads minimal, ideally no payload; names starting with Logic represent internal logic-layer events and are reserved for world/domain orchestration inside the logic layer.
• EventSystem: Event-driven handler under Event.

Event Naming Boundary (Mandatory)