SDK review brief

SlowSystems Neuro SDK Partner Brief

A concise technical brief for reviewing the signal boundary, draft event schema, artifact status, requested access, and device-partner value.

View Proof Pipeline Readiness · Open review manifest

Architecture: AvailableEvent schema: DraftRuntime fixture: AvailableLive device proof: Pending

Current artifact

Available now: vendor-neutral architecture, review manifest, simulated fixture run, and draft cognitive_state_update JSON Schema. The next proof milestone is a timestamped live-device or open-platform runtime artifact.

What SlowSystems is requesting

  1. Which raw, derived, or optics/fNIRS-related streams are available under the relevant SDK path?
  2. May non-medical derived events be displayed to users in a prototype or beta?
  3. Which compatibility, integration, screenshot, and demo wording is permitted?
  4. Which approval path applies before public beta or commercial release?
  5. Which privacy, security, storage, and data-processing documents should be prepared?

Why this matters to device partners

Expands non-medical developer use cases

Turns device streams into structured app-layer workflows without clinical positioning.

Converts streams into event contracts

Provides a draft cognitive_state_update model that product teams can inspect.

Reduces raw-data exposure

Separates raw streams from derived outputs and AI-facing summaries.

Creates a reviewable path before release

Makes proof status, sample artifacts, approval questions, and boundaries explicit.

Access paths

Open proof path

OpenBCI and BrainFlow-compatible pipelines for runtime artifacts without implying endorsement.

SDK evaluation path

Muse / InteraXon, EMOTIV Cortex, and Neurosity Crown conversations around stream access and permitted use.

Muse clarification path

Muse S Athena, optics/fNIRS stream availability, and Personal-to-Commercial path.

Adapter architecture

Device / simulator → adapter interface → stream validation → feature windowing → derived event schema → app/API consumer

Release boundary

  • Device-specific claim wording is a review item.
  • Brand, logo, screenshot, and compatibility wording need the relevant approval path.
  • Raw streams stay outside third-party AI summaries by default.