📊 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 approach centers on using the disk as the primary data contract, avoiding traditional databases. This design simplifies synchronization, boosts offline capabilities, and makes data more portable, while maintaining system transparency and resilience.
Threlmark has adopted a novel architecture that treats local disk storage as the definitive source of truth, replacing traditional database systems. This approach is detailed in the original analysis. This approach simplifies data synchronization, enhances offline usability, and improves data portability, making systems more resilient and transparent.
Threlmark’s design centers on storing each piece of data as a separate file on the local disk, with the directory structure acting as a formal contract that defines how data is organized and accessed. Instead of relying on a centralized database, the system uses atomic file writes to prevent corruption and employs tolerant merging techniques to handle concurrent edits and external modifications.
By assigning one file per item, Threlmark reduces race conditions and simplifies conflict resolution, facilitating seamless offline work and easy data recovery. The directory layout is explicit, making it easy for external tools to read and modify data without special permissions. This approach emphasizes transparency, interoperability, and resilience, allowing for straightforward manual editing and integration with other tools.
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.
SANDISK 1TB Extreme Portable SSD (Old Model) – Up to 1050MB/s, USB-C, USB 3.2 Gen 2, IP65 Water and Dust Resistance, Updated Firmware – External Solid State Drive – SDSSDE61-1T00-G25
Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity…
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.
JSON file editor for data management
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.
SABRENT USB-C Lay Flat Docking Station – NVMe M.2 + SATA 2.5”/3.5” SSD/HDD Enclosure, 10Gbps, Tool-Free, Offline Clone Function, USB 3.2 Type-C, for Windows, Mac, Linux (DS-UFNC)
Wide Compatibility – Dual Format Support: Works with M.2 PCIe NVMe SSDs (2242, 2260, 2280) and 2.5”/3.5” SATA…
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.
Implications of Disk as the Single Data Source
This architecture shifts the complexity from managing a centralized database to ensuring file-level data integrity and consistency. For more on this approach, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. It enhances data portability, reduces vendor lock-in, and improves offline capabilities, which are critical for modern, distributed workflows. However, it also introduces new challenges in handling concurrent edits and filesystem overhead, requiring careful design of merge and conflict resolution mechanisms.
Evolution of Local-First Systems and Threlmark’s Approach
Traditional data management relies heavily on databases and server-based architectures, which can introduce lock-in, complicate offline use, and hinder data portability. This trend is explored in the related article. The local-first movement aims to address these issues by prioritizing local storage as the primary data source. Threlmark’s architecture exemplifies this shift, emphasizing file-based data management, explicit directory structures, and atomic operations. This approach aligns with broader trends toward resilient, offline-capable tools that prioritize user control and transparency.
„Treating the disk as the contract simplifies synchronization and makes data more portable, while also keeping the system easy to inspect and extend.“
— Thorsten Meyer, Threlmark developer
Remaining Challenges and Unresolved Questions
It is not yet clear how well Threlmark’s architecture scales with very large datasets or complex collaborative workflows. The effectiveness of conflict resolution and merge strategies in highly concurrent environments remains to be fully tested. Additionally, the impact on performance and filesystem overhead with many small files is still under assessment.
Upcoming Developments and Adoption Milestones
Threlmark plans to refine its conflict resolution mechanisms and optimize filesystem operations to better handle large-scale projects. Broader adoption and integration with external tools are expected to increase, testing the robustness of the architecture in diverse use cases. Future updates may include enhanced user interfaces and automated recovery features to further improve resilience and usability.
Key Questions
How does Threlmark handle concurrent edits?
Threlmark employs atomic file writes and tolerant merge strategies to manage concurrent modifications, reducing conflicts and ensuring data integrity.
Can users manually edit data files?
Yes, the explicit directory structure and individual files make manual editing straightforward, supporting transparency and manual recovery.
What are the main advantages of a disk-based approach?
It improves offline usability, data portability, transparency, and resilience by eliminating reliance on centralized databases and servers.
Are there performance concerns with many small files?
Managing numerous small files can introduce filesystem overhead, and optimizing performance is an ongoing area of development for Threlmark.
Will this architecture work for large, collaborative teams?
The approach shows promise, but scalability and conflict management in highly collaborative environments are still being tested and refined.
Source: ThorstenMeyerAI.com
