About

BSC Lab

BSC Lab is an open sensory-stimulation research and engineering platform. It pairs a precision audio-visual stimulation application with SSTIM, a public RDF knowledge graph for describing techniques, parameters, exposure conditions, safety metadata, and evidence — so what you build, browse, and annotate all live in one place.

The work is non-clinical. It supports exploration and authoring of sensory experiences; it does not diagnose, treat, cure, or prevent any condition, and it makes no claim of clinical efficacy. See Scope.

How the pieces fit

Æterni Anima is the organization responsible for everything here. BSC Lab and BioSynCare are its two platforms — SSTIM and Patch Studio live inside BSC Lab — and BSC is the framework both platforms build on. Knowing which is which makes the rest of the app easier to read.

The organization

Æterni Anima

The organization behind all of this — BSC Lab, the SSTIM knowledge graph it publishes, Patch Studio, and BioSynCare are all its responsibility. It is an independent initiative rather than an incorporated company: the name the work is developed, released, and credited under.

The framework

BSC

The framework both platforms build on: audio — Martigli respiratory waves, binaural beats, Symmetry permutations, soundscapes and colored noises — together with visual cues matched to the Martigli oscillation. It defines the three techniques it originated (Martigli, Martigli-Binaural, Symmetry); the generic ones it applies are incorporated from the SSTIM vocabulary rather than redefined.

Open platform

BSC Lab

The open-source research and engineering platform you are using now. It holds the SSTIM knowledge graph and its Turtle sources, Patch Studio, and the surfaces built around them — Graph, Field, Presets, SPARQL, and Logbook. Software is Apache-2.0; the ontology, vocabulary, and public reference data are CC BY 4.0.

Knowledge graph · in BSC Lab

SSTIM

The Sensory Stimulation Ontology — a public RDF knowledge graph of techniques, modalities, parameters, exposure conditions, safety metadata, evidence-qualified claims, protocols, presets, and sessions. OWL classes, a multilingual SKOS vocabulary, and SHACL shapes under the stable namespace w3id.org/sstim. Developed and published within BSC Lab, it is the reusable, citable scientific artifact — and namespace governance is set to pass to the W3C Community Group once its charter is ratified.

Commercial application

BioSynCare

A separate, closed-source commercial application in its own repository. It shares the preset JSON format and the SSTIM vocabulary with BSC Lab, but neither project imports the other’s code or private data.

What you can do here

Every screen below is reachable from the dock at the bottom of the window. This is a working application, not a landing page — jump straight in from any card.

Graph Knowledge browser

An interactive Cytoscape view of the SSTIM knowledge graph — OWL classes, multilingual SKOS concepts, object/data properties, and the links between them, drawn straight from the Turtle sources. It is also where you annotate the ontology.

How to usePick a scope: Full SSTIM shows the released ontology and vocabulary; Catalog + ecosystem switches to the versioned catalog and live people/organizations (the left rail explains what each data source is); or narrow to one thematic slice — Core OWL classes, All SKOS vocabulary, Frequency bands, Modalities, Mechanisms, Techniques, Voice types, Preset groups, Evidence, Cautions, Exposure, and more. Toggle the edge layers — subClassOf, object/data property, narrower, related, instanceOf, catalog relation, ecosystem relation. Press / to search, Enter to centre, and c / f / r to centre, fit, or relayout (? lists every shortcut). Select any node to open its detail panel: definition, a copyable IRI, a link to its generated reference entry, and its incoming/outgoing connections — which you can filter by edge kind or isolate with Focus neighborhood — plus a notes area for annotation.

Patch Studio Real-time authoring

A live surface for authoring multi-sensory patches. Layer audio tracks (Isochronic Tone, Binaural Beat, Carrier, Noise, Drone, ambient Sample), visual tracks (geometry, particles, gradients, pacers, ripples, spirals, mandalas…), and a haptic Vibration track — with per-parameter modulation and photosensitivity safeguards.

How to useAdd tracks from the palette and shape each parameter; many can be tempo-synced or modulated. Press play to preview audio and visuals together in real time. The audio engine — Vanilla Web Audio, AudioWorklet, AudioWorklet + WASM, or the sound-free Silent engine — is chosen in Settings and applied on the next playback. Playback always starts from a tap or click, per browser autoplay rules.

Field Sensory Field instrument

A bounded visual/audio exposure instrument for prototyping sensory fields. Each control is mapped to the exposure-ontology term it emits — full-screen light fields, free-view stereoscopy, blink patterns — so what you shape here is expressible directly in SSTIM.

