Optional device integration
SlowSystems is a structured learning platform first. In phase 1, an adult learner may optionally connect a supported Muse device to add technical session context without affecting grades, learning outcomes, or teacher feedback.
Application context
The platform does not depend on EEG and does not reproduce proprietary meditation, focus, sleep, recovery, or mental-fitness scores. Device data is not used to grade learners, infer understanding, or evaluate teachers.
Product workflow prototype
The prototype demonstrates a coach-created learning plan, an adult learner session, a knowledge check, reflection, coach feedback, and repetition planning. It uses sample educational data only and contains no live Muse SDK integration or EEG data.
Current implementation status
The table distinguishes a real clickable sample-data prototype from functions that require approved SDK access and supported-device confirmation.
Why Muse is requested
The request is limited to connection handling, timestamps, signal-quality guidance, repeatable development support, and permitted local feature processing. The device does not create the learning result.
Permitted timestamps can align optional device context with task changes, pauses, and manual markers.
Connection status and available signal-quality information can help the learner identify unusable periods.
.muse recording, logging, and playback would support reproducible integration testing where permitted.
Approved data can be processed locally before a narrowly defined session feature event shown only to the learner.
Reviewer one-page brief
The PDF brief summarizes the learning product, adult phase-one users, session workflow, optional Muse integration, product boundaries, initial SDK request, and current evidence status. The SVG remains available as the responsive web preview.
Reviewer facts
The planned implementation uses Android / Flutter with a native bridge and begins with internal testing followed by an adult closed beta only after SDK and licensing approval.
Applicant
Project stage
License path
Initial platform
Primary evaluation target
Initial users
Device-data visibility
Initial distribution
Phase-one use case
During a guided learning session, an adult learner may optionally connect a Muse device. The application records connection status, signal quality, timestamps, recording continuity, and permitted signal features alongside task changes, pauses, and manual markers. The information is shown only to the learner as technical session context. It does not grade the learner, infer understanding, or determine teacher feedback.
Planned data flow
The phase-one design keeps device access, local processing, educational records, and any future storage as separate layers.
Disabled by default.
Educational records only; no raw EEG or EEG-derived performance scores.
No raw EEG.
User-controlled and separately documented before any closed beta.
Requested capability scope
Phase 1 requires confirmation of standard Muse S Athena support for Android. It does not depend on Athena optics or fNIRS access.
Requested from Muse / InteraXon
The first question is whether Muse S Athena supports the standard phase-one Android functions. If not, the reviewer is asked to identify the appropriate current Muse model for initial evaluation.
Confirm whether the current commercial Android SDK supports Muse S Athena for phase-one EEG data, timestamps, connection status, signal-quality information, .muse recording, playback, and logging.
If Muse S Athena is not supported for these phase-one functions, confirm which current Muse model should be used for the initial commercial SDK evaluation.
Confirm permitted EEG data and any restrictions on local processing, temporary storage, persistent storage, and display of documented derived features.
Clarify requirements for internal development, adult closed-beta testing, public release, device naming, screenshots, demo material, and compatibility statements.
For Muse S Athena, clarify whether optics or fNIRS-related data are available and permitted. Phase 1 does not depend on this access.
Integration requirements
The learning workflow can operate without connected hardware.
Initial device use is limited to adult independent learners and adult learners working with a learning coach.
Phase-one device information is visible only to the learner who connected the device.
Raw device streams stay outside teacher views and third-party AI services by default.
