📊 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 makes disk storage the ultimate data contract, avoiding traditional databases. This approach improves resilience, portability, and simplicity. The system uses atomic file writes, one file per item, and explicit directory structures.
Threlmark’s new architecture design treats local disk storage as the definitive source of truth for data, moving away from traditional databases. This approach simplifies synchronization, improves offline usability, and enhances data portability, making the system more resilient and transparent. For a detailed overview, see the original analysis on Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
Threlmark’s system organizes data as individual files stored directly on disk, with each item—such as project cards—represented by a separate file. This design eliminates the need for a centralized database, reducing vendor lock-in and increasing data accessibility. The system employs atomic write operations—writing to temporary files before renaming—to prevent corruption during crashes or interruptions. It also uses tolerant merging strategies, allowing safe updates even when multiple tools or users modify data concurrently.
The directory structure acts as a formal contract, defining how data is organized and accessed. For example, each project has its folder containing metadata, lane order, and individual card files. This transparency enables external tools to read and write data directly, fostering interoperability. Learn more about this approach in Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
While this architecture offers many benefits, it shifts complexity to managing file consistency and conflict resolution, especially as the number of files grows. Developers must carefully design their directory hierarchy and update logic to maintain performance and data integrity.
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.
external SSD portable storage
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.atomic file write software
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 synchronization tools for developers
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.
Smart Keypad Door Lock with Handle, Smart Door knobs with Lock, Auto Door Lock with Code and App, Keyless Entry Door Knob for Bedroom, Front Door, Smart Home, Apartment, Local Data Storage
3-in-1 Smart Access Upgrade for Every Space – Transform your entryway experience with the KLLOQUE door lock, designed…
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 Treating Disk as the Single Source of Truth Matters
This approach fundamentally changes how data persistence and collaboration work in project management tools. By avoiding centralized databases, Threlmark enhances resilience against connectivity issues and vendor lock-in, making data more portable and easier to inspect or modify manually. It also enables faster offline access and simplifies integration with external tools, which is especially valuable for teams working in variable network conditions or with diverse toolchains.
However, this model requires careful handling of concurrent edits and conflict resolution, which can introduce complexity. The safety mechanisms like atomic writes and tolerant merging are crucial to prevent data corruption, ensuring reliability without sacrificing flexibility.
The Evolution of Local-First Data Architectures
Threlmark’s approach builds on the principles of local-first design, which emphasizes local data storage as the primary source and minimizes reliance on cloud or server-based databases. This philosophy gained momentum with tools like Beaker Browser and Automattic’s Calypso, which demonstrated the benefits of decentralized, resilient data management. Threlmark’s specific implementation emphasizes explicit directory structures and file-based data models, making the system transparent and easy to extend.
Prior to this, most project management tools relied heavily on centralized databases, which introduced lock-in, complexity, and potential points of failure. Threlmark’s design shifts this paradigm by making the disk itself the contract, simplifying synchronization and improving offline capabilities.
“Treat your disk as the ultimate contract—no need for a database or server. Use one file per item and atomic writes to prevent data corruption and race conditions.”
— Thorsten Meyer
Outstanding Challenges in File-Based Data Management
While the approach offers many advantages, it remains unclear how well the system handles extremely large datasets or high concurrency scenarios in practice. The effectiveness of conflict resolution and merge strategies under heavy load or complex edits has not been fully demonstrated. For more insights, see the comprehensive coverage in Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
Next Steps for Threlmark’s Local-First System
Threlmark plans to further refine conflict resolution mechanisms and optimize directory structures for larger datasets. User feedback and real-world testing will inform improvements in handling concurrent edits and data recovery. Additionally, the team aims to develop standardized tooling and best practices for external integrations, ensuring broader compatibility and robustness.
Key Questions
How does Threlmark prevent data corruption during updates?
Threlmark uses atomic write operations, where data is first written to a temporary file and then renamed over the original, preventing corruption if a crash occurs during writing.
Can external tools modify Threlmark’s data safely?
Yes, because the directory structure is a formal contract, external tools can read and write files directly, provided they follow the established format and conflict resolution strategies.
What are the main tradeoffs of this architecture?
The approach simplifies deployment and enhances portability but shifts complexity to managing file consistency, merge conflicts, and concurrency, especially as data volume grows.
Is this system suitable for large-scale projects?
While promising, the scalability of Threlmark’s file-based approach in very large projects remains to be fully tested. Handling many small files efficiently requires careful design.
Source: ThorstenMeyerAI.com
