📊 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 architecture relies on JSON files stored on disk as the system’s core data source, eliminating the need for a server and enabling open, portable, and restartable workflows. This approach emphasizes simplicity and safety through atomic file operations.
Threlmark’s new architecture relies entirely on JSON files stored locally on disk as the source of truth, removing the need for a centralized server or cloud storage. This approach emphasizes simplicity and safety through atomic file operations. This design choice enables open data, portability, and safer concurrency, fundamentally changing how project management tools can be built and used.
Threlmark’s core innovation is that all project data resides in plain JSON files on the user’s disk, with the directory structure serving as the API. The root directory, typically ~/.threlmark, contains manifest files, project folders, and per-item JSON files. This setup allows any external tool or user to read, modify, or migrate data without vendor lock-in, as all artifacts are inspectable and portable. For more details, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
The system emphasizes safety and concurrency through two key patterns: atomic file writes, achieved by writing to temporary files and renaming, and read-merge-write updates that preserve data integrity and forward compatibility. The architecture also includes mechanisms for self-healing, with the system reconciling lane ordering and project state on each read, ensuring consistency without locks or shared memory.
By avoiding a database, Threlmark ensures that the data remains accessible, modifiable, and restartable across different environments, making it suitable for multi-project management and AI integration where external tools can participate seamlessly.
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.
portable JSON file editor
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.
BUFFALO LinkStation 210 4TB 1-Bay NAS Network Attached Storage with HDD Hard Drives Included NAS Storage that Works as Home Cloud or Network Storage Device for Home
Value NAS with RAID for centralized storage and backup for all your devices. Check out the LS 700…
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 Data Storage Matters for Project Management
This architecture fundamentally shifts how project data can be managed, shared, and integrated with AI tools. It removes vendor lock-in, simplifies backups and migrations, and enhances safety through atomic operations. For users, this means more control, transparency, and resilience in managing their workflows and data.
The Evolution of Local-First Tools and Threlmark’s Unique Approach
Traditional project management tools often rely on centralized servers or cloud services, which can introduce lock-in, data portability issues, and dependency on network connectivity. Threlmark’s approach builds on the growing trend of local-first applications, emphasizing data ownership and safety. Its design is influenced by prior work in file-based systems and concurrency safety patterns, but it distinguishes itself by making the directory layout a formal contract and avoiding any in-memory state or databases.
This approach aligns with broader movements toward open data standards and decentralized workflows, providing a practical example of how complex project management can be handled entirely through local files.
“The core idea is that the on-disk layout is the API, making the data open, portable, and safe without a database.”
— Thorsten Meyer, creator of Threlmark
Unanswered Questions About Threlmark’s Implementation and Adoption
It is not yet clear how well this architecture scales with very large projects or teams, or how external tools and AI agents will integrate in practice at scale. Additionally, the long-term stability of the file-based contract and its compatibility with other tools remains to be seen as the system is still in development and sharing details.
Next Steps for Threlmark and Its Ecosystem
Threlmark’s developer plans to release more detailed documentation and possibly open-source the core components, encouraging community experimentation. Future updates may include enhanced AI integration, improved self-healing mechanisms, and broader tool support, aiming to demonstrate the viability of disk-based project management at scale.
Key Questions
How does Threlmark handle concurrency without a database?
It uses atomic file writes with temporary files and renaming, combined with read-merge-write updates that preserve data integrity and forward compatibility.
Can external tools modify Threlmark’s data safely?
Yes, because all data is stored as inspectable JSON files following a strict directory structure, allowing any tool that can read/write JSON to participate.
What are the benefits of this disk-based architecture?
It offers portability, transparency, safety from crashes, no lock-in, and easy migration or backup options.
Is this approach suitable for large teams or complex projects?
This remains to be proven; scalability and collaborative editing at scale are areas for future testing.
Will Threlmark support integration with AI agents?
Yes, the design explicitly supports AI participation through file-based reports, handoffs, and suggestions, enabling automated workflows.
Source: ThorstenMeyerAI.com
