📊 Full opportunity report: Disk Is the Contract: Inside Threlmark’s Local-First Architecture on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark introduces a local-first architecture where project data is stored entirely on disk as JSON files, making the system open, portable, and resilient. This approach eliminates the need for a central server or database, enabling seamless integration and safety.
Threlmark has unveiled a novel architecture that treats disk files as the definitive contract for project data, eliminating the need for a centralized server or database. This local-first approach leverages JSON files stored on the user’s disk to manage project roadmaps and AI integrations, emphasizing portability, inspectability, and restartability. The design fundamentally shifts how project tools can operate without relying on cloud services or persistent in-memory state, making it a significant development in local-first project management systems.
The core of Threlmark’s system is that all project data resides in JSON files stored in a dedicated directory, defaulting to ~/.threlmark. This includes project metadata, dependency graphs, individual roadmap cards, and external suggestions, all structured as separate files. The system’s key innovation is that the files themselves serve as the API, enabling external tools and AI agents to read and modify project data directly without a server or database layer.
Threlmark’s architecture emphasizes four properties: inspectability, portability, interoperability, and restartability. Each artifact is a plain file that can be viewed, diffed, or backed up easily. The system employs atomic write operations using temporary files and rename() calls to ensure data integrity even during crashes. Updates follow a read-merge-write pattern, allowing forward-compatible changes that preserve unknown fields, supporting evolving tools and data schemas.
The design also includes a self-healing lane management system that reconciles project cards with the actual files on disk, automatically adding missing cards or dropping orphaned ones. This approach minimizes concurrency issues and simplifies external tool integration, making Threlmark a flexible, open system for multi-project roadmapping and AI automation.
Disk is the contract: inside a local-first roadmap hub
A Next.js app on top of plain JSON files — no database, no cloud, no accounts. The key decision: the on-disk layout IS the API. Everything else cascades from taking that seriously.
There is no server-of-record — the files are the record
The UI and any external tool reach the same files through the same discipline. The data root defaults to ~/.threlmark — home-based, because it’s a shared hub every one of your apps points at.
Inspectable
Every artifact is a file you can cat, diff, grep, commit.
Portable · no lock-in
Back up with cp, sync with Dropbox / git, migrate trivially.
Interoperable
Any tool in any language joins by reading / writing files.
Restartable
No in-memory state to lose — stateless over the files.
Python in Action: 60 Mini Projects to Automate Everything (Part 1): Practical CLI Tools, File Automation, and Data Cleaning with CSV, Excel, and JSON
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Two disciplined patterns instead of a database
“Just use files” is easy to get wrong. These two patterns — ported from a battle-tested sibling app — are what make file-based state sound rather than reckless.
Atomic writes
Write to a temp file in the same dir, then rename() over the target. Rename is atomic on one filesystem — a crash mid-write leaves the complete old file or the complete new one, never a half.
The board heals itself
A single roadmap.json array races when two tools write at once. One file per card makes writes collision-free. Lane order lives in board.json and reconciles on read.
board.json. It writes an item file — the board fixes itself on Threlmark’s next read. Unknown keys are preserved, so the contract is forward-compatible.![DeskFX Free Audio Effects & Audio Enhancer Software [PC Download]](https://m.media-amazon.com/images/I/41fXbDohyuS._SL500_.jpg)
DeskFX Free Audio Effects & Audio Enhancer Software [PC Download]
Transform audio playing via your speakers and headphones
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The numbers can’t drift from the files
Anything computable from item state is computed — so the displayed numbers can never disagree with the underlying JSON. Priority is the clearest example: it’s calculated on read, never persisted.
priority — computed on read
Impact weighted heaviest; effort the only axis that subtracts. Reused verbatim from the original tool, so imported cards rank identically.
Working in Public: The Making and Maintenance of Open Source Software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A handoff is a first-class flow event
The genuinely 2026-shaped part: most building is done by AI agents, so Threlmark closes the loop. Watch a card go from ranked to Done without anyone dragging it.
Handoff → report → self-move
The brief carries a reporting protocol. The agent reports through REST or the filesystem — and a done report moves the card itself.
POST /api/projects/:id/
items/:itemId/reportDirect call. Applied immediately.
drop reports/.json
→ ingested on read Robust even if the server’s down at finish time.
Hi-Spec 17 Piece Metal Hand & Needle File Tool Kit Set. Large & Small Mini T12 Carbon Steel Flat, Half-Round, Round & Triangle Files. Complete in a Zipper Case with a Brush
Versatile Filing for Every Task: Includes 4 full-length 12-inch machinist’s files and 12 metal needle files; perfect for…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A small formula, and an honest hosting caveat
Because items are globally addressable (
Portfolio ranking — status-weighted
In-flight work floats to the top; bottlenecks cost the most, so blockers get nudged up.
Static read-only demo
Seeded data, writes to localStorage. Try-before-you-clone.
Personal Node instance
Password-gated, persistent backed-up THRELMARK_DATA_DIR.
Multi-tenant SaaS
Add accounts + per-tenant isolation. A separate build.
src/lib/*/store.ts is the natural seam — the same boundary that keeps the local tool simple is the one you’d extend for multi-tenancy. The architecture doesn’t fight that future; it just doesn’t pay for it until you need it.
Implications of a Disk-Based Contract System
This approach matters because it enables a highly portable, open, and resilient project management system that can integrate seamlessly with external tools and AI agents. By removing reliance on databases or cloud servers, Threlmark allows users to maintain full control over their data, simplify backups, and avoid vendor lock-in. It also facilitates safer concurrent modifications and supports evolving data schemas without breaking compatibility, which is critical for future-proofing complex workflows.
For developers and teams, this architecture reduces complexity, enhances transparency, and fosters interoperability across diverse tools. It demonstrates a shift toward local-first, file-based systems that can serve as reliable, self-contained hubs for project data, especially in environments where privacy, control, and resilience are priorities.
Background and Evolution of Local-First Systems
Traditional project management tools often rely on cloud-based servers and databases, which can introduce lock-in, reduce transparency, and complicate data portability. For more on this, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Recent trends in local-first and offline-capable systems aim to address these issues by storing data locally and synchronizing selectively. Threlmark’s approach builds on these principles but distinguishes itself by using the disk as the primary contract, rather than a separate database or remote API.
The idea of treating files as the source of truth is not new; however, Threlmark’s implementation emphasizes strict atomic file operations, forward-compatible schemas, and self-healing mechanisms. These features collectively create a system that is robust against crashes, easy to backup, and flexible enough to evolve over time. The system also aligns with broader movements toward open data and interoperability, enabling users to integrate third-party tools without proprietary constraints.
“The core idea is simple: the on-disk layout is the API. This choice cascades into how concurrency is handled, how external tools participate, and how AI agents can autonomously manage tasks.”
— Thorsten Meyer, creator of Threlmark
Uncertainties About Scalability and External Adoption
It remains unclear how well this architecture scales for very large projects or teams with complex workflows. While the design emphasizes safety and simplicity for local use, questions about performance in high-concurrency environments or integration with existing enterprise tools are still open. Additionally, the extent to which external developers and AI agents will adopt this approach remains to be seen, as the system is still in early deployment stages.
Next Steps for Adoption and Development
Threlmark plans to release detailed documentation and open-source the core system, encouraging community experimentation and integration. Future developments may include enhanced AI automation features, improved UI for managing multiple projects, and additional tools for synchronization with cloud services while maintaining the local-first philosophy. Monitoring user feedback and real-world use cases will shape subsequent iterations.
Key Questions
How does Threlmark ensure data safety without a database?
It employs atomic write operations using temporary files and rename() calls, ensuring that partial writes or crashes do not corrupt data.
Can external tools modify Threlmark’s project data?
Yes, since the data is stored as plain JSON files, any tool capable of reading and writing files can participate, promoting interoperability and extensibility.
What are the limitations of this approach for large teams?
Scalability and concurrency in very large projects are still untested, and performance may vary depending on the number of files and external integrations.
Will Threlmark support cloud synchronization?
Future versions may include synchronization options, but the core philosophy remains local-first, with cloud use as an optional extension.
Source: ThorstenMeyerAI.com
