📊 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 project data is stored as JSON files, making it portable, safe, and open. This approach enables AI agents to manage workflows without centralized servers, emphasizing simplicity and resilience.
Threlmark has revealed a novel, local-first architecture that treats disk storage as the definitive contract for project data, eliminating reliance on centralized servers or databases. This design allows external tools and AI agents to interact directly with project files, enabling a more open, portable, and resilient workflow architecture. The approach is a significant departure from traditional cloud-based project management systems and emphasizes simplicity and safety.
The core of Threlmark’s system is a Next.js application that operates entirely on JSON files stored locally in a designated directory (~/.threlmark). The fundamental principle is that the on-disk layout functions as the API, with no server of record. This means all project metadata, task cards, dependencies, and external suggestions are stored as individual JSON files, each representing a specific artifact.
This architecture enables complete inspectability, as files can be viewed, diffed, and backed up with standard tools. It also promotes interoperability, allowing any tool that can read and write JSON to participate in the workflow. The design supports restartability, as there is no in-memory state to lose; the system relies solely on the state of the files. The choice of a home directory (~/.threlmark) rather than a project-specific folder facilitates shared access across multiple apps and tools.
The system’s safety relies on disciplined file operations: atomic writes via temporary files and renaming, and tolerant merge strategies that preserve unknown fields and maintain forward compatibility. Each project comprises multiple files—metadata, lane orderings, individual task cards, external suggestions, handoffs, and reports—organized into dedicated folders. Shared items and archived projects are also stored as files, ensuring full traceability and portability.
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.
JSON file project management tools
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.
disk-based data backup 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.
file-based workflow automation 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 a Serverless, File-Based System
This architecture shifts the paradigm of project management tools by removing the need for centralized servers or databases, reducing lock-in and increasing control for users. It enhances data portability, as all project artifacts are stored as plain files that can be easily backed up, migrated, or integrated with other tools. The approach also improves safety, as atomic file operations prevent corruption during crashes or interruptions.
Furthermore, this design facilitates external AI agents to participate directly in workflow management, closing the loop from task prioritization to completion without intermediary systems. For users and developers, this means more transparent, customizable, and resilient project management, especially suited for workflows where control and data sovereignty are priorities.
Evolution Toward a Local-First, Open Data Model
Traditional project management tools often rely on cloud-based servers and proprietary databases, creating lock-in and complicating local-first architectures. Threlmark’s approach builds on prior efforts to decentralize data, but its key innovation is treating disk storage as the API contract. This method echoes principles from file-based databases and version-controlled workflows, emphasizing atomic operations and forward compatibility.
The idea of a disk as the source of truth is not new, but Threlmark’s implementation applies it specifically to local-first architecture for multi-project roadmaps, external integrations, and AI workflows. The system’s architecture is designed to be simple yet robust, enabling external tools to participate without needing permission or complex APIs. This development aligns with broader trends toward open, decentralized data management and AI-assisted workflows.
“The on-disk layout is the API. That one choice cascades into everything else—how concurrency is handled, why there’s one file per card, and how external tools can participate without permission.”
— Thorsten Meyer
Remaining Questions About Implementation and Adoption
While the architecture is clearly defined, it is still early to assess how well this approach scales for larger, more complex projects or how it integrates with existing enterprise workflows. Details about performance under heavy load, collaboration in multi-user environments, and adoption by larger teams remain unconfirmed. Additionally, the long-term stability of relying solely on file-based storage without a server layer is yet to be tested in diverse real-world scenarios.
Next Steps for Threlmark and User Adoption
Threlmark plans to release further documentation and tooling to facilitate external integrations and AI participation. User feedback from early adopters will shape future enhancements, especially around multi-user collaboration and advanced AI workflows. The project’s developers aim to demonstrate how this architecture can support scalable, resilient project management in varied environments, with potential expansion into enterprise settings.
Key Questions
How does Threlmark handle concurrent edits from multiple tools?
It uses atomic file writes and a self-healing board structure that reconciles differences on read, reducing race conditions and conflicts.
Can external tools modify Threlmark data without permission?
Yes, since the data is stored as open JSON files, any tool capable of reading and writing these files can participate without explicit permission, provided it follows the contract.
What are the advantages of a disk-based architecture over cloud-based systems?
It offers increased data control, portability, safety from corruption, and the ability to operate offline without dependency on external servers.
Is this approach suitable for large, multi-user teams?
While promising for individual and small-team workflows, it remains to be seen how well it scales for large, multi-user environments with complex collaboration needs.
Source: ThorstenMeyerAI.com
