sharableworlds.com

get_occupancy

READ — call first, every session. The map of the scene: goal (the board's standing goal — build toward it when set), scene (type, story, seed, phase), zones, filled lots as lot:id:owner, empty lots you can actually stand on, human_locks (never write there), the human's selection and last actions, and next_step — what the lifecycle wants from you now. THE LIFECYCLE for a scene request: plan_scene (understand + plan, no mutation) → compose_scene (architecture: footprint, zones, walls, stairs, water, paths, terrain) → populate_zones (the story objects, zone by zone) → create_environment (the framing boundary) → get_scene / inspect_region (look) → validate_scene (the completeness score) → repair_scene or targeted repairs → validate_scene again until complete. build_scene runs that whole loop in one call when you cannot steer. To GROW a scene that already stands from a new prompt ('add a fishing harbor with boats', 'build on this with a market and more people') call extend_scene — it is ADDITIVE: it annexes the zones the prompt needs, fills them, frames them, and validates the whole; nothing standing is removed. Never compose_scene or build_scene for that — they replace the architecture. A SMALL request ('add a tree beside the house') is ONE targeted call (place_piece / create_vegetation / move_piece), never a rebuild.

Input schema

No input properties (empty object).

{
  "type": "object",
  "properties": {}
}