📊 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 architecture where project data is stored solely on disk as JSON files, making workflows portable, safe, and open. This approach eliminates reliance on servers or databases, enabling seamless external tool integration and AI automation.
Threlmark has unveiled a project management system built entirely around local disk storage, where the filesystem itself serves as the authoritative source of project data, without relying on servers or cloud databases. This design allows for open, portable, and restartable workflows, with external tools and AI agents capable of directly manipulating JSON files on disk.
The core architectural decision in Threlmark is to treat the filesystem as the contract for project data, with all artifacts stored as individual JSON files in a dedicated directory (defaulting to ~/.threlmark). The system eschews traditional databases, instead using atomic file writes and read-merge-update patterns to ensure safety and consistency. This approach enables any external tool, regardless of language, to participate by reading and writing these files, fostering interoperability and openness.
Threlmark’s design includes a manifest (threlmark.json), a dependency graph (links.json), and per-project folders containing metadata, lane orderings, and individual roadmap cards. Shared cards are stored centrally for multi-project referencing, and archived projects are preserved in a separate directory. The system’s self-healing board reconciles its state on each read, ensuring consistency even with external modifications or concurrent updates.
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.
EXLIFBAG File Organizer, Fireproof File Box with Lids, Important Document Organizer Box with Lock, Portable File Folder Organizer with Handle
HIGH QUALITY FIREPROOF FILING BOX: Fireproof lock box is made of double layered non-itchy silicone coated fiberglass which…
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.![DeskFX Free Audio Effects & Audio Enhancer Software [PC Download]](https://m.media-amazon.com/images/I/41fXbDohyuS._SL500_.jpg)
DeskFX Free Audio Effects & Audio Enhancer Software [PC Download]
Transform audio playing via your speakers and headphones
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.
Blue Summit Supplies 50 Project File Folders, Reinforced Straight Cut Tab, 2 Inch Expansion Pocket, Preprinted Project Management Folder Design, Letter Size, Manila, 50 Pack
Expandable Project File Jackets with Preprinted Project Tracking Layout – Dedicated sections for project details, task tracking, follow-up…
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.
Information Technology Project Management (Mindtap Course List)
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.
Advantages of Disk as the Contract in Project Workflows
This architecture fundamentally shifts how project data is managed and shared, emphasizing portability, safety, and interoperability. By avoiding databases, Threlmark ensures that project artifacts are inspectable, easily backed up, and compatible with any tool that can read files. It also enables restartability, as the entire state is stored on disk, preventing data loss from in-memory crashes. This approach simplifies external integrations, including AI agents, which can directly modify project files without intermediary layers.
For users, this means more control over their data, easier migration between tools, and a transparent view of project progress. For developers, it reduces complexity and dependency on proprietary systems, fostering an open ecosystem for project management and automation.
The Evolution of Local-First and File-Based Project Systems
Traditional project management tools rely heavily on centralized servers or cloud services, often locking users into specific platforms and limiting data portability. Threlmark’s approach builds on prior trends toward local-first software, emphasizing user control and data ownership. Its design echoes principles seen in version control systems like Git, which treat files as the primary source of truth and enable seamless collaboration and recovery.
Earlier efforts in local-first workflows focused on individual applications; Threlmark extends this philosophy into multi-project management, combining open data formats with robust file handling techniques. Its atomic write pattern and self-healing board represent mature solutions to concurrency and consistency challenges in file-based environments.
“The on-disk layout is the API. It cascades into how concurrency is handled, why each card is a separate file, and how external tools can participate without permission.”
— Thorsten Meyer
Unanswered Questions About Threlmark’s Scalability and Adoption
It is not yet clear how well Threlmark’s architecture performs with very large projects or in multi-user environments. The system’s effectiveness in real-world, collaborative settings remains to be demonstrated, and the extent of external tool support is still evolving. Additionally, the impact on existing workflows and integrations is yet to be fully assessed.
Next Steps for Threlmark’s Development and Community Adoption
Threlmark plans to continue refining its file-based architecture, improve tooling support, and gather user feedback. Future developments may include enhanced synchronization features, broader integration with external tools, and case studies demonstrating its effectiveness in diverse project environments. Community engagement and documentation will be key to wider adoption.
Key Questions
How does Threlmark handle concurrent updates from multiple external tools?
It uses atomic file writes and a self-healing board that reconciles state on each read, minimizing conflicts and ensuring consistency without locks.
Can Threlmark work with existing project management tools?
Yes, because all data is stored as portable JSON files, external tools can read, modify, and write project artifacts directly, enabling integration with other systems.
What are the limitations of a file-based architecture for project management?
Potential challenges include scalability with very large projects and managing concurrent edits in multi-user environments, which are still being tested in real-world scenarios.
Is Threlmark suitable for team collaboration?
While designed for local-first workflows, future updates may improve multi-user support, but current emphasis is on individual control and open data portability.
Source: ThorstenMeyerAI.com
