📊 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 architecture uses the disk as the primary source of truth, avoiding traditional databases. This design simplifies data sync, improves offline capabilities, and enhances tool interoperability, making systems more resilient and flexible.
Threlmark has adopted a novel approach where the local disk is treated as the definitive source of truth for all data, moving away from traditional database systems. This design is detailed in the original analysis. This design choice simplifies synchronization, improves offline usability, and makes data portable across tools, which could significantly impact how project management and data systems are built and used.
Threlmark’s system operates on the principle that each piece of data is stored directly as a file on the disk, with one file per item. This approach eliminates the need for a central database or server, reducing complexity and vendor lock-in. Data integrity is maintained through atomic write operations, where updates are first written to a temporary file and then renamed to prevent corruption during crashes or interruptions. The directory structure itself acts as a formal data contract, making the system highly transparent and easy to extend or integrate with external tools.
To handle concurrency and prevent race conditions, Threlmark employs careful merge strategies that tolerate missing or unknown data, ensuring consistent state even in multi-tool environments. The architecture also supports self-healing mechanisms, allowing the system to reconstruct state from individual files if corruption occurs. This design emphasizes resilience, offline capability, and simplicity, offering a different paradigm from traditional centralized data stores.
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.high capacity USB flash drive
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 recovery software for disk corruption
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.
offline data management tools
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.
Impact of Disk as the Data Contract on System Design
This approach shifts complexity from managing centralized databases to ensuring file integrity and consistency at the filesystem level. It exemplifies the principles explained in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. It offers increased transparency, portability, and resilience, enabling users to work offline and avoid vendor lock-in. However, it also introduces challenges related to managing many small files and ensuring consistent directory structures, which require careful design and adherence to the data contract.
Background of Threlmark’s Local-First Architecture Shift
Traditional project management tools rely heavily on centralized databases or cloud services, which can create dependencies, reduce flexibility, and pose synchronization challenges. Threlmark’s approach builds on the principles of local-first design. Threlmark’s approach builds on the principles of local-first design, emphasizing direct file-based data storage that is accessible and modifiable outside the system. This aligns with broader trends in decentralized data management and offline-first tools, but its specific implementation as a formal data contract via directory structures is a distinctive feature.
Recent developments include detailed implementation of atomic file operations, directory structure as a formal contract, and mechanisms for conflict resolution and self-healing, setting a new standard for local-first systems.
“Treating the disk as the ultimate contract simplifies data synchronization and enhances offline usability, making systems more resilient and transparent.”
— Thorsten Meyer
Unresolved Challenges and Future Considerations
While the system’s design offers many advantages, it remains unclear how well it scales with very large datasets or high concurrency scenarios. Managing numerous small files can introduce filesystem overhead, and manual interventions may be required to resolve conflicts or inconsistencies. Details about how the system handles very complex merge conflicts or large-scale synchronization are still emerging, and further testing is needed to confirm its robustness in diverse environments.
Next Steps for Threlmark’s Local-First System Development
Threlmark plans to refine conflict resolution strategies, improve performance with large datasets, and develop tools that facilitate manual recovery and conflict management. Future updates may include enhanced self-healing features, better integration with external tools, and broader adoption of the directory-structure contract model. Observers should watch for official releases and detailed technical documentation as these developments unfold.
Key Questions
How does Threlmark ensure data safety without a traditional database?
Threlmark uses atomic file writes and careful merge strategies to prevent corruption and race conditions, ensuring data integrity through direct filesystem operations.
Can this approach handle large projects with many items?
While scalable for many use cases, managing numerous small files could introduce filesystem overhead. The system’s performance in very large datasets remains under evaluation.
How does the directory structure act as a data contract?
The directory layout explicitly defines how data is organized, making it transparent and accessible for manual editing or external tool integration, provided the structure is adhered to.
What are the main benefits of treating disk as the contract?
This approach enhances data portability, offline usability, and system resilience, reducing dependencies on proprietary databases and cloud services.
What challenges remain with this architecture?
Handling large-scale concurrency, managing many small files efficiently, and resolving complex conflicts are ongoing challenges that require further development.
Source: ThorstenMeyerAI.com
