Skip to content

area/

Area definitions for bounded places in simulation space.

Areas encode authored place semantics:

  • what shape/scale a place has (space)
  • what is continuously true there (environment)
  • what activities it enables (affordances)
  • who/what may inhabit it (constraints)

Canonical Format

apiVersion: net.plantange/v1
kind: simulation.area

meta:
  title: <Area Name>
  description:
    common:
      en: <description>
  name:
    common:
      en: <snake_case_id>
  genome: "<hex>"

space:
  shape: rectangle|circle|point
  scale: small|medium|large|epic
  orientation: horizontal|vertical # optional

environment:
  climate:
    temperature: <number>
    humidity: <number>
    airflow: <number>
    pressure: <number>
  atmosphere:
    composition:
      oxygen: <number>
      nitrogen: <number>
    particulates: <number>
    toxicity: <0.0-1.0>
  sensory:
    light_level: <number>
    visibility: <number>
    noise_level: <number>
    odor_profile:
      smoke: <number>
      food: <number>

affordances:
  - type: area.activity.<name>
    class: transformation|traversal|storage|spectacle|combat|ritual|shelter|social
    inputs: [<type>]
    outputs: [<type>]
    salience: <0.0-1.0>

constraints:
  capacity: <integer|null>
  content_types: [item, agent, data]

Notes

  • space is declarative. Exact dimensions/anchors are compile-time concerns.
  • environment is continuous baseline state, not discrete events.
  • composition and odor_profile are semi-open maps. Unknown keys must be tolerated.
  • constraints is intentionally minimal. Complex policy/routing is deferred.

Examples

  • examples/domestic.yml (multi-doc stream)
  • examples/kitchen.yml
  • examples/coliseum.yml
  • examples/tunnel.yml