📊 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, disk-based architecture where JSON files on disk serve as the system’s core data source. This approach enhances portability, safety, and interoperability without relying on a central database.
Threlmark’s latest architectural approach designates disk-based JSON files as the definitive source of project data, eliminating the need for servers or centralized databases. Disk Is the Contract: Inside Threlmark’s Local-First Architecture This local-first design allows external tools, AI agents, and users to interact directly with files, ensuring portability, safety, and interoperability, marking a significant shift in project management tool architecture.
Threlmark operates as a Next.js application built on top of plain JSON files stored locally in the user’s filesystem. Its core principle is that the disk layout itself functions as the API, meaning all project data—such as roadmap items, dependencies, and external suggestions—are stored as individual JSON files within a dedicated directory (defaulting to ~/.threlmark). This setup removes the need for a server, enabling external tools and AI agents to read and modify project data directly, fostering a truly open and portable system.
The system’s architecture includes a manifest (threlmark.json), dependency graph (links.json), and per-project folders containing metadata (project.json), lane configurations (board.json), and individual item files (items/
Two core patterns ensure data safety: atomic writes (write to a temporary file then rename) prevent corruption during crashes, and read-merge-write updates preserve data consistency and forward compatibility. The system’s self-healing behavior, such as reconciling the lane order with existing items, ensures the data remains consistent 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.
![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.
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.
Real-World Android App Projects with Kotlin and Jetpack Compose: Build Production-Style Android Apps with Modern Architecture, API Integration, State Management, Local Data Storage, Practical Projects
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.
Backup Pro 27 – Backup solution – Image Backup – Data backup programme, rescue in case of malware attack, defective hard drive or Windows crashes – compatible with Windows 11, 10
Backup, save and restore data – it's easy! Rescue in the event of a malware attack, defective hard…
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.
Better Office Products 24 Clear Pocket Expanding File Folder with 12 Colored Tabs, Letter Size, Holds 300 Sheets, Project File Organizer, Numbered Index on Cover,(2 Pack Black & Blue)
2 PACK – 24 Pocket Organizers, each with 12 assorted color tabs and two adjoining clear pockets per…
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 Disk as the Single Source of Truth Matters
This architecture fundamentally shifts how project data is managed, emphasizing portability, safety, and interoperability. To learn more about the underlying principles, see Disk Is the Contract. By removing reliance on databases or cloud services, Threlmark enables users to maintain control over their data, facilitate seamless integration with external tools, and ensure resilience against data loss or corruption. This approach is particularly relevant for developers and teams seeking a transparent, flexible, and decentralized workflow, especially in environments where data sovereignty and tool interoperability are priorities.
The Evolution of Local-First Project Tools
Traditional project management tools often depend on cloud servers or proprietary databases, creating fragmentation and lock-in. For a deeper dive into local-first project tools, visit our article on local-first architecture. Threlmark’s approach builds on the local-first movement, which advocates storing data locally to improve control and resilience. Prior efforts, such as localStorage-based tools or simple file exports, lacked the robustness and interoperability now achieved through this architecture. Recent developments in file-system atomic operations and tolerant merge strategies have made such designs more practical and reliable, paving the way for Threlmark’s innovative system.
“The core idea is that the disk layout is the API—no server, no database, just files. This makes everything open, portable, and restartable.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Threlmark’s Architecture
While the architecture is well-defined, details about how external tools and AI agents will be adopted at scale remain unclear. It is also uncertain how the system handles complex concurrent modifications in highly active workflows, and whether any performance limitations arise with very large datasets. Additionally, the extent to which existing project management workflows can transition smoothly to this model is still being explored.
Next Steps for Adoption and Development
Threlmark’s team plans to release further documentation and tooling to facilitate integration with external applications and AI agents. They will also seek feedback from early adopters to refine concurrency handling and usability. Future updates may include enhanced visualization tools and broader support for different file formats, aiming to make this architecture accessible to a wider audience of developers and teams.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark uses atomic file writes, writing updates to temporary files and then renaming them, which prevents corruption during crashes. Its read-merge-write process also preserves data integrity and forward compatibility.
Can external tools modify Threlmark data?
Yes, since data is stored as JSON files, any tool capable of reading and writing files can interact with the data directly, enabling seamless integration and automation.
What are the benefits of this disk-based approach?
This design offers portability (easy backup and migration), interoperability (any tool can join), safety (reliable atomic operations), and restartability (no in-memory state loss).
Is this approach suitable for large or complex projects?
While promising, the scalability and performance of this architecture for very large datasets are still under evaluation, and future updates will address these concerns.
How does this compare to traditional cloud-based project tools?
Unlike cloud tools that rely on remote servers, Threlmark’s local-first approach keeps all data on the user’s disk, providing greater control, privacy, and resilience.
Source: ThorstenMeyerAI.com
