havn systems · spatial renderer

Viewer.

A renderer that turns the same documents into a live 3D scene.

A focused visual runtime for seeing, selecting, and navigating spatial material without owning the document model.

Read the shape
package@havn-earth/viewer
havn / viewer connected
Viewer — spatial renderer marketing visual

Viewer is the spatial eye of Havn: a Babylon.js runtime that turns shared documents and geometry into a responsive, inspectable scene.

It does not own the truth. It renders what the system says is there, keeping scene concerns separate from collaboration, memory, and authoring.

See it in the architecture

Spatial work needs a renderer that knows its place.

When rendering logic becomes the document model, every camera decision becomes a product decision. Scenes get difficult to test, and other surfaces have to speak in renderer-specific terms.

Viewer keeps the relationship clean: give it a document, geometry, and intent; it gives back a scene people can see and manipulate.

Small boundary.
Large surface area.

Scene-ready

A runtime built around camera, lighting, shadows, selection, and spatial feedback.

Pure by boundary

Rendering stays a consumer, so the system can change the view without rewriting the material.

Made for inspection

Snapping, selection, and caching make the scene useful for thinking, not just looking.

A real scene runtime

ViewerRuntime gives the 3D surface a clear lifecycle and a place for the scene to live.

  • ↳Babylon.js renderer
  • ↳camera control
  • ↳lighting and shadows

Selection with context

Spatial interaction points back to shared identity instead of trapping meaning inside the viewport.

  • ↳selection state
  • ↳snapping behavior
  • ↳typed interaction

Performance that recedes

Geometry caching and focused responsibilities help the visual layer stay responsive as the material grows.

  • ↳geometry cache
  • ↳storage boundary
  • ↳render-only concerns

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.

Receive

Take the shared document and geometry contracts.

Frame

Place the material in a scene people can navigate.

Inspect

Select, snap, and move through what is there.

Return

Send intent back without taking ownership of the source.

Nothing here
stands alone.

Viewer is useful because it has a precise relationship with the other layers. Follow the handoffs and the product gets easier to understand.

Give spatial material somewhere to become visible.

Viewer is the focused scene layer in a system that keeps rendering, memory, and authoring in conversation.