COSMOS-CQAPublic Research Portal

Public safety

Safety boundaries for public research use.

COSMOS-CQA is a research-only public workbench. These boundaries explain the optional audio sonification, visual review surfaces, data handling, and non-claims that keep the public demo cautious and inspectable.

Audio-first safety boundary

User initiated

The sonic loop does not autoplay. It starts only when a reviewer selects Play or uses the documented keyboard control, and the same control stops playback.

Bounded contour

The maintained workbench keeps the public audio contour within documented frequency and software-gain limits. Browser code cannot control device or headphone volume.

Comfort first

Keep device volume low. Stop immediately if sound feels uncomfortable, distracting, painful, or unsuitable for hearing sensitivity, tinnitus, migraine, sensory sensitivity, or shared audio environments.

Not a treatment or diagnostic

The sonic loop is a sonification sidecar for review attention and accessibility. It is not diagnostic, therapeutic, signal-discovery, medical, or scientific measurement technology.

What the sonic loop is allowed to mean

The sonic loop maps selected tile-review values into a short, repeatable auditory contour. It is allowed to support perception, comparison, training, and accessibility alongside visual overlays, captions, labels, and evidence exports.

It must not be used to decide labels by itself, infer scientific results, validate cosmology diagnostics, make health or accessibility claims, or imply that a sound frequency has a biological effect.

Public wording: the sound is an optional way to inspect the same review object. It can help some reviewers notice patterns or compare states. It does not decide the label, validate an artifact, or produce a result.

Other public safety surfaces

Maintained checks

  • Audio is user initiated and has no autoplay path in the hosted workbench.
  • Looping is off by default and must be explicitly enabled by the reviewer.
  • Frequency, software gain, and playback-rate limits are centralized in the shared sidecar module.
  • Browser tests verify visible audio safety copy, bounded playback parameters, stop behavior, and safety-page routing.
  • Portal deployment validation includes the safety page so public releases fail if it is missing.
  • Private vulnerability and sensitive safety disclosure routes are documented separately from public issue templates.