The Runtime Heart of neurOS
neuros-core is where a live BCI pipeline actually runs. It owns the agents, the processing chain,
and the run-time configuration that connect a driver's stream to a model's prediction.
package map
neuros-core — agents, pipeline, and processing
The runtime heart of neurOS: an async agent orchestrator, the processing pipeline, and CV plugins that turn streamed signals into real-time inference.
Comprises
Agents
device, processing, model, fusion, pose, video, calcium
Pipeline
orchestration, alignment, augmentation, benchmarks
Processing
filters, feature extraction, adaptation, health
Also holds
CV plugins
DINOv3 backbone, feature matching, seg head
Autoconfig
automatic pipeline configuration
Security
access and safety layer
Role
Real-time engine
coordinates agents into a live pipeline
Adaptive
agents adapt when signals degrade
What It Comprises
- Agents — an async set of specialized workers: device, processing, model, and fusion
agents, plus modality-specific agents (motion, pose, video, facial, blink, calcium) and a
multimodal_orchestratorandmodality_manager. - Pipeline — the
pipeline,alignment,augmentation,evaluation, andbenchmarksmodules that assemble and score a run. - Processing —
filters,feature_extraction,adaptation, and ahealth_monitorloaded dynamically at run time. - CV plugins — a DINOv3 backbone, feature matching, and a linear segmentation head for imaging-heavy pipelines.
- Support —
autoconfigfor automatic pipeline configuration and asecuritylayer.
How It Differs
Where neuros-drivers handles getting data in and neuros-models handles the architectures,
neuros-core is the conductor: it coordinates agents into a real-time loop and lets them adapt
when signals degrade. It depends on the other packages rather than duplicating them.
Part of the neurOS-v1 platform.