📊 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’s innovative approach uses on-disk JSON files as the system’s core, eliminating databases and cloud dependency. This design ensures portability, safety, and interoperability, enabling AI integration and multi-project management.
Threlmark has implemented a novel local-first architecture where the entire project management system relies on JSON files stored on disk, with no server or database involved. This design choice positions the disk as the definitive source of truth, enabling portable, inspectable, and restartable workflows that support multi-project management and AI automation.
The core architectural decision in Threlmark is that all data resides in plain JSON files on the user’s disk, with the file system serving as the API. The main directory, defaulting to ~/.threlmark, contains a manifest (threlmark.json), dependency graphs (links.json), and subfolders for projects, shared items, suggestions, handoffs, reports, and archives. Each project has dedicated JSON files for metadata, lane order, and individual roadmap cards, with a strict one-file-per-item structure.
This structure allows every artifact to be inspected, diffed, and backed up as simple files, avoiding lock-in and enabling easy migration or integration with other tools. The design also emphasizes safety through atomic file writes—writing to a temporary file and then renaming it atomically—and tolerant read-merge-write cycles that preserve unknown fields for forward compatibility. The system self-heals its lane ordering by reconciling the actual files against the lane’s item list each time it is read, ensuring consistency without locks or complex concurrency controls.
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.
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 as the Single Source of Truth Matters
By using the disk as the definitive record, Threlmark ensures that project data is inherently portable and resilient. This approach allows users to back up, migrate, or integrate their project files with any external tool that can read and write JSON, removing vendor lock-in. It also enables robust safety guarantees through atomic file operations, reducing corruption risk. For developers and AI agents, the stateless, file-based system simplifies automation, collaboration, and recovery, making Threlmark suitable for complex multi-project workflows without reliance on centralized servers or databases.
The Evolution of Local-First Project Management Tools
Traditional project management tools often depend on centralized servers and databases, creating barriers for portability and resilience. Threlmark’s approach builds on prior local-first and offline-first designs, emphasizing data ownership and simplicity. Its decision to treat the disk as the contract aligns with trends towards open, interoperable, and resilient systems, addressing issues of lock-in and data loss. The architecture echoes principles seen in other offline-first apps but is distinctive in its explicit use of the file system as the API, with a clear directory structure and safety mechanisms.
This development reflects a broader movement towards decentralized, user-controlled workflows, especially relevant as AI integration and automation become more prevalent in project management.
“The on-disk layout is the API. That one choice cascades into everything else—how concurrency is handled, why there’s one file per card, how external tools can participate without permission, and how AI agents can close their own loop.”
— Thorsten Meyer
Unanswered Questions About Threlmark’s Architecture
While the file-based design offers many advantages, it is not yet clear how well it scales with very large projects or how it handles concurrent multi-user editing in practice. The system’s performance and reliability under complex workflows and integrations with external tools or AI agents remain to be tested in real-world scenarios. Additionally, the specifics of how external tools and AI agents will adopt and interact with the system are still developing.
Next Steps for Adoption and Development
Threlmark plans to release further documentation and tooling to facilitate integration with external applications and AI agents. User feedback and real-world testing will inform enhancements to concurrency handling, scalability, and usability. The project aims to establish a robust ecosystem around its file-based architecture, promoting wider adoption among developers seeking portable, resilient project management solutions.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes—writing to a temporary file and then renaming it—preventing corruption during crashes or interruptions.
Can external tools modify Threlmark data?
Yes, since data is stored as plain JSON files, any tool that can read and write JSON can participate, promoting interoperability.
How does Threlmark handle concurrent updates?
By using one file per item and atomic writes, it avoids race conditions typical of shared lists, though large-scale concurrency testing is ongoing.
Is this approach suitable for multi-user collaboration?
While designed for single-user or controlled environments, future development may address multi-user collaboration more explicitly.
Source: ThorstenMeyerAI.com
