📊 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’s new system uses a local-first, file-based architecture where disk files serve as the single source of truth. This design enables portability, inspectability, and restartability without relying on a server or database. The approach is confirmed through the project’s documentation and developer statements.
Threlmark has unveiled a project management system built entirely around a ‘disk is the contract’ architecture, where all data resides in plain JSON files stored locally. This architecture. This approach eliminates the need for a server or database, making the system highly portable, inspectable, and restartable, and marking a significant shift in how project data can be managed and shared.
The core of Threlmark’s design is that the on-disk layout functions as the API, with a designated directory (~/.threlmark) containing all project files, including a manifest, dependency graph, project metadata, lane ordering, individual cards, and external suggestions. Each project and card is stored as a separate JSON file, enabling external tools to read and modify data directly without locking or complex synchronization.
To ensure data safety, Threlmark employs atomic file writes by writing to temporary files and renaming them atomically. It also uses a read-merge-write pattern with tolerant normalization, allowing for forward compatibility and safe updates even when multiple tools modify data simultaneously. The system’s architecture supports interoperability across tools and languages, as any program can read or write files directly.
This design removes reliance on in-memory state, allowing the system to be restarted or migrated easily, and provides transparency through inspectable files, making it straightforward to back up or integrate with other systems.
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.
portable JSON file project management tool
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.local-first architecture software
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.
file-based project management system
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.
atomic file write software
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 a ‘Disk Is the Contract’ Matters for Project Management
This architecture represents a shift toward decentralized, portable, and transparent project data management. By removing the need for a centralized server or database, Threlmark enables users to maintain full control over their data, facilitate collaboration across tools, and reduce vendor lock-in. It also enhances safety and resilience, as data integrity is maintained through atomic operations and forward-compatible file formats. This approach could influence future tools aiming for simplicity, interoperability, and local-first design principles.
The Evolution of Local-First Project Tools and Threlmark’s Unique Approach
Traditional project management tools often rely on cloud servers or centralized databases, which can limit portability and transparency. Threlmark’s approach builds on prior local-first philosophies but distinguishes itself by using the file system itself as the API, with each data artifact stored as a separate JSON file. This design aligns with recent trends toward open, interoperable, and resilient data management, and responds to the fragmentation seen in conventional project management tools.
Earlier efforts in local-first project tools focused on single-project or limited scope. Threlmark generalizes this to multi-project management, emphasizing data portability, open formats, and external tool participation. The architecture reflects lessons from battle-tested file handling, emphasizing atomicity, tolerant normalization, and self-healing data structures.
“The core idea is that the on-disk layout is the API — every piece of data is a file, and that simple choice cascades into safety, portability, and interoperability.”
— Thorsten Meyer, lead developer
Remaining Questions About Threlmark’s File-Based System
While the architecture is well-documented and demonstrated in prototypes, it is not yet clear how well this system performs at scale or under heavy concurrency. Details about real-world adoption, user experience, and integration with existing tools are still emerging. Additionally, the long-term stability of the file format and how it handles complex collaboration scenarios remain to be tested in broader deployments.
Next Steps for Adoption and Development of Threlmark’s Architecture
Threlmark plans to release the system for wider testing, gather user feedback, and develop integrations with popular external tools. Further, the team aims to refine the architecture for larger teams and more complex workflows, potentially introducing versioning or conflict resolution mechanisms. Monitoring community adoption and real-world use cases will be key to understanding its impact.
Key Questions
How does Threlmark ensure data safety without a database?
It employs atomic file writes by writing to temporary files and renaming them atomically, preventing partial updates or corruption.
Can external tools modify Threlmark data?
Yes, since data is stored as plain JSON files, any tool that can read and write JSON can participate, enabling interoperability.
Is the system suitable for large teams or complex projects?
While designed for safety and portability, its performance at scale and handling of complex collaboration are still under evaluation.
What are the advantages of a file-based approach over traditional databases?
It offers portability, inspectability, transparency, and avoids vendor lock-in, making data easy to back up, migrate, and integrate.
Source: ThorstenMeyerAI.com
