Documentation
¶
Overview ¶
Package main (demoseed) seeds a throwaway Seamless data dir with a fictional but realistic six-week history so the console can be screenshotted for the landing page. Not part of the shipped product; never point it at a live data dir. All content below is invented: a solo dev's agent fleet working on a Go SaaS backend (orbital), its frontend (orbital-web), a homelab, and dotfiles.
demoseed populates a THROWAWAY Seamless data dir with a fictional six-week history for console screenshots. Run it against a fresh dir while no daemon holds the DB (single-writer SQLite):
go run ./cmd/demoseed -data /tmp/seamless-demo
Timestamps are backdated through the store/files/events APIs, which write caller-supplied times verbatim; nothing here goes through MCP (which stamps time.Now). Deterministic apart from the anchor "now".
Scene-mode seeding for the landing page's with/without terminal captures (plan:terminal-scenes). Unlike the console fleet seed in main.go/data.go, this stands up a MINIMAL, precise state: one project (myapp), one active plan, a handful of memories, one backdated finding, and one failed trial -- exactly what scene 1's briefing and scene 2's landmine need, and nothing that would clutter a recorded briefing. The repo->project mapping is seeded here too, so a single `demoseed -scenes -repo <path>` run (before the daemon starts) leaves the throwaway instance ready to record against.
Source Files