📊 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 innovative local-first architecture uses disk storage as the primary data contract, avoiding traditional databases. This approach improves offline capability, simplifies synchronization, and enhances data portability, with confirmed details on its design and safety mechanisms.
Threlmark has adopted a groundbreaking approach by making disk storage the definitive source of truth for its project management system, eliminating reliance on traditional databases. This design choice enhances offline usability, simplifies synchronization, and promotes data portability, marking a significant shift in how data systems can be architected.
Threlmark’s architecture treats each project’s data as a collection of plain files stored directly on disk, with each item represented by a separate file. This approach removes the need for a centralized database, instead relying on explicit directory structures as a formal contract to facilitate data access and interoperability.
To ensure data integrity, Threlmark employs atomic file writes—writing to temporary files before renaming them to prevent corruption during crashes—and tolerant merging strategies that handle missing or outdated data gracefully. These mechanisms enable safe concurrent edits and external tool integrations without risking data loss or inconsistency.
Using one file per item reduces race conditions and simplifies conflict resolution, as simultaneous edits to different files do not interfere. The system also reconstructs project views by reading these files, enabling self-healing capabilities that recover from partial corruption or missing 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.
SSK Portable SSD 1TB External Solid State Drives, up to 1050MB/s USB C SSD External Hard Drive USB 3.2 Gen2 for iPhone 15/16/17Pro, Windows, Mac, Android Phones and Tablets
Capacity Reminder: Display capacity of 1TB SSD often appears as around 931GB on Windows. MacOS typically shows full…
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.![Express Rip Free CD Ripper Software - Extract Audio in Perfect Digital Quality [PC Download]](https://m.media-amazon.com/images/I/41xx28xHa+L._SL500_.jpg)
Express Rip Free CD Ripper Software – Extract Audio in Perfect Digital Quality [PC Download]
Perfect quality CD digital audio extraction (ripping)
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.
JSON file editor for project management
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 as the Single Source of Truth Matters
This approach fundamentally shifts how data persistence and collaboration are handled in project management tools. By making disk storage the primary contract, Threlmark offers increased resilience against system failures, improved offline capabilities, and enhanced data portability—benefits that are particularly relevant for users who need reliable, flexible workflows without vendor lock-in.
However, this design also introduces new challenges, such as managing numerous small files and ensuring consistent directory structures, which require careful implementation of conflict resolution and merge strategies. Overall, this architecture could influence future development of local-first applications, emphasizing transparency and user control.
Background and Evolution of Local-First Systems
Traditional project management tools rely heavily on centralized databases or cloud services, which can introduce latency, lock-in, and dependency on network connectivity. The concept of local-first architecture has gained traction as a way to empower users with offline capabilities and data sovereignty. Threlmark’s approach builds on this trend by treating disk storage itself as the authoritative source, inspired by principles from projects like Beaker Browser and other local-first frameworks. This development aligns with broader efforts to reduce reliance on proprietary systems and increase transparency in data management.
“Treating disk as the ultimate contract allows for a more resilient, transparent, and flexible system, especially in offline scenarios.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Implementation Details
While Threlmark has outlined its core principles, specific details about conflict resolution, merge conflict handling, and performance at scale remain under development. It is not yet clear how the system manages large projects with thousands of files or how manual editing might impact consistency. Additionally, the long-term robustness of self-healing mechanisms and their behavior under extreme conditions are still being tested.
Upcoming Developments and Adoption Roadmap
Threlmark plans to release more detailed documentation and open-source tools to demonstrate their file-based architecture. Future updates will focus on refining conflict resolution strategies, optimizing performance with large datasets, and expanding integrations with external tools. User feedback from early adopters will likely shape subsequent iterations, with the goal of establishing this approach as a standard for local-first applications.
Key Questions
How does Threlmark prevent data corruption during file writes?
Threlmark uses atomic file writes, where data is first written to a temporary file and then renamed to replace the original, preventing corruption if a crash occurs during the write process.
Can external tools modify data directly in Threlmark’s system?
Yes, because the directory structure and file formats are explicit and transparent, external tools can read and write files directly, provided they adhere to the established structure and data contracts.
What are the main tradeoffs of this approach?
While it improves resilience and portability, managing many small files can introduce filesystem overhead and complexity in maintaining consistency, especially in large projects with frequent concurrent edits.
How does this architecture handle conflicts when multiple tools edit the same file?
Threlmark employs tolerant merge strategies that can reconcile differences and preserve essential data such as IDs and timestamps, though detailed conflict resolution mechanisms are still under development.
Will this approach be suitable for enterprise-scale projects?
It depends on implementation details and optimization; current focus is on small to medium projects, but ongoing development aims to scale the architecture for larger use cases.
Source: ThorstenMeyerAI.com
