📊 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, file-based architecture where JSON files on disk serve as the definitive record for project data. This approach emphasizes portability, safety, and interoperability without relying on databases or cloud services.
Threlmark has implemented a novel local-first architecture that treats disk-stored JSON files as the definitive source of project data, eliminating the need for cloud or database dependencies. This approach allows external tools and AI agents to interact directly with project artifacts, making the system highly portable and resilient. The design choice underscores a shift toward decentralized, user-controlled project management.
The core architectural principle of Threlmark is that there is no central server or database; instead, all project data resides in JSON files stored on the user’s disk, specifically in the ~/.threlmark directory. This directory contains manifest files, project metadata, lane configurations, individual roadmap cards, and shared resources, all organized in a way that makes each artifact inspectable, portable, and interoperable.
This file-based system supports atomic writes through temporary file renaming, ensuring data integrity even during crashes. It also employs a read-merge-write pattern that preserves unknown fields for forward compatibility, allowing external tools to modify data without breaking existing configurations. The system’s design enables multiple tools to participate seamlessly, as they simply read and write files, avoiding lock-in or reliance on server infrastructure.
Furthermore, Threlmark uses one file per item (card), which prevents race conditions and simplifies concurrent updates. The lane order is stored separately in a self-healing ‘board.json’ file that reconciles itself with the current set of items on each read, ensuring consistency without complex locking mechanisms.
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.
EXLIFBAG File Organizer, Fireproof File Box with Lids, Important Document Organizer Box with Lock, Portable File Folder Organizer with Handle
HIGH QUALITY FIREPROOF FILING BOX: Fireproof lock box is made of double layered non-itchy silicone coated fiberglass which…
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.
local-first data integrity tools
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.
JSON file version control system
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 Filesystem Matters for Project Data
This architecture shifts control back to users by removing dependence on centralized servers or cloud storage, making project data more portable and resilient. It enables seamless integration with other tools, simplifies backups, and reduces lock-in risks. For developers and teams, this means greater flexibility, easier collaboration, and enhanced data safety, especially in environments with unreliable internet or strict privacy requirements.
The Evolution of Local-First Project Management Tools
Traditional project management tools often rely on cloud services or centralized databases, which can introduce lock-in, privacy concerns, and dependency on network connectivity. Threlmark’s approach builds on the growing trend of local-first applications, emphasizing user control and data portability. Its design draws inspiration from battle-tested file handling patterns, such as atomic writes and tolerant merge strategies, to ensure safety and forward compatibility. This development aligns with broader movements toward decentralized, user-centric software architectures.
“Using disk as the contract means every artifact is inspectable and portable, making project data more resilient and interoperable.”
— Thorsten Meyer, Threlmark developer
Remaining Questions About Scalability and Integration
It is not yet clear how well this disk-based architecture scales with very large projects or numerous concurrent users. While atomic file operations are robust for individual updates, the impact on performance with extensive data or high-frequency changes remains to be tested. Additionally, how this approach integrates with existing enterprise workflows or cloud-based collaboration tools is still under exploration.
Next Steps for Threlmark and the Local-First Model
Threlmark plans to continue refining its file-based system, including performance optimizations and enhanced external tool support. Future developments may include better synchronization mechanisms for multi-user environments and integrations with popular development platforms. The team also aims to gather user feedback to improve usability and expand the ecosystem of compatible tools.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic write techniques, writing to temporary files before renaming, which prevents corruption during crashes. It also employs read-merge-write patterns to preserve data integrity and compatibility.
Can external tools modify Threlmark data?
Yes, since all data is stored as plain JSON files, any tool capable of reading and writing JSON can participate without special permissions or APIs.
What are the limitations of this disk-based approach?
Potential challenges include scalability with very large projects and managing concurrency in multi-user environments, which are areas for ongoing development.
Is this approach suitable for enterprise or team use?
While ideal for individual or small-team workflows, additional features and synchronization mechanisms would be needed for large-scale, multi-user collaboration.
How does this architecture compare to traditional cloud-based tools?
It offers greater control, portability, and resilience, but may lack some of the real-time collaboration features of cloud solutions unless further integrated.
Source: ThorstenMeyerAI.com
