The BioSynCare Ecosystem

People who follow this work run into several names — BioSynCare, BSC Lab, SSTIM, Patch Studio, Seraphony — and reasonably assume they are branding variations on one product. They are not. They are layers of a single architecture, and the order runs in the opposite direction from what most people expect: not from a product outward, but from formalised knowledge down to everyday use.

The pathway is knowledge → open technology → everyday delivery. This post is the map.

The mission is to make high-quality, scientifically informed and aesthetically meaningful sensory stimulation accessible through everyday digital devices — supporting performance, well-being, health, and contemplative experience.

The vision is longer-range: to establish sensory stimulation as a reliable and widely accessible component of everyday life, research, and professional practice.

That second sentence is what explains the layered structure. "Reliable and widely accessible" is not something an app can deliver on its own. It needs a shared way to describe what is being done, tools that let anyone inspect and reproduce it, and a delivery surface people actually use.

SSTIM is the foundation and the part designed to outlast every application built on it. It is a machine-readable knowledge base for sensory stimulation, combining an OWL ontology, SKOS vocabularies, RDF data, evidence annotations, and implementation profiles.

It describes the things the field otherwise discusses in loose prose: techniques, modalities, stimulus parameters, exposure boundaries, evidence claims, protocols, presets, and sessions.

It lives at the persistent namespace https://w3id.org/sstim and carries an all-version DOI (10.5281/zenodo.21286974). The source set is manifest-driven, organised as Turtle modules behind four profile entry points:

New integrations are expected to start at Core or Core Plus and add concern modules through the manifest-resolved dependency closure, rather than merging everything at once. The sstim prefix resolves at prefix.cc, and the ontology is parsed and browsable in BioPortal.

There is a second audience here that is easy to miss. SSTIM is explicitly positioned as infrastructure for symbolic and hybrid AI — a substrate a reasoning system can consume, validate against, and act on, rather than prose it has to guess at.

BSC Lab is the open-source environment that turns the knowledge layer into something executable. It is a shared research and creation workbench connecting knowledge, prototypes, and reusable implementations.

It ships as a static web application — an ontology graph browser, a SPARQL workbench, a preset browser, a logbook, and profile and settings surfaces. It works with no account; sync is optional.

Patch Studio is the part most people will actually touch: a visual workbench for designing, combining, testing, and documenting stimulation patterns, with built-in Sensory Field starters.

One deliberate choice deserves to be stated plainly, because it is unusual for a project with a commercial layer: defensive publication is chosen over patenting, to preserve open access, reuse, and collaboration across the wider ecosystem. The methods are published so they stay usable, not fenced so they stay owned.

What BSC Lab publishes is example and reference data: the BSC framework, framework techniques (some originated by BSC, some vendor-neutral ones it incorporates), protocols, reference presets, evidence assessments, exposure hypotheses, and DOI-identified references. What it deliberately does not publish is real participant session data, the private BioSynCare catalogue, or anything clinical.

Validation is not informal. The repository runs SHACL Core and SHACL-SPARQL validation, OWL reasoning, repository-wide semantic integrity checks, and executable SPARQL competency queries under a pinned toolchain. A 2026 external automated OOPS/FOOPS review has been resolved; independent human ontology review is explicitly not claimed.

BioSynCare is the commercial multiplatform application — web, iOS, and Android — that turns the ecosystem's knowledge and technology into structured sessions people use daily.

A session combines patterned auditory stimulation, breathing guidance, visual cues, optional colored noise, and natural soundscapes, so a person can regulate their level of activation according to what they need in the moment. The main capabilities:

BioSynCare is a wellness and performance-support platform. It does not replace medical diagnosis, treatment, or professional care.

A vocabulary that only one organisation uses is a private schema, not a standard. The W3C Sensory Stimulation Vocabulary Community Group exists so the terminology does not stay proprietary: it is an international forum developing shared terminology, semantic models, and implementation guidance, opening a route toward interoperability and future standards.

Alongside it, BSC is working to convene an international coalition of researchers, developers, practitioners, and institutions around sensory stimulation, shared knowledge, and responsible standards — to strengthen coordination among existing initiatives and present the field clearly and credibly to public authorities, professional communities, and the general public.

Publishing your methods is one half of accountability. The other half is committing to standards someone else wrote, and being checkable against them.

BioSynCare has endorsed the European Charter for the Responsible Development of Neurotechnologies, promoted by the European Brain Council, and is listed among the organisations supporting it — alongside bodies including the European Academy of Neurology, the European Association of Neurosurgical Societies, and the European Federation of Neurological Associations.

What the listing records is agreement and direction. BioSynCare already meets many of the Charter's commitments and is running an active implementation programme against the remainder — treating endorsement as a commitment trajectory with open gaps disclosed, rather than as a claim of finished conformance. Support is where the work starts, not a certificate for having completed it.

That posture is the same one the rest of this architecture is built on. A public schema for evidence tiers and exposure boundaries is only useful if the organisation behind it is willing to be measured against something it does not control.

The obvious question is why a commercial application maintains a public ontology and an open-source lab at all.

The short answer is that the vocabulary problem is real and no single product solves it. Without a shared way to say "this technique, at this rate, in this modality, within this exposure boundary, supported by this evidence at this tier," every tool describes its methods in prose that cannot be compared, queried, or cited. Claims stay unfalsifiable by construction.

Keeping the layers distinct also imposes useful discipline in each direction:

The stated aim is to develop an open sensory and semantic layer through which people, symbolic and hybrid AI systems, and sensory technologies can describe, validate, and responsibly coordinate sensory interactions.

That is a wider target than a wellness app. It assumes a future in which several kinds of agent — human and machine — need to negotiate sensory experience with each other, and in which doing so safely requires a shared, inspectable description of what is being delivered and within what boundaries.

The core team is Renato Fabbri, Ph.D. (research, architecture, software, and coordination), Riccardo Berti (development), Eva Castilho and Clarice Garcia (communication and marketing), and Edson Correa (production and project management).

The scientific and institutional network includes Juliana Braga de Salles Andrade, Ph.D. (neuroscience), Dr. Rafael Reinehr and Dr. Marco Fracasso (medicine), IPRJ (research), and Junto Innovation Hub (territory, innovation, and entrepreneurship).

If you want to use sessions, start with the app and the method guides — brainwave entrainment, binaural beats, sensory stimulation — or the companion post on what sensory stimulation actually is.

If you want to inspect or reuse the methods, start with BSC Lab's scope and evidence framework documents, then the SSTIM manifest and the Core profile.

If you want to collaborate — as a researcher, developer, practitioner, institution, or pilot organisation — the W3C Community Group is open, and work with us is the direct route.