📊 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 uses local disk files as the ultimate data source, avoiding traditional databases. This design improves offline usability, simplifies synchronization, and enhances data portability, making systems more resilient and flexible.
Threlmark has adopted a novel local-first architecture that treats disk storage as the definitive source of truth, eliminating the need for traditional databases. This approach is detailed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. This approach enhances offline usability, simplifies synchronization, and promotes data portability, making systems more resilient and transparent.
Threlmark’s system uses one file per data item, with atomic write operations to prevent corruption and race conditions. The directory structure acts as a formal contract, ensuring transparency and interoperability with external tools. This design simplifies data recovery, as the system can reconstruct state from individual files even if parts are corrupted or missing.
To ensure data safety, Threlmark employs atomic file writes—writing to a temporary file before renaming it over the original—and tolerant merging that preserves key fields like IDs and timestamps. These techniques help maintain consistency amid concurrent edits and external interference.
The directory layout is explicitly designed to serve as a data contract, with clear organization at the root and within project folders. This transparency allows manual editing, external tool integration, and easy inspection, fostering an open ecosystem.
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 2TB 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-2T00-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.![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.
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.
atomic file write utility
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 Advances Data Resilience
Using disk storage as the primary data contract shifts the paradigm from centralized databases to decentralized, file-based systems. This approach makes data more accessible, portable, and less dependent on vendor-specific solutions, reducing lock-in. It also enhances offline capabilities, allowing users to continue working without internet access and ensuring data safety through simple, transparent mechanisms. However, this model requires careful handling of concurrent edits and conflict resolution, which can introduce complexity but ultimately results in a more flexible and resilient system.
The Evolution Toward Local-First Data Architectures
Traditional project management tools rely heavily on cloud servers and proprietary databases, which can lead to vendor lock-in and limited offline functionality. Recent developments in local-first data architectures advocate for storing data directly on user devices in plain files. Recent developments in local-first principles advocate for storing data directly on user devices in plain files, enabling offline access, easier synchronization, and greater user control. Threlmark’s implementation exemplifies this shift, emphasizing the importance of treating disk as the authoritative data source.
Previous efforts in this space have highlighted challenges such as data consistency, conflict resolution, and system robustness. Threlmark’s approach addresses these by employing atomic writes, tolerant merging, and explicit directory contracts, setting a new standard for local-first architectures.
“Treating disk as the contract simplifies data management, enhances transparency, and makes systems more resilient to failures. For a detailed analysis, see the original analysis.”
— Thorsten Meyer, Threlmark developer
Remaining Challenges in Implementing Disk as the Data Contract
It is not yet clear how well Threlmark’s approach scales with very large datasets or highly concurrent multi-user environments. While the system employs atomic writes and tolerant merging, the complexity of conflict resolution in more complex scenarios remains to be fully tested and documented. Additionally, manual management of directory structures and files could introduce human error, and the impact on filesystem performance with many small files is still being evaluated.
Upcoming Developments and Testing of Threlmark’s Architecture
Threlmark plans to further refine its conflict resolution strategies and optimize filesystem interactions for larger datasets. Future updates may include enhanced tools for manual conflict resolution, automated integrity checks, and broader adoption in multi-user environments. Observers will watch for real-world testing results and community feedback to assess scalability and robustness.
Key Questions
How does Threlmark handle concurrent edits to the same data item?
Threlmark employs tolerant merging and atomic writes to manage concurrent edits, reducing the risk of conflicts. However, complex conflict scenarios may still require manual resolution or specialized tools.
Can Threlmark’s approach work with large-scale projects?
While the architecture is designed to be scalable, practical limits depend on filesystem performance and conflict management complexity. Ongoing testing aims to clarify these boundaries.
Is manual editing of files safe in Threlmark’s system?
Manual editing is possible and transparent, but it requires understanding the directory structure and data format. Incorrect edits could cause inconsistencies, so caution is advised.
What are the main benefits of treating disk as the contract?
This approach improves offline usability, data portability, transparency, and resilience against system failures, reducing reliance on proprietary databases.
Will Threlmark’s system support multi-user collaboration?
Multi-user support is in development, with current focus on conflict management and synchronization strategies to ensure consistent data across users.
Source: ThorstenMeyerAI.com
