📊 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 definitive data source. This design enables portability, interoperability, and resilience without relying on a traditional database.
Threlmark’s latest architecture for project management tools is built entirely on local disk storage, with JSON files acting as the definitive record. This approach eschews traditional databases and servers, making the system highly portable, restartable, and interoperable, according to the developer Thorsten Meyer.
The core design decision is that the on-disk layout itself functions as the API, with files stored in a structured directory hierarchy. Each project has its own folder containing metadata, lane orderings, and individual cards, with files stored under the items/ directory, one per card. Shared cards, suggestions, reports, and handoffs are organized in dedicated subfolders, enabling external tools and AI agents to participate seamlessly.
Data integrity and safety are achieved through atomic file writes—using temporary files and renaming—preventing corruption during crashes. The system also employs read-merge-write patterns, allowing forward compatibility by preserving unknown fields and handling missing or invalid data gracefully. The architecture ensures that every artifact is inspectable, portable, and compatible with any tool that can read and write JSON files, avoiding lock-in or reliance on a centralized server.
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.
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.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.
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/<file>.json
→ ingested on readRobust even if the server’s down at finish time.
A small formula, and an honest hosting caveat
Because items are globally addressable (<projectId>/<itemId>), the Portfolio ranks everything together by a status-weighted score — finishing beats starting, blockers get a boost.
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-First Design Reshapes Project Management
This architecture fundamentally shifts how project data can be stored, shared, and manipulated. By making the disk the single source of truth, Threlmark enables users to back up, migrate, and integrate tools easily without vendor lock-in. It also enhances resilience—since no in-memory state is lost on crash—and promotes interoperability, allowing external tools and AI agents to participate directly through file operations. This approach could influence future designs of local-first tools, emphasizing simplicity and robustness.
Python in Action: 60 Mini Projects to Automate Everything (Part 1): Practical CLI Tools, File Automation, and Data Cleaning with CSV, Excel, and JSON
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The Evolution Toward Local-First, File-Based Systems
Traditional project management tools rely heavily on centralized servers and databases, creating barriers to portability and resilience. Threlmark’s approach builds on the growing trend of local-first architectures, which prioritize storing data locally and syncing as needed. The idea of using files as the source of truth is inspired by previous projects emphasizing open, portable data formats. Threlmark’s specific implementation, with its structured directory layout and atomic file operations, aims to address issues of concurrency, data integrity, and extensibility in multi-project environments.
“The on-disk layout is the API. That choice cascades into how concurrency is handled, why there’s one file per card, and how external tools can participate without permission.”
— Thorsten Meyer
Project Planner: Management Notebooks Organizer & Work Log Book Tracker With Checklist Brainstorming for Entrepreneurs, Managers & Small Business Owners
- Creative Planning Notebook: 224 pages with 112 project sheets
- All-in-One Project Management: Consolidates project details in one place
- Goal and Task Tracking: Sections for objectives, deadlines, and notes
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unresolved Questions About Scalability and Collaboration
It remains unclear how well this disk-based architecture scales with very large projects or teams. The approach’s effectiveness in multi-user, concurrent editing scenarios, especially over networked filesystems, has not been fully tested. Additionally, how external tools and AI agents will coordinate in complex workflows without a central server is still under exploration. Further real-world testing is needed to validate its robustness at scale.
3.5" Disk Storage Box Data Case Holder – Stores up to 100 Disks! – Disc Diskette PC Storage Data Case Tray File
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Development
Thorsten Meyer plans to release more detailed documentation and community tools to facilitate adoption. Future developments may include enhanced conflict resolution mechanisms, improved integration with existing project management workflows, and performance optimizations for larger datasets. Monitoring how external tools and AI agents interact with the system in practical settings will inform ongoing refinements.
Drafting Tools and Ruler Shapes for Architecture – Set of 3 for House Plan Furniture Kitchen, Building, Interior Design
- Includes House, Furniture, and Kitchen Templates: Various templates for architecture and interior design
- Sized for Precision Drawing: Different dimensions with 1/4 inch scale
- Flexible and Durable Material: Sturdy yet flexible for professional use
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Threlmark handle concurrent edits?
It uses atomic file writes and a read-merge-write pattern, which reduces race conditions. However, multi-user, real-time editing scenarios are still being evaluated for scalability.
Can external tools participate without permission?
Yes, any tool that can read and write JSON files in the specified directory structure can participate, making the system highly open and interoperable.
What are the advantages of this disk-based approach?
It offers portability, restartability, no vendor lock-in, and easy integration with other tools and backups, all without relying on a server or database.
Are there any limitations or risks?
Scalability at very large sizes or in multi-user environments over networked filesystems remains untested. Handling complex concurrency scenarios could also pose challenges.
What is the timeline for wider release?
Thorsten Meyer plans to release more documentation and community tools in the coming months, with ongoing testing to refine the system.
Source: ThorstenMeyerAI.com
