📊 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 architecture where project data resides solely on disk as JSON files, removing the need for a centralized server. This design enhances portability, safety, and interoperability, with confirmed implementation details now public.
Threlmark has implemented a novel local-first architecture where project data is stored exclusively as JSON files on disk, making the filesystem the single source of truth. This approach eliminates the need for a server or cloud database, enabling direct, portable, and interoperable access to project artifacts. Disk Is the Contract: Inside Threlmark’s Local-First Architecture. The design decision is confirmed and currently in use, marking a significant shift in project management tools.
Threlmark’s core innovation is that all project information—tasks, dependencies, and progress—is stored as individual JSON files within a dedicated directory (defaulting to ~/.threlmark). The system’s architecture treats these files as the contract, meaning external tools, AI agents, and users all interact with the same files following the same discipline, without relying on a centralized database.
Key to this design is the principle that the filesystem layout is the API. For example, each project has its own folder containing metadata, lane orderings, and individual task files. Shared items, suggestions, reports, and handoffs are organized into dedicated subfolders, ensuring full inspectability and easy migration. This setup allows for complete portability—users can back up, sync, or migrate data simply by copying files—while maintaining consistency and safety through atomic write operations and tolerant read-merge-write cycles.
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.
DSDCDJ File Box with Lock – Portable File Organizer Box with Handle, Sturdy Important Document Organizer with Label, Slide, Reflective Strip for Hanging Letter/Legal Folder
Upgraded File Organizer: The file box is made with tear-resistant 800D polyester fabric and reinforced with thick cardboard…
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 project data backup
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.
![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 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-Based Data Matters for Project Management
This architecture fundamentally changes how project data can be managed, shared, and extended. By removing reliance on a server, Threlmark enhances data portability and reduces lock-in, enabling users to integrate with other tools easily. It also improves safety and resilience, as the system is restartable and resistant to corruption from crashes. For developers and AI integrations, the open file-based format offers a transparent, flexible, and scalable way to interact with project data, fostering a more open ecosystem.
The Evolution of Local-First Project Tools
Traditional project management tools often depend on centralized databases or cloud services, which can fragment data and create lock-in. For a deeper dive into Threlmark’s approach, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Threlmark’s approach builds on prior local-first principles but advances them by making the filesystem the definitive contract. This design aligns with broader trends toward open, portable, and resilient software architectures, and responds to needs for more flexible AI integration in project workflows. The decision to treat disk as the source of truth is a deliberate departure from typical client-server models, emphasizing safety, interoperability, and user control. Learn more about Threlmark’s architecture.
“The core idea is simple: the on-disk layout is the API. This makes the entire system portable, restartable, and open to external tools without any server dependency.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Implementation and Ecosystem
While the architecture is confirmed and in use, details about how external tools, AI agents, and integrations will adopt this model at scale remain under development. It is not yet clear how widely this approach will be adopted outside of Threlmark, or how it will perform under complex collaborative scenarios involving multiple concurrent users or external integrations. Additionally, the long-term evolution of the file format and compatibility strategies is still being refined.
Next Steps for Adoption and Ecosystem Growth
Threlmark plans to release detailed documentation and open-source tools to facilitate integration with other systems. The focus will be on encouraging developers and AI tool creators to adopt the file-based contract, expanding interoperability. Future updates may include enhanced conflict resolution, versioning, and community-driven extensions to the core architecture. Monitoring adoption and real-world use cases will be key to understanding its impact.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark uses atomic file writes—writing to temporary files then renaming—to prevent corruption, and employs tolerant read-merge-write cycles to preserve data integrity during updates.
Can external tools modify project data directly?
Yes, external tools can read and write JSON files directly, following the established directory structure and file conventions, enabling seamless integration.
What are the advantages of this file-based approach?
It enhances portability, safety, and interoperability, allowing easy backups, migrations, and integrations without lock-in or reliance on a central server.
Is this approach suitable for large or collaborative projects?
While promising, the scalability and concurrency aspects are still being tested. The architecture is designed for resilience but may require additional tooling for complex collaboration scenarios.
Source: ThorstenMeyerAI.com
