A canvas, not a dashboard
Material can sit beside material before it has earned a tidy category.
- ↳infinite space
- ↳node graph
- ↳multimodal content
havn systems · knowing canvas
Board.
The surface people step into: infinite, spatial, and aware of its contents.
A canvas for messy material that lets thinking stay visible while the system works underneath it.
package
@havn-earth/board-corehavn / board connected
Board is where the Havn system becomes a place rather than a set of packages: an infinite canvas that keeps material, arrangement, and questions in the same frame.
It is intentionally framework-agnostic at the core. The surface can grow from a calm Svelte experience without giving up the typed commands and boundaries that make it extensible.
See it in the architectureThinking needs a surface that can hold the mess.
Linear tools are good at finished answers. Real work is often earlier than that: references beside fragments, a question beside an image, a half-formed shape next to a source.
Board gives that material room. It keeps the author in control while the deeper system makes the canvas more aware of what it contains.
Small boundary.
Large surface area.
Infinite by nature
A workspace that can expand with the question instead of forcing an early hierarchy.
Commandable
Typed imperative APIs make interactions explicit, inspectable, and composable.
Aware of its contents
Knowing and the board meet where retrieval becomes a part of making.
Actions with a spine
Commands give the surface a clear way to evolve without hiding state changes in UI glue.
- ↳typed commands
- ↳framework-agnostic core
- ↳extensible interaction
The first knowing surface
The board is where Havn’s intelligence becomes tangible, useful, and still authored by a person.
- ↳ask the board
- ↳tag-driven layouts
- ↳collaboration-ready
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.
Bring it in
Put the material, reference, or fragment on the board.
Arrange
Give the question a shape you can see and revisit.
Ask
Query the board without leaving the material behind.
Make
Use the response as context, never as a replacement for authorship.
Nothing here
stands alone.
Board is useful because it has a precise relationship with the other layers. Follow the handoffs and the product gets easier to understand.
memory substrate↗
Knowing
Reads the board’s material and brings useful context back into the surface.
spatial renderer↗
Viewer
Lets selected documents and spatial objects become scenes inside the workspace.
realtime infrastructure↗
havn-server
Carries collaboration, image services, and durable state around the surface.
Give the work a place to think out loud.
Board is the product surface that makes the rest of the ecosystem legible: material in, questions alongside it, action still yours.