📊 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 definitive data source, simplifying sync, enhancing offline use, and promoting portability. This approach shifts complexity from databases to file management, offering new flexibility and resilience.
Threlmark’s new architecture treats local disk storage as the definitive source of truth, eliminating reliance on traditional databases and servers. This approach enhances offline usability, simplifies synchronization, and improves data portability, offering a fundamentally different way to manage project data.
Threlmark’s system operates on the principle that each data item is stored as a separate file on the disk, with atomic write operations ensuring data integrity. The directory structure itself acts as a formal contract, making data organization transparent and easily accessible for manual or automated editing.
By avoiding centralized databases, Threlmark reduces vendor lock-in and simplifies deployment. The approach also enables seamless offline work, as all data resides directly on the user’s device, and external tools can interact with the files without proprietary interfaces.
To safeguard data consistency, Threlmark employs atomic file writes—writing to temporary files before renaming them—and tolerant merge strategies that handle concurrent edits and missing data gracefully. This reduces the risk of corruption and race conditions while maintaining system resilience.
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.
portable external SSD drive
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.file synchronization software for offline use
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.
atomic file write utility
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 disk storage 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.
Implications of Disk as the Single Data Source
This architecture shifts the complexity from managing a centralized database to ensuring file integrity and conflict resolution at the file level. It offers increased transparency, portability, and offline capabilities, making it attractive for users prioritizing control and resilience. However, it introduces challenges in handling numerous small files and maintaining consistent directory structures, which require careful design and management.
Evolution Toward Local-First Data Management
Traditional project management tools rely heavily on cloud-based databases, which can be opaque, lock-in users to specific platforms, and suffer from connectivity issues. Recent trends in local-first architecture advocate for storing data directly on user devices, emphasizing resilience and user control. Threlmark’s approach is part of this broader movement, applying it specifically to project management via a file-based system that treats the disk as the contract.
“Treating the disk as the contract simplifies synchronization, enhances offline usability, and makes data portable without sacrificing safety or interoperability.”
— Thorsten Meyer, Threlmark developer
Remaining Challenges and Unknowns in Implementation
While the approach offers many benefits, it remains to be seen how well it scales with very large datasets or highly complex project structures. Managing numerous small files could introduce filesystem overhead, and manual conflicts may still occur if directory structures are not carefully maintained. The long-term robustness of conflict resolution strategies in diverse real-world scenarios is still under evaluation.
Next Steps for Threlmark’s Local-First System
Threlmark plans to refine conflict resolution algorithms and optimize directory management to improve scalability. Future updates will likely include enhanced tooling for manual conflict resolution and better integration with external tools that read and write project files. Monitoring user feedback will guide further development to address scalability and usability issues.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark employs atomic file writes, writing changes to temporary files before renaming them to prevent corruption, and uses tolerant merge strategies to handle concurrent edits safely.
Can external tools modify Threlmark data?
Yes, because data is stored as plain files in a well-defined directory structure, external tools can read and write files directly, provided they adhere to the data contract.
What are the limitations of this disk-based approach?
Managing many small files can introduce filesystem overhead, and conflict resolution may become complex in highly concurrent or large-scale environments. Scalability and manual conflict management are ongoing considerations.
Is this approach suitable for all types of projects?
While ideal for offline, portable, and transparent workflows, it may require additional management for very large datasets or highly collaborative environments with frequent concurrent edits.
Source: ThorstenMeyerAI.com
