Naru M / For developers
Expression is
its own engine.
Give it a state and intensity. Let the Light Engine translate them into a coherent light experience.
Explore the engineering Lab ↗Read the current technical scopeKnow what exists
Clear scope.
Room to grow.
| Stage | What it means |
|---|---|
| Working browser implementation | Four public Expression Modes with eight compatible internal profiles, intensity scaling, layered particles, 3D rendering, touch, optional synthesized audio and an engineering Lab. The Lab includes a deterministic Mock service and a Live proxy structure. |
| Light Engine v1 / Current delivery scope | A reusable expression component and small local programming interface, examples, tests and integration documentation. The supplied specification describes the hardware-driver boundary; this website does not ship production device firmware. |
| Runtime SDK / Roadmap | Runtime coordination, state memory and transition priorities, connectors, diagnostics tooling, and formal SDK packaging. |
| EchoAI / Future integration | Mode inference, cloud/API integration, authentication and device/cloud communication. A production EchoAI service is not included. |
A small semantic contract
State.
Intensity.
Expression.
The local Light Engine specification uses a state identifier and a value from 0 to 1. Intensity changes strength while preserving the feeling’s identity. The engine expresses the supplied state; it does not determine how a person feels.
Warm, Calm, Sad and Dynamic share overlapping color territories. Rhythm, motion and space make the difference.
{
"state": "happy",
"intensity": 0.80
}Light Engine specification input. The existing Lab web API uses mode and additionally validates a request ID.
# Reference interface — specification,
# not an installed Python package.
engine.begin()
engine.set_state("happy")
engine.set_intensity(0.8)
engine.update() # non-blocking
engine.reset()One boundary, many sources
Inference and expression.
Independently useful.
- INPUT
Semantic state
Manual selection and local touch now. Future connectors can supply sensing or EchoAI results.
- LOCAL
Light Engine
Profiles resolve color, brightness, glow, motion, rhythm, density and spatial behavior.
- RENDERER
Output adapter
Browser simulation is implemented. LED-driver integration is specified, with hardware details still open.
Touch stays local-first. A network response must never be a prerequisite for a local light response.
The path ahead / From the supplied roadmap
A focused first step.
- 01
Light Engine v1
Current milestone: expression, timing, intensity, the renderer/driver contract, examples and tests.
- 02–03
Runtime & connectors
Planned: orchestration, memory, transition priority and provider boundaries.
- 04–05
Tooling & SDK packaging
Planned: runtime diagnostics and a broader package once the boundaries are stable.
- 06
Production API integration
Future: EchoAI supplies semantic state through a connector. The cloud remains separate from embedded expression.