📊 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 project management system where the disk is the primary data source, enabling portability and concurrency without a database. This approach is a significant departure from traditional cloud-based tools.
Threlmark has unveiled a novel architecture that designates the local disk as the single source of truth for project data, eschewing traditional server-based storage. This design enables a portable, interoperable, and restartable system where external tools can participate without permission or central authority, as explained in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. The approach marks a significant shift in project management tools, emphasizing local-first principles to improve control, flexibility, and resilience.
The core of Threlmark’s architecture is that all project data resides in plain JSON files stored on the user’s disk, with no server or cloud dependency. The system uses a specific directory layout, including a manifest (threlmark.json), dependency graph (links.json), and individual files per project and task, stored under a designated data directory, typically ~/.threlmark. This setup makes every artifact inspectable, portable, and interoperable, allowing users to back up, migrate, or integrate with other tools easily.
Key to ensuring data safety and consistency are two disciplined patterns: atomic file writes and read-merge-write updates with tolerant normalization. Atomic writes involve writing to a temporary file and renaming it, preventing corruption during crashes. The read-merge-write process allows the system to grow forward-compatible, preserving unknown fields and handling partial updates gracefully. This design enables multiple tools or agents to modify project data concurrently without conflicts, as each file is independent and collision-free.
Additionally, Threlmark’s architecture includes a self-healing board structure that automatically reconciles the lane order with the current set of task files, adding missing items or dropping nonexistent ones. This ensures the project view remains consistent and up-to-date, even when external modifications occur.
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.![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.
file-based task management app
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.
Information Technology Project Management (Mindtap Course List)
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 Local-First Data Storage Matters in Project Management
This architecture shifts control back to users by removing reliance on centralized servers or cloud services, reducing data lock-in and increasing resilience. It enhances interoperability, allowing diverse tools to work with the same data set seamlessly, and improves safety, as data is stored in a transparent, inspectable format. For developers and power users, this approach simplifies backups, migrations, and integrations, fostering a more open and flexible ecosystem for managing complex projects.
Furthermore, the design supports AI and external tool participation without permission barriers, enabling automation and collaboration at a granular level. As project workflows become more distributed and autonomous, this local-first approach could influence broader trends toward decentralized data management in productivity software.
The Evolution of Project Data Storage and Threlmark’s Innovation
Traditional project management tools typically depend on cloud servers or centralized databases, which can introduce lock-in, reduce transparency, and create single points of failure. While some tools have adopted local storage, they often rely on complex databases or proprietary formats, limiting interoperability and portability.
Threlmark’s approach builds on the principle of local-first design, emphasizing that data should be stored, managed, and controlled locally, with the disk serving as the authoritative source. Its architecture is inspired by prior work on file-based systems and concurrency-safe file operations, but applies these principles specifically to multi-project roadmaps, integrating AI agents and external tools in a seamless, decentralized manner. The concept was first articulated as a way to generalize single-project roadmaps into a multi-project hub that is open, safe, and restartable.
“The core idea is simple: the disk is the contract. All data lives in files, and those files are the only truth.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Threlmark’s Architecture
While the architecture is well-defined, it is still unclear how well it performs under high concurrency or with very large projects. The practical implications for real-world collaboration, especially with multiple external tools modifying data simultaneously, are still being tested. Additionally, the user experience and tooling ecosystem around this approach are in early stages, and broader adoption or integration remains to be seen.
Next Steps for Threlmark and Its Community
Threlmark plans to release detailed documentation and developer tools to facilitate external integrations. Further testing and user feedback will inform improvements, particularly around concurrency handling and UI enhancements. The team also aims to foster an ecosystem of compatible tools that leverage the open file-based contract, encouraging innovation and wider adoption of local-first project management.
Key Questions
How does Threlmark handle concurrent updates from external tools?
It uses atomic file writes and a read-merge-write pattern with tolerant normalization, allowing multiple tools to modify files safely without conflicts.
Is Threlmark suitable for large or complex projects?
The architecture is designed to be scalable, but real-world performance under high concurrency or large data sets remains to be fully tested.
Can external tools fully participate in project management with Threlmark?
Yes, because all data is stored in plain JSON files, any tool capable of reading and writing these files can participate without permission barriers.
What are the advantages of a disk-based contract over cloud-based systems?
It offers greater control, portability, transparency, and resilience, reducing lock-in and enabling offline access and easy backups.
Source: ThorstenMeyerAI.com
