📊 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 designates the disk as the ultimate source of truth, avoiding traditional databases. This approach improves offline usability, simplifies synchronization, and enhances data portability, all while maintaining system transparency.
Threlmark has adopted a novel local-first architecture that treats disk storage as the definitive source of truth, replacing traditional databases. This approach simplifies synchronization, improves offline usability, and enhances data portability, making the system more resilient and transparent for users and developers alike. You can explore the detailed architecture in the original analysis.
Threlmark’s system operates directly on plain files stored on the user’s disk, with each item represented by a separate file. This design eliminates reliance on cloud servers or proprietary databases, allowing users to edit data with simple tools like text editors. The system employs atomic write operations to prevent data corruption during updates, and uses tolerant merge strategies to handle concurrent edits and external modifications.
The directory structure itself functions as a formal data contract, with explicit organization of project files, metadata, and item files. This transparency facilitates interoperability with external tools and manual editing, as all data is accessible and understandable. The architecture also supports self-healing mechanisms, enabling the system to reconstruct its state from individual files if inconsistencies or corruption occur.
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.
SANDISK 2TB Extreme Portable SSD (Old Model) – Up to 1050MB/s, USB-C, USB 3.2 Gen 2, IP65 Water and Dust Resistance, Updated Firmware – External Solid State Drive – SDSSDE61-2T00-G25
Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity…
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.
Dear Editor
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.
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
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 AI with VS Code: Mastering Private, Offline LLM Development: Run Open-Source Models Securely with Ollama, Continue, Llama.cpp, and Zero-Cloud Extensions – Keep Your Code and Data 100% Private
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 are handled in project management tools. By removing the dependency on centralized databases, Threlmark enhances data portability, resilience, and offline capability. Users can work without internet connectivity, and data remains accessible and modifiable with standard tools. For developers, this architecture simplifies deployment and reduces vendor lock-in, but it also shifts complexity toward ensuring data integrity through atomic operations and conflict resolution strategies.
Overall, this design promotes transparency, flexibility, and robustness, potentially influencing how future tools manage data storage and synchronization.
The Evolution of Local-First Data Management
Traditional project management tools rely heavily on centralized databases or cloud services, which can create bottlenecks, lock-in, and reliability issues during connectivity outages. Recent developments in local-first architecture advocate for treating local disk storage as the primary source of truth, emphasizing data accessibility, offline capability, and simplicity. For a deeper dive, see this internal link.
Threlmark’s implementation builds on these principles, shifting the paradigm from centralized data management to decentralized, file-based systems. This approach aligns with broader trends in software design that prioritize user control, transparency, and resilience, especially in environments where internet access is unreliable or where data sovereignty is a concern.
“By making the disk the contract, we simplify synchronization and improve offline usability without sacrificing transparency or control.”
— Thorsten Meyer, Threlmark developer
Remaining Challenges and Open Questions
It is not yet clear how well Threlmark’s approach scales with very large datasets or complex collaboration scenarios involving many concurrent users. The effectiveness of conflict resolution and self-healing mechanisms in highly dynamic environments remains to be fully tested. For more insights, see the original analysis.
Future Developments and Next Steps for Threlmark
Threlmark plans to further refine its conflict resolution strategies, improve performance with large datasets, and develop more comprehensive tooling for manual data management. They also aim to gather user feedback to enhance the robustness of self-healing and synchronization features. Additionally, efforts to standardize directory structures and data contracts may facilitate broader adoption and interoperability with other local-first tools.
Key Questions
How does Threlmark prevent data corruption during updates?
Threlmark employs atomic write operations, where data is first written to a temporary file before replacing the original, preventing corruption if a crash occurs during the write process.
Can users manually edit data files without risking inconsistency?
Yes, the system is designed to tolerate manual edits, but users should follow established formats to avoid conflicts. The architecture includes conflict resolution and self-healing mechanisms to mitigate issues.
What are the main tradeoffs of this local-first approach?
While it improves offline use and transparency, managing many small files and ensuring consistency during concurrent edits can increase complexity and potentially impact performance.
Will this architecture work with large, collaborative projects?
This is still under evaluation. Future updates aim to improve scalability and conflict handling to support more complex collaboration scenarios.
Source: ThorstenMeyerAI.com