How to useOpen the Field and adjust the exposure controls; inline links show what each setting means in the ontology. Alternate scenes are reachable from the + menu: Stereoscopic Tree, Abstraction, and 3D Landscape. Blink rates are bounded by the photosensitivity flash-rate limit, and visual stimulation honours the safety toggle in Settings.

Presets Reference catalog

The public BSC Lab reference presets — the catalog objects shared with BioSynCare — read live from the RDF knowledge graph, with their group, target frequency band, and linked evidence claims.

How to useFilter the catalog by group (Heal, Support, Perform, Indulge, Transcend), by target band (delta, theta, alpha, smr, beta, gamma and sub-bands), or by evidence tier, and open a preset to see its parameters and the evidence behind it.

SPARQL Query workbench

A SPARQL 1.1 workbench that runs entirely in your browser (Comunica over an N3 store), querying the ontology and the public instance data together.

How to usePick one of eight example queries — vocabulary, ontology structure, catalog, ecosystem, evidence, exposure, and external alignments to BFO/OBI/IAO and Wikidata — or edit the starter query and write your own, then press Run and read the results table. Named graphs keep ontology terms, public reference data, and annotations separate, so cross-source queries need one GRAPH block per source; the "About this endpoint" panel on the page explains why, and lists the raw Turtle URLs if you want to query the same data from your own tooling instead.

Logbook Personal record

A private, long-term record of your sensory-stimulation work — sessions, observations, ideas, activities, initiatives, notes, and achievements, across multiple named logbooks.

How to useAdd entries, tag them, and filter by tag. Entries are stored locally in your browser by default; when a deployment is configured with sign-in, they become a private per-account record. Your data stays yours and is never committed to the repository.

Settings Appearance, engine, safety

Where you choose the visual skin, the audio engine, and the photosensitivity safety behaviour.

How to usePick a skin (Paper, Midnight, Aurora, Ember, Daylight), select the audio engine used by Patch Studio and the Field, and set the visual-stimulation safety toggle. Unsupported engines fall back automatically.

Two more reference surfaces open from the + menu in the top bar: your optional account Profile (private, sign-in based), and the generated Ontology docs and Vocabulary docs.

SSTIM, in a little more depth

The knowledge graph is organised as a small set of Turtle modules, each an owl:Ontology with its own metadata:

  • Core — OWL classes, properties, axioms, evidence governance, and the session model.
  • Vocabulary — multilingual SKOS values for bands, modalities, mechanisms, techniques, evidence, and cautions.
  • Shapes — SHACL constraints validating modules, evidence, protocols, presets, safety, and sessions.
  • Alignments — conservative, verified links to Wikidata and OBO Foundry.
  • Exposure — delivery media, perceived modalities, devices, placement, stimulus patterns, and limits.
  • Patch Studio — reproducible voice and authoring parameter properties.
  • Ecosystem — neutral agent relationships, engagement provenance, and consent lifecycle metadata.

Controlled values are dual-typed as both OWL individuals and SKOS concepts. The ontology is validated with SHACL and an OWL reasoner, is published under https://w3id.org/sstim, and carries a citable DOI.

Community coordination happens in the Sensory Stimulation Vocabulary Community Group at the W3C — an open group, proposed and chaired by Renato Fabbri, for aligning sensory-stimulation vocabulary and interoperability work across projects. Anyone can join and participate.

Reading the data sources

The Graph's Data sources panel lists what is loaded and where it comes from. The four words mean different things:

  • Ontology — the versioned OWL term modules: classes, properties, and axioms, released and citable under w3id.org/sstim.
  • Vocabulary — the multilingual SKOS concept values (frequency bands, modalities, mechanisms, techniques…), dual-typed with the OWL classes.
  • Catalog — versioned public reference instances of frameworks, implementations and their components, presets, and evidence records.
  • Ecosystem — a live projection of people, organizations, and reviewed relationships in the field. It is fetched at runtime, each record is separately approved and sourced, and it is retractable: it is deliberately excluded from citable releases and archives.

Where your data lives

BSC Lab keeps different kinds of data deliberately separate, in different named graphs and stores:

  • Authoritative ontology & public reference data — the shared, citable SSTIM sources, the same for everyone.
  • Annotations — public notes in a shared annotation graph; your private notes in your own, visible only to you.
  • Your Logbook — local to your browser, or private to your account when sign-in is configured.

Real participant session data, the private BioSynCare catalog, and any clinical material are not part of this repository. Your private notes and logbook stay yours.