Skip to main content

Reference

The nexBash4 public global separates inspectable state from callable behavior:

nexBash
|-- state     read-only, frozen, serializable snapshot
|-- api       callable domain namespaces (control, config, observe, strategy)
`-- options   persisted player option flags
  • State reference: the frozen nexBash.state snapshot and its branches.
  • API reference: the callable namespaces under nexBash.api, plus the top-level accessors and helpers on the global.
  • Options & settings: the option flags, battlerage reserves, and the persisted settings document shape.
  • Events: the EventStream topics nexBash emits, and the host topics it reacts to.

Contract boundaries​

Everything under state is data — a fresh, deeply frozen copy built on each read, safe to inspect, stringify, or attach to a bug report. Everything under api is callable behavior. The Nexus eventStream global is the canonical listener boundary for other packages.

Two things are explicitly not part of the public contract:

  • nexBash.runtime — the internal mutable owner layer that state projects. Read state; do not read or write runtime.
  • nexBash.machines / nexBash.actors and the debug / attachDebug helpers — diagnostics, not a stable surface.