📊 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 architecture designates the disk as the ultimate data contract, replacing databases with plain files. This approach improves resilience, offline capability, and interoperability, but introduces new concurrency challenges.
Threlmark’s new architecture treats the local disk as the definitive source of truth for data, eliminating the need for traditional databases or cloud servers. This approach is detailed in the original analysis. This design simplifies synchronization, improves offline usability, and enhances data portability, positioning the disk itself as the contract that defines the system’s state.
Threlmark’s approach centers on storing each data item as an individual file within a structured directory, with atomic write operations ensuring data integrity during updates. This method allows for concurrent editing without conflicts, as each file operates independently. The directory layout itself acts as a formal contract, making data structures transparent and accessible for manual inspection or external tools.
To safeguard data, Threlmark employs techniques such as temporary file writes and tolerant merging, which prevent corruption and facilitate conflict resolution. These safety measures are designed to handle external interference and system failures gracefully, ensuring consistent data even in complex multi-tool environments.
This paradigm shift from database reliance to disk-based storage emphasizes simplicity, resilience, and interoperability, but also introduces challenges related to managing numerous small files and maintaining directory structure integrity. For more on this approach, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
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.
SANDISK 128GB Ultra Flair USB 3.0 Flash Drive, SDCZ73-128G-G46, Black
High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard…
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.
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
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.
Local AI with VS Code: Mastering Private, Offline LLM Development: Run Open-Source Models Securely with Ollama, Continue, Llama.cpp, and Zero-Cloud Extensions – Keep Your Code and Data 100% Private
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.
Impact of Disk as the Single Data Source
This approach fundamentally changes data management in project tools by removing dependencies on centralized databases, making systems more resilient to network failures and easier to extend or modify. It enables offline work without synchronization issues and reduces vendor lock-in, fostering greater user control and transparency.
However, this method shifts complexity to ensuring file safety, conflict resolution, and maintaining directory structures. It may require new workflows for developers and users, especially when dealing with many small files or manual edits.
Evolution Toward Local-First Data Management
Traditional project management tools rely heavily on cloud-based databases, which can introduce latency, lock-in, and dependency on network connectivity. This evolution toward local-first principles is discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Recent trends favor local-first principles, emphasizing local storage and synchronization, to improve resilience and user control.
Threlmark’s design builds on these principles, pushing the idea further by making the disk itself the primary contract, rather than a secondary storage layer. This approach aligns with broader movements advocating for data ownership and offline-first capabilities, responding to user demands for more reliable, portable, and transparent tools.
“Treating the disk as the contract simplifies synchronization and makes data more portable and resilient.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Risks of File-Based Storage
While the disk-as-contract model offers resilience and transparency, it introduces challenges in managing many small files, ensuring consistency across manual edits, and handling complex merge conflicts. It is not yet clear how well this approach scales in large or highly collaborative environments, or how it compares in performance to traditional database systems under load.
Additionally, the specific mechanisms for conflict resolution and self-healing are still being refined, and their effectiveness in real-world scenarios remains to be fully demonstrated.
Next Steps for Threlmark’s Disk-First System
Threlmark plans to continue refining its conflict resolution and self-healing mechanisms, aiming for broader adoption and testing in diverse project environments. Future developments may include improved tooling for manual file management, enhanced conflict detection, and integration with external tools that respect the directory structure contract.
Further user feedback and real-world case studies will inform ongoing improvements, with an eye toward scaling the architecture for larger teams and more complex workflows.
Key Questions
How does Threlmark prevent data corruption with file-based storage?
Threlmark uses atomic file writes—saving changes to a temporary file before renaming it over the original—to prevent corruption during crashes or interruptions.
Can this system handle concurrent edits from multiple tools?
Yes, by assigning one file per item and employing tolerant merge strategies, Threlmark minimizes conflicts and allows safe concurrent editing, though managing conflicts remains a key challenge.
What are the main advantages of this architecture?
It offers enhanced resilience, offline usability, data portability, and transparency, reducing reliance on vendor lock-in and centralized databases.
Are there any downsides or limitations?
Managing many small files can introduce filesystem overhead and complexity, and conflict resolution in collaborative environments may require careful handling.
Will this approach scale for large teams or complex projects?
This remains to be fully tested; ongoing development aims to address scalability and performance concerns as adoption grows.
Source: ThorstenMeyerAI.com
