📊 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 introduces a local-first, file-based architecture where the disk is the authoritative source for project data. This design emphasizes portability, safety, and interoperability, challenging traditional server-based models. The approach enables external tools and AI agents to participate seamlessly.
Threlmark has unveiled a novel architecture that makes disk storage the definitive source of truth for project data, eschewing traditional server or cloud reliance. This design allows external tools, AI agents, and users to interact directly with JSON files on disk, fostering a portable, interoperable, and restartable system.
The core of Threlmark’s approach is the use of a plain folder structure, with a manifest, dependency graph, and individual JSON files for each project component, including one file per roadmap card. This setup removes the need for a server, instead relying on atomic file operations like rename() to ensure data integrity. The system’s design emphasizes openness, with data being accessible and modifiable by any tool capable of reading and writing files, making it highly portable and flexible.
By avoiding a centralized database, Threlmark ensures that all artifacts—cards, lanes, dependencies—are inspectable, versionable, and migration-friendly. The architecture also supports concurrency through atomic writes and tolerant read-merge strategies, allowing multiple tools or AI agents to update data simultaneously without conflicts. The self-healing board structure automatically reconciles discrepancies, maintaining consistency even when external modifications 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
- High-Speed NVMe Performance: Up to 1050MB/s read, 1000MB/s write
- Durable and Water-Resistant: IP65 water and dust resistance, 3-meter drop protection
- Portable and Secure: Includes carabiner loop for easy attachment
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.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/.json
→ ingested on read Robust even if the server’s down at finish time.
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 a Disk-Centric Project System
This architecture challenges the conventional reliance on cloud or server-based databases for project management. By making disk storage the contract, Threlmark enhances data portability, resilience, and transparency. It enables a broader ecosystem of tools, including AI agents, to participate without special permissions or integrations, potentially transforming how teams manage complex workflows and collaborate across tools.
For developers and power users, this approach simplifies backups, migrations, and integrations, as all data resides in plain files. It also reduces dependencies on external services, increasing control and security. Overall, this design could influence future project management tools to adopt more open, decentralized architectures.
Evolution Toward Local-First, File-Based Data Management
Traditional project management tools often rely on centralized servers or cloud services, which can introduce lock-in, reduce transparency, and complicate integrations. Threlmark’s architecture is inspired by the broader ‘local-first’ movement, emphasizing data ownership and portability. Its design builds on prior work in file-based systems, applying proven patterns like atomic writes and tolerant read-merge to ensure safety and consistency.
Previous tools have struggled with fragmentation, with each project maintaining separate lists or boards, making it difficult to ask universal questions like ‘what’s the most important thing to do next?’ Threlmark addresses this by creating a unified, portable data contract rooted in simple files, enabling multi-project hubs that are both flexible and resilient.
“”The on-disk layout is the API. That choice cascades into how concurrency, participation, and automation work in Threlmark.” Learn more about Threlmark’s architecture.”
— Thorsten Meyer
Unanswered Questions About Scalability and Collaboration
It remains unclear how well this architecture scales with very large projects or teams, especially regarding performance and concurrent editing. The system’s reliance on file operations may face challenges in high-frequency update scenarios or distributed environments. Additionally, the user experience for non-technical users and integration with existing tools are still being explored.
Next Steps for Adoption and Development
Threlmark plans to release detailed documentation and developer tools to facilitate wider adoption. Future updates may include enhanced conflict resolution, real-time collaboration features, and integrations with popular IDEs and project management platforms. Observers will watch for community feedback and real-world testing to evaluate the architecture’s robustness and versatility.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic write operations, writing to temporary files and renaming them, preventing partial corruption even during crashes.
Can external tools participate without permission?
Yes, since all data is stored in shared JSON files, any tool capable of reading and writing these files can participate without special permissions.
What are the limitations of this approach?
Potential challenges include scalability for very large projects, handling simultaneous updates in distributed setups, and ensuring user-friendly interfaces for non-technical users.
Will this architecture support real-time collaboration?
Real-time collaboration features are not yet confirmed but are a possible future development, depending on how the system evolves to handle concurrent file modifications.
Source: ThorstenMeyerAI.com
