Imersa, open
Device identity, normalized capabilities, rooms, scenes, connector isolation, deterministic plans, execution results, permissions, and audit history.
Back to selected work
Open source / local orchestration
Imersa
A local foundation for connected devices, rooms, deterministic scenes, and automation whose decisions can be inspected before they run.
- Role
- Creator and core engineer
- Release
- Foundation 0.1.0
- License
- MPL 2.0
- Status
- Open core in active development
The premise
Normalize the environment without flattening it.
Connected devices expose incompatible identities, capabilities, state shapes, commands, and failure modes. Imersa gives product experiences one stable model while preserving what each device can actually do.
Execution is deliberately two phase. A caller first receives an inspectable plan based on current state and permissions. The stored plan runs only with the required scopes, an idempotency key, and explicit confirmation for consequential actions.
Product boundary
One open foundation, private products around it.
Imersa publishes the reusable local orchestration contract. Flow HiFi and Flow Music integrate with it without exposing their product-specific implementation.
Flow HiFi and Flow Music, private
Product experience, media logic, commercial integrations, accounts, analytics, hardware tuning, and other proprietary product work.
The integration contract
A versioned local API and TypeScript library let private applications use Imersa without merging their source or ownership boundaries.
Independent rebuild
The repository started from an empty directory.
An earlier experiment grew from a third-party bridge fork. That was the wrong technical and licensing foundation for the product Imersa had become.
I preserved that lineage as an archived legacy fork, then created a new repository with an independent history, explicit provenance rules, and no imported predecessor source.
Clean historyNew root commit and non-fork GitHub repository
Open licenseMPL 2.0 at the file boundary
Provenance gateCI checks source identifiers and project boundaries
Foundation 0.1.0
What the open core contains now.
Typed domain
Devices, capabilities, rooms, scenes, principals, risks, and commands validate at the runtime boundary.
Deterministic planning
Plans capture current revisions, blocked resources, required scopes, risk, and confirmation before any connector writes.
Exact execution
Idempotent runs report success or failure for every step and expose partial outcomes instead of hiding them.
Reference API
A local authenticated HTTP server exposes versioned health, device, scene, planning, execution, and audit routes.
const plan = runtime.scenes.plan("evening", principal);
const result = await runtime.scenes.execute(plan.id, principal, {
confirmed: true,
idempotencyKey: "evening-2026-07-29",
});
Current limits
A credible foundation, not a finished platform.
The core does not yet include production hardware adapters, persistent storage, encrypted connector credentials, or a production identity provider. The controller image on this page is interface direction, not evidence that those integrations have shipped.
The next work is to harden storage and identity, publish the first connector specification, and validate adapters against owned equipment without weakening the clean-source boundary.