📊 Full opportunity report: Disk Is the Contract: Inside Threlmark’s Local-First Architecture on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
TL;DR
Threlmark’s local-first architecture makes disk storage the primary data contract, simplifying sync and enhancing offline capabilities. This approach avoids traditional databases, favoring file-based data management.
Threlmark’s new architecture treats disk storage as the definitive source of truth, eliminating the need for traditional databases and cloud servers. This approach is detailed in the original analysis. This design choice enhances offline usability, simplifies data sync, and improves data portability across tools, making systems more resilient and transparent.
Threlmark’s approach centers on storing each data item as a separate file in a well-structured directory layout, with atomic write operations to prevent corruption. This method ensures data safety during concurrent edits and system failures. The directory structure functions as a formal contract, enabling external tools to read and modify data directly, fostering interoperability. The system employs self-healing mechanisms to reconstruct views from individual files, maintaining consistency even when files are missing or corrupted. This architecture shifts complexity from centralized databases to file management, requiring careful handling of merge conflicts and concurrency but resulting in a more transparent, flexible system that works well offline and across multiple tools. For a deeper dive, see our internal coverage.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.
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.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.
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/<file>.json
→ ingested on readRobust even if the server’s down at finish time.
A small formula, and an honest hosting caveat
Because items are globally addressable (<projectId>/<itemId>), the Portfolio ranks everything together by a status-weighted score — finishing beats starting, blockers get a boost.
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 Source of Truth
This architecture fundamentally changes how data persistence and collaboration are handled in project management tools. By making the disk the primary contract, Threlmark offers a system that is highly portable, resilient to outages, and free from vendor lock-in. It simplifies data recovery and enhances offline capabilities, which are critical in environments with unreliable internet. However, it also introduces new challenges, such as managing concurrent file access and ensuring data integrity through atomic operations and conflict resolution. This approach could influence future design patterns for local-first applications, emphasizing transparency and user control over data.
As an affiliate, we earn on qualifying purchases.
Background and Evolution of Local-First Data Management
Traditional project management tools rely on centralized databases or cloud services, which can create dependencies, latency, and lock-in. This trend is discussed in detail in the original analysis. The concept of local-first architecture has gained traction as a way to improve resilience and user control. Threlmark’s design builds on these principles by treating the disk as the contract, inspired by the idea that files are inherently transparent and portable. This approach aligns with recent trends toward offline-first systems and open data formats, aiming to reduce reliance on proprietary storage solutions and facilitate seamless integration with external tools.
“Treating the disk as the ultimate contract allows for a more resilient, transparent, and portable system that works offline and across tools.”
— Thorsten Meyer, Threlmark developer
As an affiliate, we earn on qualifying purchases.
Unresolved Challenges and Open Questions
It is not yet clear how Threlmark handles complex merge conflicts during concurrent edits, especially in multi-user environments. The scalability of managing numerous small files and the potential filesystem overhead are also still being evaluated. Additionally, the long-term robustness of self-healing mechanisms in diverse failure scenarios remains to be tested in real-world deployments.
As an affiliate, we earn on qualifying purchases.
Next Steps for Threlmark’s Local-First System
Threlmark plans to refine conflict resolution strategies and optimize file management for larger projects. Future updates may include enhanced tooling for manual conflict resolution and better visualization of data integrity. Broader adoption and real-world testing will help validate the architecture’s resilience and performance, guiding further improvements.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Threlmark prevent data corruption during crashes?
It employs atomic write operations, where updates are first written to a temporary file before replacing the original, preventing corruption if a crash occurs during writing.
Can external tools modify Threlmark data directly?
Yes, the directory structure acts as a formal contract, allowing external tools to read and write data files without special permissions, fostering interoperability.
What are the main tradeoffs of this architecture?
While it simplifies portability and offline use, managing many small files and resolving merge conflicts can increase complexity and filesystem overhead.
How does Threlmark handle concurrent edits?
The system uses tolerant merging and conflict resolution strategies to ensure data consistency during simultaneous modifications.
Is this approach suitable for large-scale projects?
This is still under evaluation; managing many files and ensuring performance at scale remain challenges to be addressed in future development.
Source: ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
