Gameplay and interactive simulation patterns built on canonical uDOS state.
- gameplay-facing modules
- interaction experiments
- educational samples around spatial or stateful flows
- canonical runtime ownership
- networking ownership
- general-purpose shell ownership
src/docs/tests/scripts/config/examples/
Keep experiments modular and grounded in stable public contracts.
Gameplay should consume family contracts without redefining them.
Gameplay treats uDOS-grid as the canonical spatial source for place and
artifact truth.
The repo activation path is documented in docs/activation.md.
Run the current repo validation entrypoint with:
scripts/run-gameplay-checks.sh