Dev Desk
A local developer cockpit connecting source-cited project handoffs with persistent tasks, notes and model experiments.
Product interface · demonstration data
Problem & context
Project context, recorded next steps and personal work become fragmented across repositories and tools. Returning to a project needs a clear path from its source context to the next action.
My contribution
Built a modular TanStack Start workspace and macOS shell around an owned loopback server and private PGlite storage. Connected project briefs to editable, project-linked work and added an explicit text-model testing workspace. Integrated Accord’s shared review notebook through scoped HTTP adapters, with corrections previewed before application. Added Registre, a hardware register whose import preserves original source fields, uncertain observations and historical estimates.
Decisions & tradeoffs
Keep observed project evidence separate from personal work.
Retain source paths, lines and cautions in resume briefs; capturing a next step creates an editable task without rewriting its source repository.
Give local persistence a clear runtime owner.
Use revision-checked saves and a shared process lease, refusing a competing writer before it opens the database.
Preserve source evidence when importing a hardware inventory.
Retain original fields and source dates, with unresolved observations and unverified historical estimates kept explicit.
Outcome
Implemented a local workflow for inspecting projects, capturing their next steps and retaining linked work across sessions. The screenshot shows the application running with synthetic project and work data.