Two public parts of one system.
The RSOS Language is where programs are written, checked and run. The RSOS Multimodal Cue Framework is one host the language compiles to: the body layer. Each has its own site, release line and evidence, and they connect through one narrow interface.
RSOS Language this site
The language, its operators and grammar, the compiler with consent and harm checks, the White Dragon engine, the communication layer for AI agents, the mental-model builder, the painting editor and the keyboard.
Evidence: pre-registered tests on real LLM agents (A1–A3b) and the first human test (HT1). Software 0.2.1 · 10.5281/zenodo.24321030
RSOS Multimodal Cue Framework
The body layer: vibration codes, cognitive states such as Owl and Eagle, schedules and conditioning through visual, auditory and kinesthetic channels, with its own devices, protocols and runtime.
v2.1.0 · 10.5281/zenodo.24301903
Visit the cue framework site ↗How they connect
Three statements carry a program across the boundary, and one rule set is shared. Everything else stays on its own side.
| In the language | On the cue framework |
|---|---|
CUE eagle CODE "-.." CHANNEL kinesthetic | An RSX code for a state, on a channel |
MESSAGE owl TO architect STATE needs_input | A state signal from one part to another, as an RSX code |
PERSPECTIVE guardian eagle | A NODES cognitive state |
| Consent and harm checks | The framework's own Spine, safety modes and hash-chained audit log, loaded read-only |
In practice
Person-facing output needs the cue framework's governance. Without it, the compiler warns (W005) that the output must not be used on a person. With it, a program compiles to a session.
# point the language at the cue framework
RSOS_CUE_FRAMEWORK=/path/to/RSOS-Multimodal-Cue-Framework \
python -m rsoslang session examples/healing.rsl
Why two sites
Different evidence
The language's results are about AI agents and human input; the cue framework's are about the body layer. Kept apart, each claim stands on its own data.
One architecture
The cue framework is a compile target of the language, not its container, so the language can target other hosts the same way: agents, teams, organisations.
Independent releases
Each has its own version, DOI and changelog, and can be cited on its own.