Work in public. Break it before we brag about it.
The project is currently in prototype and test-hardening territory. The focus is not feature count. It is proving that the underlying rules survive hostile tests.
Mounted model + runtime separation
Prototypes have demonstrated a mounted model being read by a separate runtime process with persistent state surviving reconnects.
Persistence and decay tests
State retention, decay behavior, activation thresholds, and dormant-but-nonzero traces are being tested under controlled timing.
Simultaneity / collision hardening
Same-moment conflicting events are being treated as a first-class architectural problem instead of being silently flattened into ordinary sequencing.
Provenance hardening
The runtime is being pushed toward rejecting state changes that cannot prove a lawful source, path, and eligibility relationship.
Next: broader host integrations
Once the core runtime laws are stable, the same model behavior can be tested in richer game, mobile, and simulation hosts.
Expect things to change.
Names, interfaces, file formats, benchmarks, and implementation details can move as the architecture gets attacked and refined.