Umbra-Noesis · Infrastructure Layer
Umbra Link is the backbone that ties the Umbra-Noesis stack together — managing who is present, which nodes are reachable, and how they communicate in a private, local-first mesh.
Overview
Every component in the Umbra-Noesis stack — EVE OS, EVAA, PCe hardware — needs to know who is operating it and where other nodes are. Umbra Link is where that context lives. It defines identity, resolves location, and manages secure communication between participants without routing anything through a cloud intermediary.
A human-facing identity that persists across nodes. The system knows who it is working with — not just which machine is currently active.
Each machine — workstations, laptops, PCe kits, mobile rigs — carries a unique Node ID. Umbra Link tracks which nodes are reachable and what their capabilities are.
One shareable code to link trusted devices and locations into a unified private mesh — home lab, field unit, or remote node — without a central relay. In Development
Ecosystem Integration
EVE OS
The platform layer that hosts Umbra Link services. Node identity and routing run on the OS itself — no external service required.
EVAA Cognition
The local AI layer reads identity context from Umbra Link — it knows who it is talking to and from which node, enabling structured, governed responses.
PCe Systems
Documented hardware profiles — workstations, kits, mobile rigs — that Umbra Link binds into a single coherent environment regardless of physical location.
Roadmap
Identity Schema
Formalize User ID and Node ID specifications, aligned with AACP protocol for structured message binding across nodes.
ActiveConnection Codes
One personal code to link home rigs, field units, and PCe systems into a unified mesh. No account, no cloud relay.
In DevelopmentMesh Routing & Sync
Rules for how nodes discover each other, sync selectively, and stay resilient when one node goes offline or changes network.
RoadmapDesign Principle
Local-first. Consent-based. No cloud required.
Umbra Link never phones home. Identity and routing live on your hardware. Remote connections happen only when explicitly authorized — and only between trusted participants.