📊 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 enhances offline capability, simplifies sync, and promotes data portability, shaping new standards for project tools.
Threlmark’s new architecture treats local disk storage as the definitive source of truth, replacing traditional databases with a file-based system that simplifies synchronization, enhances offline usability, and improves data portability.
Threlmark’s approach centers on storing each data item as a separate file within a well-defined directory structure, which acts as the system’s explicit contract. This design eliminates reliance on centralized databases or cloud servers, making data accessible directly through plain files. The system employs atomic write operations—writing to temporary files and then renaming—to prevent corruption during updates, and uses tolerant merge strategies to handle concurrent modifications safely.
By assigning one file per item, Threlmark reduces race conditions and simplifies conflict resolution, allowing multiple tools or users to edit different parts simultaneously without clobbering each other. The directory layout itself is a formal contract, making data structures transparent and easily accessible for manual inspection or external integration. This setup not only boosts resilience in offline scenarios but also enhances interoperability with external tools, as they can read and write files directly following the established structure.
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.offline data management 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-based project management tool
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-first storage device
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 System’s Contract Matters
This approach fundamentally shifts how data persistence and collaboration are handled in project management tools. By making the disk the ultimate authority, Threlmark reduces vendor lock-in, simplifies data recovery, and enables seamless offline operation. It also fosters a more transparent and flexible ecosystem where external tools can interact directly with data files, facilitating interoperability. However, this design introduces new challenges, such as managing many small files and ensuring consistent directory structures, which require careful handling and robust conflict resolution strategies. Overall, it offers a more resilient, portable, and user-controlled architecture that could influence future development in local-first systems.
Background and Development of Local-First Data Models
Traditional project management tools rely heavily on centralized databases or cloud services, which can lead to lock-in, data silos, and challenges with offline access. Recent trends in local-first architecture aim to address these issues by prioritizing local storage and user control. Threlmark’s implementation builds on this movement by treating the disk as the contract, emphasizing file-based data management, atomic operations, and explicit directory structures. This approach aligns with broader efforts in the tech community to create resilient, portable, and interoperable systems that work seamlessly offline and across different tools, as detailed in the original analysis.
“Treating the disk as the contract allows for a more transparent, resilient, and flexible system that is easier to understand and extend, as discussed in this article.”
— Thorsten Meyer, Threlmark developer
Unresolved Questions About Threlmark’s Architecture
It is not yet clear how Threlmark handles complex merge conflicts in practice or how scalable the system remains with a large number of small files. The long-term robustness of the directory-based contract and its impact on performance in extensive projects are still under evaluation. Additionally, the specifics of how external tools will integrate and adhere to the directory structure are still being developed and tested.
Next Steps for Threlmark’s Development and Adoption
Threlmark plans to further refine its conflict resolution mechanisms and optimize performance for larger projects. The team will also work on establishing best practices for external tool integration and manual data management. Expect more detailed documentation and community feedback to shape future iterations. Broader adoption will depend on how well the system scales and how effectively it manages conflicts in real-world scenarios.
Key Questions
How does Threlmark ensure data safety during updates?
Threlmark uses atomic write operations—writing updates to temporary files before renaming—to prevent corruption during crashes or interruptions.
Can external tools modify data in Threlmark’s system?
Yes, external tools can read and write files directly following the directory structure, provided they adhere to the established data contract.
What are the main challenges of this architecture?
Managing many small files, ensuring consistency across directory structures, and resolving conflicts during concurrent edits are key technical challenges.
Is this approach suitable for large-scale projects?
While promising, scalability in large projects remains to be fully tested, especially regarding filesystem performance and conflict management.
Source: ThorstenMeyerAI.com
