📊 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 approach designates disk storage as the primary data contract, eliminating traditional databases. This enhances offline capability, data portability, and system transparency, with confirmed technical implementations. Details on scalability and conflict resolution are still emerging.
Threlmark has adopted a novel architecture that makes disk storage the primary contract for all data, moving away from traditional database reliance. This approach is detailed in the original analysis. This approach simplifies synchronization, enhances offline usability, and improves data portability across tools, confirmed through their technical documentation and recent product updates.
Threlmark’s system treats each project item as a separate file stored directly on disk, employing atomic write operations to prevent data corruption during updates. The directory structure acts as a formal data contract, ensuring transparency and interoperability with external tools. This design allows users to edit files manually or through external applications without risking inconsistency, as the system can reconstruct state from individual files even after failures.
The architecture emphasizes safety through techniques such as atomic file writes—where temporary files are renamed to replace originals—and tolerant merging that preserves essential metadata like IDs and timestamps. This setup reduces race conditions and conflict issues, especially in multi-tool environments, and supports self-healing mechanisms to maintain synchronization.
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.
external disk storage for project management
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.atomic file write storage devices
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.
offline data synchronization tools
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 architecture storage solutions
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 Source of Truth
This approach fundamentally shifts how data persistence and collaboration are handled in project management tools. By removing reliance on centralized databases, Threlmark enhances data portability, resilience, and offline capabilities. It also simplifies integration with external tools, as they can read and write files directly following the established directory structure. However, it introduces new challenges around managing concurrent edits, conflict resolution, and maintaining the integrity of many small files, which require careful design and handling.
Background and Development of Local-First Design
Traditional project management tools rely on centralized databases or cloud servers to store data, which can lead to issues with offline access, lock-in, and data portability. Threlmark’s design builds on local-first principles, emphasizing that the disk should serve as the definitive source of truth. This concept aligns with broader movements toward resilient, user-controlled data management, and is influenced by prior work on file-based synchronization and conflict handling in distributed systems.
Recent updates from Threlmark demonstrate a focus on atomic file operations and explicit directory structures, enabling more transparent and flexible workflows. For a deeper dive, see this detailed overview. While the approach is innovative, it remains in development, with ongoing work to refine conflict resolution and scalability mechanisms.
“Treating the disk as the ultimate contract simplifies synchronization and enhances offline resilience.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Areas for Further Development
While Threlmark’s architecture has demonstrated promising results, it remains unclear how well the system scales with very large projects or numerous concurrent users. Conflict resolution strategies for simultaneous external edits are still being refined, and the impact on performance with many small files has yet to be fully tested. Additionally, the robustness of self-healing mechanisms in complex scenarios is under ongoing evaluation.
Next Steps in Threlmark’s Development and Adoption
Threlmark plans to continue refining its conflict resolution and synchronization algorithms, aiming to improve scalability and performance. They will also focus on expanding integration capabilities with external tools and platforms, testing the system in larger, real-world projects. Further user feedback and technical validation will inform updates, with broader adoption expected as these improvements mature.
Key Questions
How does Threlmark handle concurrent edits from multiple tools?
Threlmark employs tolerant merging and atomic write techniques to minimize conflicts. However, the exact conflict resolution strategies are still being developed to handle complex scenarios effectively.
Can I manually edit project files without risking corruption?
Yes, the directory structure is transparent, and manual edits are possible. The system’s design ensures safety through atomic writes and merge mechanisms, but manual changes should follow the established format to avoid inconsistencies.
What are the main benefits of this architecture for users?
Users gain offline access, data portability, and simplified synchronization. External tools can integrate more easily, and the system is more resilient to failures without relying on centralized servers.
Are there any limitations or risks associated with making disk the contract?
Managing many small files can introduce filesystem overhead and complexity in maintaining consistency. Conflict resolution and performance at scale are ongoing challenges that Threlmark aims to address.
Source: ThorstenMeyerAI.com
