Every thread of one maker's working life (projects, time, stuff, ideas, an AI council that argues, a night shift that never sleeps) woven on a single loom.
Loom isn't an app someone opens. It's a workshop three actors share around the clock: a human, a fox, and a foreman.
Runs Loom as a fullscreen tablet PWA. Drags builds between priority bands, checks the custody calendar on the go, drops ideas before they evaporate.
A violet button in the bottom corner of every page. Ask a question, report a bug, hand over a file. Kit answers from inside the workshop, with tools that touch real data.
An autonomous agent on a nightly cron ladder. Reviews the whole board while the house sleeps, makes non-destructive priority moves, and compiles the morning brief.
Follow one thread through the machine: the same path every project takes.
Everything starts as a one-liner in the Idea Incubator: typed on the tablet, said out loud to Kit, or spun off an active build. Ideas cost nothing to keep and nothing to kill. The good ones get promoted; the rest wait without guilt.
A Build is any initiative: client work, a kid's website, a prototype, a workshop. Builds live in priority bands (NOW / SOON / LATER / ICEBOX), and everything else in Loom (tasks, runs, people, inventory) attaches to one. No orphan to-do lists.
The Calendar carries deadlines and events, but its signature layer is the custody overlay: which of the four boys are home, painted across each day in their colors, down to the 10 AM handoff. Work planning and dad planning are the same planning.
handoff days paint every block's hours: one gradient layer per crew
The R&D Council convenes five roles (Visionary, Engineer, Hustler, Critic, Synthesizer) spread across five model providers. They deliberate in rounds over the live state of the board and return a scored consensus memo: what to push, what to park, what's hiding under the loud stuff.
Images, 3D models, dielines, trace-art, audio, gcode: every generation run lands in the Engine ledger with its prompt, parameters, cost, rating, and the Build it served. Six months later you can answer "what did that artwork cost and which model made it" in one query.
| run | kind | build | cost | ★ |
|---|---|---|---|---|
| 01KX…9F | image ×4 | Visions charms | $0.31 | ★★★★ |
| 01KX…2A | 3D model | DREAM cup | $0.90 | ★★★ |
| 01KX…7C | council | — board-wide | $0.57 | ★★★★★ |
| 01KX…D4 | trace-art | Gryffin pages | $0.12 | ★★★★ |
Forge's cron ladder runs the quiet hours: review every build, pull deadline work forward, flag the stale, then compile a morning brief that reads like a diary entry over coffee, ending with the single most promising signal for the day.
Loom runs on the home server it serves: private by construction, boring by design.
Next.js + tRPC + Postgres in a read-only Docker container on cortex-server. Reached over Tailscale only; there is no public login page to attack.
The same typed tRPC procedures serve the UI, Kit's tools, Forge's night shift, and external automations. Nobody gets a side door.
Installs fullscreen on the workshop tablet with an offline shell for Builds and Calendar, the two views you check with dirty hands.
Council seats route across Claude, GPT, Gemini, MiniMax, and xAI with prefix routing and automatic fallback. No single vendor owns the argument.
Contacts link to the builds they touch: 60+ edges mapping who introduced whom and which human is behind which project.
Files dropped in the Kit panel land on disk and flow to the agent (spritesheets, PDFs, screenshots), with a ledger entry when something gets made.
Loom is a private tool, built for one workshop. But the pattern (typed API, agent callers, night-shift curation) transfers. If you want something like it for your operation, talk to us.