📊 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 employs a unique local-first architecture where project data is stored as JSON files on disk, eliminating reliance on servers or databases. This approach enhances portability, safety, and external tool integration, driven by a core design principle: ‘disk is the contract.’
Threlmark has introduced a novel architecture that treats disk storage as the primary contract for project data, removing the need for servers or databases. This design enables seamless external tool integration, improved safety, and full portability, marking a significant shift in how project management tools can operate locally.
The core of Threlmark’s approach is that all project data resides in plain JSON files stored on the user’s disk, with the directory layout serving as the API. This setup allows external tools to read and write data directly, fostering interoperability without lock-in. The system’s architecture is built around the principle that the disk is the single source of truth, with the data root defaulting to ~/.threlmark, but configurable via environment variables.
Key to this design are two safety patterns: atomic file writes—using temporary files and rename operations to prevent corruption—and read-merge-write updates that preserve data integrity and forward compatibility. Each roadmap item is stored as an individual JSON file under the items/ directory, enabling collision-free updates and external modifications. The overall structure includes project metadata, dependency graphs, lane orderings, and shared resources, all stored as separate files, making the system highly inspectable, portable, and restartable.
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.
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 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.
Secure Data Wipe USB – Permanent Hard Drive Erase Tool | Military-Grade Data Sanitization for PC, Laptop, HDD & SSD | Bootable USB Drive – Easy & Secure Data Removal
✔ Permanently Wipe Data – Securely erase your hard drive, ensuring no recovery is possible.
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 a Disk-First Approach Transforms Project Management
This architecture matters because it provides a new model for local-first project tools, emphasizing user control, data portability, and external integration. By avoiding centralized servers and databases, Threlmark enhances data safety and resilience, making it easier for users to back up, migrate, or incorporate external tools. This approach could influence future project management solutions, especially in environments prioritizing privacy and offline access.
Development of Threlmark’s Local-First Design Philosophy
Traditional project tools often rely on cloud servers or databases, which can fragment workflows and limit data portability. Threlmark’s design builds on prior local-first principles, aiming to unify multiple project roadmaps into a single, portable JSON-based system. This shift aligns with broader movements toward user sovereignty over data and interoperability among tools, but with a specific focus on local storage as the primary contract.
The approach is inspired by the limitations of conventional kanban and roadmap tools, which often store data in isolated formats like Notion pages or localStorage. Threlmark’s innovation is to treat the disk as the authoritative source, enabling external tools and AI agents to participate directly, without needing permission or access to proprietary servers.
“The on-disk layout is the API. It’s a simple, robust contract that makes everything else possible—interoperability, safety, and external participation.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Threlmark’s Scalability and Use Cases
It is not yet clear how well this disk-first architecture scales with very large or highly complex projects, or how it performs under heavy concurrent modifications. Additionally, the practical integration with existing tools and workflows remains to be tested in diverse real-world scenarios. Further user feedback and developer experience will clarify these aspects over time.
Next Steps for Adoption and Ecosystem Development
Threlmark plans to release detailed documentation and encourage external tool developers to build integrations based on the file contract. Future updates may include enhancements to synchronization, conflict resolution, and user interface improvements that leverage the underlying architecture. Monitoring user adoption and feedback will be crucial to refining the system’s capabilities and understanding its broader impact.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark uses atomic file writes—writing to a temporary file and renaming it—to prevent corruption. It also employs read-merge-write patterns that preserve data integrity during updates.
Can external tools modify Threlmark data?
Yes, because the data is stored as plain JSON files in a defined directory structure, any tool capable of reading and writing JSON can participate, making the system highly interoperable.
What are the limitations of this architecture?
Potential challenges include scaling to very large projects and managing concurrent modifications in complex workflows. These areas require further testing and development.
Source: ThorstenMeyerAI.com
