yeksax
lattice
← Back to home

Lattice

CLI, daemon and dashboard

What the agent wrote should outlive the conversation.

Agents produce plans, audits, and reports as standalone HTML, and those files rot in a downloads folder or disappear with the chat. Lattice registers each one by absolute path without copying, moving, or rewriting it, then builds a searchable library from what is already on disk. The filesystem stays the source of truth, and publishing remains a separate, deliberate act.

Stack

language

Go 01 language Go One binary contains the CLI, daemon and dashboard on three operating systems. go.dev TypeScript 02 language TypeScript The hosted side: worker, schema and the dashboard's client code. typescriptlang.org

front-end

Astro 03 framework Astro The landing page at lattice.pub, static and built from the same repo. astro.build Tailwind CSS 04 styling Tailwind CSS The site and the local dashboard, from one theme config. tailwindcss.com

data

Cloudflare D1 05 database Cloudflare D1 Shared snapshots, poll answers and the threads under them. developers.cloudflare.com

infra

Cloudflare Workers 06 runtime Cloudflare Workers The optional backend for public snapshots. Nothing local depends on it. developers.cloudflare.com
01 register

One command

`lattice add` writes only a sidecar with the title, tags, and slug. The HTML stays exactly where it was written.

  • Registered by absolute path
  • The original is never touched
02 library

Local dashboard

Any command spawns the daemon, which serves the library on the loopback and reads the same theme config the writing skill does.

  • Daemon starts on demand
  • Theme shared with the skill
03 share still your files

Hosted snapshot

Publishing is its own command, never a side effect. Results from polls embedded in a page are available from the terminal.

  • Sharing is opt-in
  • Poll results are available in the CLI