Architecture

The repository separates five concerns:

• src/lib/showcase/registry.ts defines catalog identity, grouping, descriptions, and upstream documentation routes.
• route pages compose shared showcase shells with isolated demo components.
• src/lib/builder, the session API, and builder routes define serialisable editing, rendering, persistence, export, and browser-relay integration.
• src/app.css provides one shared skin over headless Bits UI behavior.
• deploy contains source templates for the service and both HTTP surfaces; their runtime state is a separate verification boundary.

Read the detailed contracts:

• Stack
• Showcase contract
• Design system
• Builder architecture

Target request and deployment topology

Status: verified. The production application uses adapter-node behind nginx, the wiki is published as Quartz static output, TLS covers both public hosts, and the build/service/browser receipts are recorded in Operations.

flowchart LR
  Browser["Browser"]
  AppHost["bits.loca.zone"]
  WikiHost["wiki.bits.loca.zone"]
  Edge["Nginx reverse proxy — verified"]
  Node["SvelteKit adapter-node on 127.0.0.1:51500"]
  Static["Published Quartz static output"]
  AppSource["Application source"]
  WikiSource["q5vault source"]
  AppBuild["Verified adapter-node build"]
  WikiBuild["Verified Quartz build"]
  Deploy["deploy templates"]

  Browser --> AppHost --> Edge --> Node
  Browser --> WikiHost --> Edge --> Static
  AppSource --> AppBuild --> Node
  WikiSource --> WikiBuild --> Static
  Deploy --> Edge
  Deploy --> Node

The diagram is the observed production topology as of 2026-08-30. Operations contains the supporting build, service, TLS, publication, and browser receipts.

---

loca.zone · bits.loca.zone · SvelteKit · Bits UI