📊 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 local-first approach makes disk the ultimate data contract, replacing databases with simple, resilient file-based storage. This enhances offline capability, data portability, and system transparency.
Threlmark has adopted a novel architecture where the local disk is treated as the definitive source of truth, eschewing traditional databases. This approach simplifies data synchronization, improves offline usability, and makes data more portable across tools, marking a significant shift in how project data is managed. For a detailed explanation, see the original analysis.
Threlmark’s system relies on one file per data item, using atomic write operations to prevent corruption and race conditions. The directory structure acts as a formal data contract, making it easy for external tools to read and modify data without proprietary interfaces. This design prioritizes transparency, resilience, and ease of extension, allowing users to work directly with plain files that reflect the current state of their projects.
Key safety mechanisms include atomic file writes—writing to a temporary file before renaming—and tolerant merging that preserves essential metadata like IDs and timestamps. These ensure data integrity during concurrent edits or unexpected failures. The approach also enables self-healing, where the system reconstructs views from individual files, reducing dependency on a central database or server.
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.
Samsung T7 Portable SSD, 1TB External Solid State Drive, Speeds Up to 1,050MB/s, USB 3.2 Gen 2, Reliable Storage for Gaming, Students, Professionals, MU-PC1T0T/AM, Gray
MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to…
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.high capacity USB flash drive
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 recovery software for JSON files
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 tools
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.
Impacts of Disk as the Single Data Source
This architecture shifts the paradigm from centralized databases to decentralized, file-based data management. It enhances offline capabilities, reduces vendor lock-in, and simplifies data recovery. For users, this means more control over their data, easier integration with external tools, and increased system resilience. For developers, it introduces new challenges in managing file concurrency and conflict resolution but ultimately results in a more transparent and flexible system.
Evolution of Data Management in Project Tools
Traditional project management tools rely heavily on centralized databases or cloud services, which can introduce lock-in, complicate offline use, and obscure data structure. Threlmark’s approach builds on the growing trend towards local-first, peer-to-peer, and file-based systems, emphasizing user control and system transparency. This development aligns with broader movements advocating for open, interoperable, and resilient data architectures.
“Treating the disk as the contract simplifies data handling and enhances offline usability, making the system more resilient and flexible.”
— Thorsten Meyer, Threlmark Developer
Unresolved Challenges and Future Risks
It is not yet clear how well this architecture scales with very large datasets or complex collaboration scenarios involving many simultaneous users. The potential for manual errors or conflicts in manual file editing remains a concern, and the system’s ability to handle extensive concurrent modifications without conflicts is still being tested. For more insights, see the original analysis.
Next Steps for Threlmark’s Local-First System
Threlmark plans to further develop conflict resolution mechanisms, improve self-healing features, and test scalability with larger datasets. User feedback and real-world usage will guide enhancements, particularly around multi-user collaboration and automated conflict management. Expect updates that refine the directory structure and safety protocols to support broader adoption.
Key Questions
How does Threlmark prevent data corruption during file writes?
Threlmark uses atomic write operations, where data is first written to a temporary file, then renamed over the original, preventing corruption if a write is interrupted.
Can external tools safely modify Threlmark data?
Yes, the directory structure is a formal contract, allowing external tools to read and write files directly, provided they follow the agreed format.
What are the main advantages of this architecture?
It offers offline capability, data portability, transparency, and resilience against server or cloud failures, reducing vendor lock-in and simplifying data recovery.
What challenges does this approach face?
Managing concurrent edits, conflict resolution, and scaling with large datasets are ongoing challenges that Threlmark aims to address in future updates.
Source: ThorstenMeyerAI.com
