📊 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 system’s core data store. This design enables portability, safety, and interoperability without relying on servers or databases. The approach is a significant shift from traditional cloud-based project tools.
Threlmark has adopted a novel architecture where all project data resides on disk as plain JSON files, eliminating the need for a server or cloud storage. This approach makes the system portable, restartable, and interoperable, and is designed to support external tools and AI agents seamlessly.
The core design decision is that the disk itself acts as the contract for all data. Files are stored in a dedicated directory (~/.threlmark), with a clear structure: a manifest, project metadata, lane ordering, individual item files, and shared resources. This setup ensures that all artifacts are inspectable, portable, and compatible with any tool that can read/write files.
Threlmark emphasizes safety through disciplined file operations. Atomic writes are achieved by writing to temporary files and renaming them, preventing corruption during crashes. Updates use a read-merge-write pattern, allowing for forward compatibility and preserving unknown fields, which enables external tools and AI agents to participate without breaking the system.
By using one file per item, the system avoids concurrency issues common in monolithic JSON arrays. The lane structure in ‘board.json’ self-heals on read, reconciling with existing item files and dropping missing or deleted items automatically. This ensures the project view remains consistent without locks or complex coordination.
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.![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.
eufy Security eufyCam S330 (eufyCam 3) 4-Cam Kit, Security Camera Outdoor Wireless, 4K with Integrated Solar Panel, Face Recognition AI, Expandable Local Storage, Spotlight, No Monthly Fee
Crystal-Clear Night Surveillance: Achieve superior night vision with the eufy 4k camera's Starlight system, delivering 4K quality and…
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.
YvnShine 50 Pack Job Folder for Project Management, Heavy Duty Manila File Jacket 10×12 Inch, Preprinted Cost Tracking & Invoice Organization, Construction Project Management Files
COMPREHENSIVE PROJECT MANAGEMENT SYSTEM: Professional manila folder designed for contractors and project managers. Organize work orders, service documentation,…
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 shifts the paradigm from cloud-dependent, server-based tools to a local-first, open, and portable system. It allows users to own their data fully, integrate external tools easily, and ensure safety and consistency without complex infrastructure. For developers and teams seeking control, this design offers a robust foundation for building resilient, interoperable project workflows.
Background of Threlmark’s Design Philosophy
Traditional project management tools often rely on cloud servers and databases, which can introduce lock-in, privacy concerns, and dependency on external infrastructure. Threlmark’s design builds on prior ideas of local-first software, emphasizing data ownership and simplicity. Its architecture reflects a response to fragmentation in project roadmaps and a desire for more integrated, open solutions. The concept of using disk as the system’s contract aligns with broader trends in open data and portable workflows.
“The core idea is that the disk is the contract. All data lives as files, making everything inspectable, portable, and safe from server failures.”
— Thorsten Meyer, creator of Threlmark
Unresolved Aspects of Threlmark’s Architecture Adoption
It is not yet clear how well this approach scales with very large projects or how it performs under heavy concurrent modifications. Additionally, the ecosystem of external tools and AI integrations is still evolving, and broader adoption remains to be seen. The long-term stability and community support for this file-based model are also uncertain.
Future Developments and Adoption Pathways
Threlmark plans to continue refining its file-based system, potentially developing more tools for integration and automation. Broader adoption by developer communities interested in local-first workflows could expand, and further documentation may improve interoperability. Monitoring how the system handles larger-scale projects will be key to understanding its scalability and robustness.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes—writing to temporary files and renaming them—plus read-merge-update patterns that preserve data integrity even during crashes or concurrent modifications.
Can external tools modify Threlmark data?
Yes, because all data is stored as plain JSON files, any tool that can read and write files can participate, making the system highly interoperable.
What are the limitations of this disk-based approach?
Potential challenges include scaling to very large projects and managing complex concurrent edits. Its effectiveness depends on disciplined file management and careful synchronization.
Is this approach suitable for team collaboration?
It can support collaboration through shared file directories, but may require additional tooling or synchronization strategies for real-time multi-user editing.
What is the next step for users interested in Threlmark?
Exploring the current documentation, trying out the open-source setup, and participating in community discussions will help users understand its capabilities and limitations.
Source: ThorstenMeyerAI.com
