📊 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, file-based architecture where JSON files on disk serve as the system’s core data store. This approach ensures portability, safety, and interoperability, challenging traditional cloud-based project tools.
Threlmark’s latest design approach centers on using on-disk JSON files as the definitive source of project data, eliminating the need for a server or cloud storage. This architecture enables a portable, restartable, and interoperable project management system that handles concurrency and external tool participation without a database.
Threlmark’s core innovation is its ‘disk is the contract’ principle, where all project information resides in a structured directory of JSON files stored locally. The system’s root defaults to ~/.threlmark, containing key files like threlmark.json and links.json, along with project-specific folders holding metadata, lane orderings, and individual task cards. Each card is a separate JSON file, facilitating atomic updates, easy diffing, and external tool integration.
This file-based approach ensures data portability—users can back up, sync, or migrate their project data easily—and guarantees that the system is restartable, as it relies solely on the filesystem state. The design also emphasizes safety through atomic file writes, using temporary files and rename operations to prevent corruption during crashes. Moreover, the architecture supports forward compatibility by preserving unknown fields during updates, allowing tools to evolve independently.
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.
Hi-Spec 17 Piece Metal Hand & Needle File Tool Kit Set. Large & Small Mini T12 Carbon Steel Flat, Half-Round, Round & Triangle Files. Complete in a Zipper Case with a Brush
Versatile Filing for Every Task: Includes 4 full-length 12-inch machinist’s files and 12 metal needle files; perfect for…
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.![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.
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.
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.
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.
USB 2.0 High Speed Laptop USB to USB PC Data File Transfer Cable Link Direct Copy Between 2 Computers for XP,Vista,Windows7,8 (32/64 bit),win10
High Speed: This is high-speed USB 2.0 chip,the actual test speed is about 480Mb/s (the actual speed also…
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 Local-First Architecture Changes Project Management
This approach fundamentally shifts how project data is stored and manipulated, removing reliance on centralized servers or cloud services. It empowers users with full control over their data, enhances interoperability with other tools, and reduces lock-in risks. Additionally, the architecture allows external AI agents and tools to participate seamlessly, fostering automation and collaboration without complex permissions or integrations.
By making the data inspectable and portable, Threlmark addresses common fragmentation issues in project roadmaps and task management, offering a resilient, transparent, and flexible system suited for developers and teams prioritizing local control and simplicity.
The Evolution of Local-First and File-Based Project Tools
Traditional project management tools often rely on cloud-based databases, creating dependencies on external servers and risking lock-in. Learn more about Threlmark’s local-first architecture. Threlmark’s design draws inspiration from local storage and filesystem-based workflows, emphasizing data portability and safety. Its architecture echoes broader trends in local-first software, where users retain control over their data, and systems are designed to be resilient to network outages and service disruptions.
Prior to this, tools like Notion or Trello stored data centrally, requiring internet access and risking data lock-in. Threlmark’s approach, by contrast, stores every piece of information as individual files, enabling straightforward backups, migrations, and external integrations. This design also aligns with principles seen in version control systems, where atomic commits and file diffs ensure data integrity and traceability.
“The core idea is that the on-disk layout is the API, making the data portable, restartable, and interoperable without a database.”
— Thorsten Meyer
Remaining Questions About Threlmark’s File-Based System
It is not yet clear how well this architecture scales for very large projects or teams with complex collaboration needs. While atomic writes and self-healing boards address concurrency and consistency, real-world performance and conflict resolution in highly active environments remain to be tested. Additionally, the extent of external tool support and integration with other project ecosystems is still evolving.
Upcoming Developments and Adoption of Threlmark’s Architecture
Developers and teams interested in Threlmark’s approach can expect ongoing enhancements to external tool integrations, performance optimizations, and user interface improvements. Future updates may also explore standardized schemas for interoperability and broader community adoption, potentially influencing how local-first project tools evolve.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes, where updates are written to temporary files and then renamed, preventing corruption even during crashes.
Can external tools modify Threlmark data?
Yes, because the data is stored as plain JSON files, any tool that reads and writes JSON can participate without special permissions.
What are the main benefits of this file-based approach?
It offers portability, restartability, interoperability, and eliminates lock-in, giving users full control over their project data.
Is this system suitable for large teams or complex projects?
While promising, its scalability and conflict handling in highly active environments are still being evaluated.
Source: ThorstenMeyerAI.com
