📊 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 employs a local-first architecture where project data resides solely on disk as JSON files, eliminating the need for a server. This design enhances portability, safety, and interoperability, enabling AI and external tools to participate seamlessly.
Threlmark’s new approach to project management architecture leverages local disk storage as the definitive source of truth, removing the need for a server or cloud-based database. Disk Is the Contract: Inside Threlmark’s Local-First Architecture This design allows external tools, including AI agents, to interact directly with project data stored as JSON files, ensuring portability, safety, and interoperability.
The core architectural decision in Threlmark is that there is no server-of-record; instead, all project data resides on the user’s disk in a structured file system. The data root defaults to ~/.threlmark, containing a manifest (threlmark.json), dependency graphs (links.json), and individual project folders with metadata, lane configurations, and one file per roadmap card under the items/ directory. External tools and AI agents can read and write these files directly, enabling seamless participation without permission barriers.
This file-based system is designed for safety and robustness through disciplined patterns such as atomic writes—where temporary files are renamed atomically—and read-merge-write updates that preserve existing data while allowing forward compatibility. The architecture supports restartability; since all state is stored in files, there is no in-memory state to lose, and the system can recover from crashes or interruptions easily.
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.
Samsung T7 Portable SSD, 1TB External Solid State Drive, Speeds Up to 1,050MB/s, USB 3.2 Gen 2, Reliable Storage for Gaming, Students, Professionals, MU-PC1T0T/AM, Gray
MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to…
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.
Aiibe 64 GB Flash Drive USB Flash Drive 64GB Thumb Drive USB 2.0 Memory Stick Zip Drive Backup Jump Drive Single 64GB 64G USB Drive for PC Laptop
Large Data Storage Capacity: Flash Drive with 64GB capacity, meet your needs of daily use on work, school,…
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.
Hi-Spec 17 Piece Metal Hand & Needle File Tool Kit Set. Large & Small Mini T12 Carbon Steel Flat, Half-Round, Round & Triangle Files. Complete in a Zipper Case with a Brush
Versatile Filing for Every Task: Includes 4 full-length 12-inch machinist’s files and 12 metal needle files; perfect for…
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 a Disk-Based Contract Transforms Project Management
This architecture fundamentally shifts how project data is managed, shared, and extended. Learn more about Threlmark’s local-first architecture By making the filesystem the authoritative record, Threlmark enhances data portability, allowing users to back up, migrate, or integrate with other tools effortlessly. It also enables external AI agents and third-party tools to participate directly, facilitating automation and collaboration without complex permissions or server dependencies. This approach supports a more resilient, transparent, and flexible workflow, especially valuable in multi-project environments where fragmentation and lock-in are common issues.
The Evolution of Local-First Project Tools and Threlmark’s Unique Approach
Traditional project management tools often rely on centralized servers or cloud services, which can introduce lock-in, reduce transparency, and complicate data portability. Discover how Threlmark’s architecture promotes data portability Threlmark builds on the local-first philosophy, similar to other tools that store data locally, but distinguishes itself by defining the disk as the contract—every artifact is a file, making the entire system restartable and interoperable. Thorsten Meyer’s detailed design emphasizes safety through atomic file operations and tolerant update patterns, ensuring data integrity even in concurrent environments. This approach aligns with broader trends towards decentralization and user control in software architecture.
“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, and how AI agents can participate without permission.”
— Thorsten Meyer
Unresolved Questions About Threlmark’s Scalability and Integration
While the architecture promises high safety and portability, it is not yet clear how well it scales with very large projects or how it integrates with existing enterprise workflows. Details about performance under heavy load, multi-user scenarios, or complex external integrations remain to be tested or publicly documented.
Next Steps for Adoption and External Tool Compatibility
Threlmark is expected to continue refining its file-based system, potentially releasing more detailed documentation and tooling to facilitate wider adoption. Future developments may include enhanced support for multi-user environments, performance optimizations, and integrations with popular project management or automation platforms. Observers will watch for community feedback and real-world use cases to evaluate scalability and robustness further.
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 atomically—to prevent corruption during crashes or interruptions.
Can external tools or AI agents modify Threlmark data?
Yes, since all data is stored as files in a known structure, external tools and AI agents can read and write directly to participate without special permissions.
What are the advantages of a disk-based architecture?
It offers portability, transparency, restartability, and interoperability, enabling easy backups, migrations, and integrations with other tools.
Are there any limitations to this approach?
The scalability with very large projects or multi-user scenarios is still uncertain, and performance under heavy concurrent access has not yet been fully demonstrated.
Source: ThorstenMeyerAI.com
