Contracts that travel
The types are the connective tissue between packages and runtimes.
- ↳shared identifiers
- ↳typed actions
- ↳stable package boundaries
havn systems · compute foundation
Kernel.
The geometry and compute layer underneath the making tools.
Shared primitives give every Havn surface the same language for shape, identity, and action.
package
@havn-earth/kernelhavn / kernel connected
Kernel is the part of havn that should feel invisible: a small, shared vocabulary for the systems that make and render things.
It holds the type contracts and compute bridges that let higher layers move quickly without inventing a new primitive for every surface.
See it in the architectureA product is only as coherent as its primitives.
Spatial tools often drift apart at the seams. Geometry is redefined in the renderer, actions are duplicated in the UI, and the same object means something different to each package.
Kernel keeps that drift from becoming product behavior. It is a boundary for the hard, shared parts so the surfaces above can stay calm.
Small boundary.
Large surface area.
One vocabulary
Typed contracts create a common grammar for nodes, geometry, actions, and identity.
Local power
WASM and GPU bridges keep demanding work close to the machine and close to the material.
Room to compose
A focused foundation gives Viewer, Knowing, and Board a stable place to meet.
Geometry without ceremony
2D and 3D geometry utilities are available where making actually happens.
- ↳geo3d exports
- ↳WASM bridges
- ↳future-ready primitives
Compute as a first-class layer
The foundation leaves room for local GPU work and AI actions without turning the UI into an infrastructure project.
- ↳WebGPU compute
- ↳AI infrastructure hooks
- ↳deterministic intent
How the layer
moves.
Every surface in Havn has a job in the loop. This one keeps its responsibility clear, then hands the work to the layer that comes next.
Define
Give a thing a shared identity and a typed shape.
Compute
Move the expensive work to the right local runtime.
Hand off
Pass the result to the surface that needs to make it visible.
Keep it legible
Let the product remain about the work, not the plumbing.
Nothing here
stands alone.
Kernel is useful because it has a precise relationship with the other layers. Follow the handoffs and the product gets easier to understand.
Build on a foundation that stays understandable.
Kernel is the shared ground beneath Havn. Start with the surface you care about, then trace the primitives underneath it.