📊 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 single source of truth. This design enables portability, interoperability, and resilience without a central database, transforming project flow management.
Threlmark has unveiled a novel local-first architecture that treats disk-based JSON files as the authoritative source for project data, eliminating the need for a central server or database. This approach allows external tools and AI agents to interact directly with the project files, ensuring portability, transparency, and resilience. The system is designed to handle multi-project workflows with a focus on open, interoperable data management.
The core architectural decision in Threlmark is that all project data resides on disk as JSON files, which serve as the contract for all interactions. The main directory, typically located at ~/.threlmark, contains a manifest file (threlmark.json), a dependency graph (links.json), and individual folders for each project, each holding metadata, lane configurations, and one file per roadmap card within the items/ directory. External tools can read and write these files directly, enabling seamless integration without requiring a server or database.
To ensure data safety, Threlmark employs atomic write operations that write to temporary files before renaming, preventing corruption during crashes. It also uses a read-merge-write pattern that preserves existing data, allowing forward compatibility with unknown fields. The design supports multiple projects, shared items, and archiving, all while maintaining inspectability, portability, and interoperability. This setup makes the entire system restartable, as it relies solely on file states, avoiding in-memory dependencies.
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 "Disk Is the Contract: Inside Threlmark’s Local-First Architecture 3")
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.
disk-based JSON data storage
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.
WORKPRO W051003 8 In. Half Round File, Durable Steel File for Concave, Convex & Flat Surfaces, Comfortable Anti-Slip Grip, Double Cut & Single Cut, Tool Sharpener for Pro's and DIY (Single Pack)
HALF ROUND FILE – Easily shape curves or make straight edges on wood, metal, and plastic with this…
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 Files Matter for Project Management
This architecture shifts the paradigm from centralized databases to a decentralized, file-based approach, enabling greater control, transparency, and flexibility. It allows users to back up, migrate, and modify project data easily, fostering a more open ecosystem where external tools and AI agents can participate without restrictions. For developers and teams, this means more resilient workflows, easier debugging, and enhanced interoperability across tools and platforms.
The Evolution of Threlmark’s Data Management Strategy
Traditionally, project management tools rely on centralized servers or cloud-based databases, which can limit flexibility and transparency. Threlmark’s approach builds on the idea of a single-product roadmap, initially a localStorage kanban, and extends it into a multi-project hub that emphasizes open data. By choosing JSON files stored locally, Threlmark aims to eliminate lock-in, improve portability, and support external integrations, including AI-powered automation. The design reflects a deliberate shift towards a decentralized, resilient architecture that aligns with modern needs for data control and interoperability.
“The on-disk layout is the API. It’s the contract that all tools and agents follow, ensuring consistent, portable, and safe project management.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Threlmark’s Architecture
While the design principles are clear, it is not yet confirmed how well this architecture scales with very large projects or complex workflows. The impact on collaborative editing, concurrency, and real-time updates remains to be tested in broader use cases. Additionally, the specifics of how external tools and AI agents will adopt and interact with this system are still under development, and user feedback is awaited to assess practical limitations.
Future Developments and Adoption Path
Threlmark plans to release further documentation and tooling to facilitate wider adoption of its file-based architecture. The developer community will likely experiment with integrating external tools and AI agents, testing the system’s robustness at scale. Future updates may include enhanced synchronization features, user interface improvements, and broader interoperability support, with user feedback guiding ongoing development.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic write operations that write to temporary files before renaming, preventing corruption during crashes or interruptions.
Can external tools modify project data?
Yes, any tool that can read and write JSON files in the specified directory structure can participate, enabling open ecosystem integration.
What are the benefits of a disk-based, file contract approach?
It provides portability, transparency, resilience, and the ability to back up or migrate data easily without lock-in or reliance on a central server.
Is this approach suitable for large or collaborative projects?
This is still being tested; scalability and real-time collaboration capabilities are areas for future development and validation.
Source: ThorstenMeyerAI.com
