RSOS

RSX-V, the command layer above RSX

An RSX-V command is a typed, staged and audited set of vector operators. It compiles into an RSX program, which compiles into a timeline and the lines a wristband plays. One program therefore exists in three forms, and each form can be checked against the next.

message → RSX-V command → RSX cue program → timeline → device lines → firmware

One program in three forms

Loading the example…

1. RSX-V command

Vectors, a gate, staged phases with conditions, laws

2. RSX cue program

Written by the bridge; tiers, breath, phases, cues

3. Device lines

What the wristband receives (RSOS Device Protocol)

What RSX-V adds

Typed vectors

34 operators, each typed by the cognitive layer it acts on (C1–C11): the canonical 17-vector set, extended operators, Vector 0 NullSafe and operators that reach layers no earlier operator reached.

A gate and staged phases

A gate runs first. Each phase has conditions on body state and layer activation (IF, ELSE, UNTIL, MIN, MAX), and at most 17 vectors run at once.

Ten laws

Among them a simulation before every live run (GhostPass), consent (ConsentStack), separation of conflicting operators (InteractionMatrix), time windows (ChronoGate) and a hash-chained log (ResonanceAudit).

Measurement and NEXT

Every vector is audited for agency, distress, drift and layer activation. NEXT writes the successor command from the measured result and upgrades older vector commands.

Translator

A message becomes vectors and then a complete command. Each operator keeps a link to the clause of the message it came from.

The same safety

The bridge compiles to RSX, so the RSX limits, the Watchdog and the output gate apply unchanged. A command carries a guidance level (self-guided, structured or clinician-led) that the program it compiles to keeps, that NEXT never lowers and that the Watchdog checks against the domain before a run. The archetype agents are governed by the same Spine and Watchdog as the person side.

Status. Built and tested. Every result comes from simulation, the firmware core in the host simulator or hand-coded validation; none comes from people.