📊 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 employs a local-first architecture where JSON files on disk serve as the definitive data source. This design simplifies concurrency, portability, and external integrations, challenging traditional database reliance.
Threlmark has introduced a novel approach to project management architecture that relies solely on JSON files stored on disk, eliminating the need for a server or database. This approach builds on the concept of disk as the contract. This system makes the disk the definitive record, enabling high portability, concurrency safety, and external tool integration, according to the developer Thorsten Meyer.
The core architectural decision in Threlmark is that there is no central server or database; instead, all project data resides in a structured set of JSON files on the user’s disk. The main directory, typically ~/.threlmark, contains a manifest, dependency graph, project metadata, and individual files for each roadmap card. This setup allows any external tool to read or modify data directly, provided it adheres to the file structure.
Threlmark’s design emphasizes four properties: inspectability, portability, interoperability, and restartability. Each artifact, such as a project file or card, is stored as a separate JSON file, making it easy to review, back up, or migrate. The system avoids lock-in by enabling simple copying or syncing of files, and it supports external integrations without requiring API permissions. The architecture also ensures data safety through atomic file writes, where temporary files are renamed atomically to prevent corruption during crashes or interruptions.
Additional features include a self-healing board that reconciles lane ordering against existing items, automatically appending missing cards, and removing references to deleted files. This approach simplifies concurrency management, as single-file atomic writes prevent race conditions, and the system’s stateless design means it can restart without losing data.
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.
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
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.
Project Planner: Management Notebooks Organizer & Work Log Book Tracker With Checklist Brainstorming for Entrepreneurs, Managers & Small Business Owners
TURN YOUR IDEAS INTO REALITY: Unleash your creativity with this unique planning notebook, consisting of 224 pages divided…
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.
Tsubosan Hand tool Workmanship file set of 5 ST-06 from Japan
Tsubosan Hand tool file ST-06
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.
Smart Keypad Door Lock with Handle, Smart Door knobs with Lock, Auto Door Lock with Code and App, Keyless Entry Door Knob for Bedroom, Front Door, Smart Home, Apartment, Local Data Storage
3-in-1 Smart Access Upgrade for Every Space – Transform your entryway experience with the KLLOQUE door lock, designed…
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.
Why Disk-Based Data Management Matters for Project Tools
Threlmark’s local-first architecture challenges the conventional reliance on centralized databases for project management. By making the disk the single source of truth, it offers enhanced portability, transparency, and resilience. This approach reduces lock-in, simplifies backups, and allows external tools to participate seamlessly, which could influence future design choices in productivity software. It also demonstrates a practical way to manage concurrency and data integrity without complex infrastructure, potentially inspiring other tools to adopt similar architectures.
The Evolution of Local-First and File-Based Systems
Traditional project management tools often depend on cloud servers and databases, complicating data portability and external integrations. For more on this, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Threlmark’s approach builds on the growing trend of local-first applications, which store data locally to improve privacy and control. The concept of using files as the source of truth has gained traction in the developer community, exemplified by tools like Git and other version-controlled workflows. Threlmark extends this idea into a multi-project hub, emphasizing that the disk can serve as a reliable, safe, and interoperable data store, challenging the assumption that databases are necessary for complex workflows.
“The core idea is that the on-disk layout is the API, and there is no server-of-record. The files are the record, and everything else builds on that.”
— Thorsten Meyer
Unanswered Questions About Scalability and External Use
It is not yet clear how Threlmark’s architecture performs under large-scale or highly concurrent workloads, or how it integrates with existing enterprise systems. Additionally, the extent to which external tools can modify data safely in complex scenarios remains to be tested in real-world use cases.
Future Developments and Community Adoption of Disk-First Approach
Threlmark plans to continue refining its file-based architecture, potentially introducing more robust conflict resolution and collaboration features. The developer community’s response and adoption will also influence whether this approach gains broader traction in project management and productivity tools.
Key Questions
How does Threlmark handle concurrent updates from multiple external tools?
It uses single-file atomic writes and a self-healing board that reconciles discrepancies upon each read, reducing race conditions and ensuring data consistency.
Can external tools modify Threlmark data safely?
Yes, as long as they follow the file structure and atomic write protocols, external tools can participate without risking data corruption.
Is this architecture suitable for large or collaborative teams?
While promising for individual and small-team use, performance and conflict management in larger, distributed environments remain to be evaluated.
What are the main advantages of a disk-based, file-centric system?
It offers portability, inspectability, interoperability, and restartability, making data easy to back up, migrate, and integrate with other tools.
Will Threlmark replace traditional database-driven project tools?
There is no indication of replacing existing tools; instead, it offers an alternative architecture that prioritizes local control and simplicity.
Source: ThorstenMeyerAI.com
