Optional spec layer

When you need structured events, rules, or tests, start a file with spec instead of say lines. Stage 1 uses the same brace-free style as scripts:

Keyword	Role
`spec`	Name and version
`state` / `config`	Fields with `name type is default`
`entity`	`entity Name keyed by id` and indented fields
`event`	`event E with arg type`
`output`	Declared outputs with indented parameters
`on`	Handlers: `on E with args if condition`
`rule`	`when` / `otherwise` and `set` / `emit` / `reject`
`machine`	`from to to` transitions
`invariant` / `limit` / `test`	Optional properties and tests

Tests interleave send and expect lines in order:

test adds_one
  send Tick
  expect count is 1
  send Tick
  expect count is 2

You do not need this layer for simple tools — use say scripts and romit run when that is enough.

Keyboard shortcuts