RSOS Language
RSOS: an executable spatial-symbolic language for human–AI and AI–AI communication. Whitepaper: R. A. Elu (2026), doi:10.5281/zenodo.24304403 (all versions). Code: Apache 2.0. Software release 0.2.0: doi:10.5281/zenodo.24317658.
RSOS State Runtime: 2 model calls instead of 42
For multi-agent workflows that edit shared state. The model decides; the language executes. On real LLM agents (pre-registered, every failure reported): a 14-step task in 2 model calls instead of 42, 2.8–3.7× cheaper than the best setup built for the same agents at API prices, 8× faster, 32/32 correct, every injected drift healed with zero model calls. When agents compute from their own copies, a Slipstream-style anchor protocol got 0 of 16 tasks right; RSOS stayed right.
pip install rsoslang # or, from a clone: pip install -e .
claude mcp add rsos -- rsoslang mcp # or with no install: claude mcp add rsos -- uvx rsoslang mcp
python experiments/a5_runtime_equivalence.py # from a clone: this runtime replays every measured plan, 32/32 match
Drop it in (Python or MCP) → · Replicate it, under $1 → · All results, failures included →
A spatial-symbolic programming language for humans and AI. You write a program the way you think it: objects in a scene, placed, touched, pierced, entered, coloured, connected by lines, kept in the rooms of a house. The same program runs in two places:
- in a machine: an AI agent workflow, a simulation;
- in a person: a practised mental model, delivered as a timed session of images, words, sounds, scents and vibration codes.
Open the editor → A real 12-module support agent, painted. Put a guest at the head, heart, brain or beside a module, and see the measured effect.
Results (17 Nov 2026, pre-registered, real LLM agents; whitepaper v2: doi:10.5281/zenodo.24320392): a protocol designed by the RSOS White Dragon engine (A3b) used 0.55× the BPE channel tokens of a Slipstream-style anchor protocol while keeping every copy of the shared state true in 16/16 tasks (anchor protocol 0/16) and healing every injected drift without a model call. The White Dragon also redesigned a weak agent system, cutting errors by 63% (A2). Of 27 predictions on real hosts, 18 passed and 9 failed; all are reported.
First real-host test (A1, 17 Nov 2026, pre-registered): three LLM agents (planner, worker, checker) on 8 tasks. The RSOS palace protocol used about 7× fewer channel tokens than JSON with full state (2,563 vs 17,311), finished 7/8 tasks exactly correct (JSON 5/8), and caught and healed 24/24 injected drifts with 0 model calls (38 tokens per repair). Summaries + retrieval: 0/8 correct, 24/24 drifts kept. One model family, 8 tasks. Report: experiments/A1_REPORT.md.
Purpose
RSOS grew from one seed: healing, transforming, signalling and evolving. It integrates the whole of human
experience, including its shadow, so that what is integrated can be transformed rather than denied. Because its seed
is healing, RSOS is used with consent and for the good of the person or system it works with, never to harm or
coerce. See RESPONSIBLE_USE.md,
GOVERNANCE.md, CONTRIBUTING.md and TRADEMARKS.md.
What makes it different
-
Where you place an operator decides what it does. The same spell corrector placed at a module's head, heart, brain or beside it gives four different results, measured on held-out data.
-
Meanings in three tiers.
- a fixed core, shared by everyone;
- declared variations, scoped to a person, host, world or state;
- meanings left open on purpose, found by search.
Nothing changes silently.
-
The host decides. Every operation runs on a declared host with its own channels and states. A cue on a channel the host does not have is an error.
-
Safety is in the compiler. Person-facing operations need consent and pass a constitution of seven checks; return to baseline is always available.
-
Every result is reproducible. Pre-registered experiments, seeds, result hashes; negatives published with positives.
Quick start
pip install -e .
python -m rsoslang check examples/robot_head.rsl
python -m rsoslang ir examples/sol_remote.rsl
RSOS_CUE_FRAMEWORK=/path/to/RSOS-Multimodal-Cue-Framework python -m rsoslang session examples/healing.rsl
./reproduce.sh
Use it from Claude or any MCP assistant
{"mcpServers": {"rsos-language": {"command": "python", "args": ["-m", "rsoslang.mcp_server"],
"env": {"RSOS_CUE_FRAMEWORK": "/path/to/RSOS-Multimodal-Cue-Framework"}}}}
The tools are rsos_statements, rsos_check, rsos_compile, rsos_session, rsos_paint_workflow,
rsos_apply_gestures and rsos_paint_graph.
Results
See results/BUILD_REPORT.md. It covers every pre-registered test, the ones that failed included.
Licence
Apache 2.0. Research and development software; not a medical device.
Metadata
Release files for rsoslang 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rsoslang-0.3.0.tar.gz | 94.9 kB | Without provenance | Details for rsoslang-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rsoslang-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for rsoslang-0.3.0-py3-none-any.whl |
Total release size: 185.5 kB
Release files / rsoslang-0.3.0.tar.gz
| Download URL | rsoslang-0.3.0.tar.gz |
|---|---|
| Size | 94.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5be0685caec533a86cb34752af6e71acd0b57ac294fa2893ec1789f2f12c7fc6
|
|
BLAKE2b-256 checksum How to use checksums |
77c7e53c532ed77055cab0c51a2ba2050ddd4757505f4fe335350ab443f7a157
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Release files / rsoslang-0.3.0-py3-none-any.whl
| Download URL | rsoslang-0.3.0-py3-none-any.whl |
|---|---|
| Size | 90.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00c6ced8b6d2ddcb80f3e23dc1864c4bdab53b8cceffd689a53368c9b0edf610
|
|
BLAKE2b-256 checksum How to use checksums |
9bcb063888448fb86d5d3d47ba41b13265831f42b27e5a1ea35d9e869d85612e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Security for rsoslang 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.