RSOS

Nothing in RSOS starts unchecked

CONTAIN is the safety layer every part of RSOS asks before it acts: the player before a run, the heart-rate trigger before an offer, LINX before an AI proposal changes a plan, the node studio before a plan is approved. It can allow, block or pause, and it always says why. It also watches every program and node over time, and pauses one that stops helping.

What it checks, in the order it checks it, and how things stand in this browser right now:

    Right now

    Report something that felt wrong

    A report linked to a program pauses it until it is looked at. Reports stay in this browser; they are part of a research contribution only if you choose.

    Your node plan

    What the device may do on its own

    Each anchor earns its own autonomy, one stage at a time: manual (you fire it), suggest (the device offers it when it detects stress, you confirm), automatic (the device fires it by itself, within the limits below), and under pressure (also during your pressure practice, only if you choose it). Each stage needs evidence, and when the evidence weakens the anchor drops back by itself.

    Your consent

    Some things work below your awareness or analyse you. None of them happens without a record of your consent, and you can withdraw it at any time.

    Automatic decisions

    WhenWhatDecision

    Session state

    One governance engine for people and agents (spec/CONTAIN.md §9–§10). An unwanted state is the start signal for repurposing; the session state decides which programs may run and who leads. A state can be raised by a self-check or a practitioner's screening result; it is never lowered by itself. On a person's own device the clinician-led protocol is advisory: a record, a prompt and a default block; clearing the browser's data resets it.

    Self-check

     

    Clinical module

    Off by default. The practitioner uses a validated instrument of their choice (for example the C-SSRS screener or PHQ-9) and records the result here. The clinician sets a PIN here before any result; resuming from the clinician-led protocol needs it. On a person's own device this control is advisory: a record, a prompt and a default block. Clearing the browser's data resets it, and whoever sets the PIN first holds it. Enforced clinician control needs a clinician-held device or a server.

    WhenFromToWhyBy

    Guidance levels

    Every program, node and session has a level. Consent and openness apply at every level; the level decides who is in the loop.

    LevelScope and who leads

    Session states

    StateWhat may run

    Research and development framework; not a medical device.

    The device safety envelope

    Limits no program can exceed, whoever wrote it: the planner, a therapist, LINX or you. A program may set stricter limits for itself, never looser ones. A program outside the envelope does not start (conformance check C14).

    WhatLimitWhy

    What CONTAIN watches over time

    SignalWhenWhat happens
    Worse afterDistress after a run is on average 0.5 or more higher than before, over the last 4 to 5 rated runsThe program or node is paused
    Agency fallsAgency drops by 1 or more on average over the last 4 to 5 runsPaused
    Rising distressDistress after runs is 1.5 or more higher than in the 5 runs beforeWatched; paused together with any other signal
    Stopped oftenStopped 4 of the last 6 timesWatched; paused together with any other signal
    Adverse eventA moderate or serious event possibly or likely related to a programThat program is paused until the therapist restores it
    Session stateA self-check (intensity 7 or more, or under 4 hours of sleep: Stabilisation) or a practitioner's screening result in the clinical module (moderate: Stabilisation; high: clinician-led protocol); flags for medication interaction or practical circumstancesOnly what the state allows can start: the clinician-led protocol pauses self-guided practice until the clinician resumes it; Stabilisation and Paused: practical allow regulation programs (paced breathing, interrupt, stillness) and practical steps
    Practice pausedA serious adverse event in 30 days; two moderate related events in 14 days; a screening answer of yes in 7 days; distress at 8 or more after 3 of the last 5 runs in a weekDevice offers and therapist-led work stop; a new plan needs a therapist present; the practitioner reviews it with the person

    A paused program is restored by the person, or by the therapist when an adverse event was involved or practice is paused (conformance check C15). After a restore, only new runs count.

    Every decision

    The last decisions in this browser, newest first.

    WhenWhatDecisionWhy