📊 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 approach enhances portability, inspectability, and concurrency without relying on a database. The system’s core decision is that the disk layout is the API, enabling seamless external integration and robust state management.
Threlmark has unveiled a novel local-first architecture that treats the disk as the primary contract for project data, eliminating the need for a centralized server or database. This design choice positions JSON files on disk as the definitive source of truth, enabling greater portability, inspectability, and resilience for project management tools.
The core of Threlmark’s approach is that the on-disk layout is the API, with a specific directory structure containing manifest files, project metadata, individual roadmap cards, and shared resources. This setup allows any external tool or AI agent to read and modify project data directly via filesystem operations, avoiding lock-in or reliance on cloud services.
To ensure data integrity, Threlmark employs atomic file writes using temporary files and rename operations, preventing corruption during crashes. It also uses read-merge-write patterns with tolerant normalization, allowing for forward compatibility and preserving unknown fields for future extensions.
By storing each roadmap item in its own JSON file, Threlmark avoids concurrency issues typical of monolithic JSON arrays. The self-healing nature of the board, which reconciles its lane order with existing items on each read, ensures consistency without locks or complex synchronization mechanisms.
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.
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.
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.
AMBER X Smart Personal Cloud Storage Device Data and Media Files, Built-in 512GB High-Speed SSD with USB Storage, Plex and Home Assistant/iOS/Android/Windows/Mac Compatible
Easy to Set Up and Use Home-based Personal Cloud Data Backup for All Your Smart Devices
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.
Project Planner Notepad – Project Management Organizer Desk Pad – Manage Project Tasks and Meeting Deadlines Effectively – 50 Sheets of Premium 120gsm Paper | Management | A4 Mono
Comprehensive Project Planning: Plan for success with a dedicated project timeline and task sections to track milestones and…
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 Architecture Transforms Project Management
This approach matters because it fundamentally changes how project data is stored, shared, and manipulated. By making the filesystem the source of truth, Threlmark enables seamless external integrations, reduces lock-in, and enhances data portability. It also simplifies recovery and debugging, as every artifact is inspectable and version-controlled through standard tools like diff and git. This design could influence future project management tools seeking more resilient and open architectures.
The Evolution of Local-First and File-Based Systems
Traditional project management tools often rely on centralized servers and databases, which can hinder portability and transparency. Threlmark’s architecture builds on prior local-first principles, emphasizing data ownership and control. Its decision to treat the disk layout as the API echoes trends in version control and file-based workflows, but applies them to project management at a granular level. This development is part of a broader movement towards decentralized, interoperable tools that prioritize user sovereignty over data.
“The key decision was that the disk layout is the API. This makes everything inspectable, portable, and restartable—no database needed.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Threlmark’s Architecture
While the architecture is clearly defined, it is not yet confirmed how well this approach scales with very large projects or multiple concurrent external tools. The practical implications for real-world workflows, such as integration with existing tools or handling complex dependency graphs, remain to be tested. Additionally, the user experience and ease of adoption for teams familiar with traditional cloud-based tools are still uncertain.
Next Steps for Adoption and Development
Threlmark plans to release more detailed documentation and possibly open-source its implementation, allowing developers to experiment and build on this architecture. Future updates may focus on improving integrations, expanding the file format schema, and testing scalability. Observers will watch for community feedback and real-world use cases that validate or challenge the system’s design principles.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes with temporary files and rename operations, preventing corruption during crashes, and employs read-merge-write patterns with tolerant normalization for forward compatibility.
Can external tools modify project data directly?
Yes, any tool that can read and write files in the designated directory structure can participate, making the system highly interoperable.
What are the limitations of a disk-based architecture?
Potential challenges include scalability with very large projects and managing concurrent modifications from multiple external sources, which require further testing and refinement.
Will Threlmark support cloud or server-based integrations?
Currently, the focus is on local-first, filesystem-based operation, but future developments may explore optional cloud sync or remote access features.
Source: ThorstenMeyerAI.com
