📊 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 entirely on disk as JSON files, making it portable, inspectable, and resilient. This approach removes the need for a central database, enabling external tools and AI agents to interact seamlessly.
Threlmark’s latest architecture design centers on using disk files as the definitive record for project data, removing the need for a server or database. This local-first approach makes project management data portable, inspectable, and resilient, enabling external tools and AI agents to operate directly on the files.
The core of Threlmark’s design is that all project information—such as cards, dependencies, and workflows—is stored in plain JSON files on the local disk, specifically in a directory like ~/.threlmark. The system’s architecture treats these files as the source of truth, meaning external tools, AI agents, and the user interface all access and modify the same files directly, without relying on a centralized database or server.
This approach simplifies concurrency handling through atomic file writes, where updates are written to temporary files and then renamed, ensuring data integrity even if crashes occur during writes. The system also employs a read-merge-write pattern, allowing it to tolerate unknown fields and grow the data schema without breaking compatibility.
By organizing data into one file per item, along with separate files for lane arrangements, dependencies, and external suggestions, Threlmark ensures that each artifact is inspectable, portable, and interoperable. This design supports versioning, migration, and integration with third-party tools, all without lock-in or complex synchronization mechanisms.
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.
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.
17Pcs File Tool Set with Carry Case,Premium Grade T12 Drop Forged Alloy Steel, Precision Flat/Triangle/Half-round/Round Large File and 12pcs Needle Files/1 brush
Premium Forged Alloy Steel: 4 pcs precision large file are made by T12 Drop Forged Alloy Steel, 12…
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.
atomic file write tools for Windows/Mac
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-First Design Changes Project Management
This architecture shifts the paradigm of project management tools from centralized, server-based systems to a decentralized, local-first approach. It enhances data portability, allowing users to back up, migrate, or integrate their project data easily. It also improves resilience and transparency since every artifact is a simple file that can be inspected, diffed, and versioned with standard tools. For developers and AI integrations, this means easier interoperability and more control over workflows, reducing reliance on proprietary platforms.
Background and Evolution of Threlmark’s Architecture
Traditional project management tools often depend on centralized servers and databases, which can lead to lock-in, data silos, and difficulties in migration or external integration. Threlmark was designed to address fragmentation in roadmaps by generalizing a single-product roadmap into a multi-project hub, emphasizing openness and portability. Its recent shift to a purely file-based system builds on lessons from similar applications, emphasizing atomic operations and schema flexibility, to create a resilient, restartable system that external tools and AI agents can reliably interact with.
“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 external tools can participate without permission.”
— Thorsten Meyer
Unresolved Questions About Scalability and Adoption
It is not yet clear how well this file-based architecture scales with very large projects or teams, or how it performs under high concurrency. Additionally, the extent of adoption by external tools and AI agents remains to be seen, as does the system’s ability to handle complex dependency graphs or real-time collaboration scenarios.
Next Steps for Threlmark’s Development and Ecosystem
Threlmark plans to further develop integrations with external tools and AI agents, testing the robustness of its file-based approach at larger scales. Future updates may include enhanced user interfaces for managing large projects, improved conflict resolution mechanisms, and expanded documentation to facilitate third-party tool development. Monitoring adoption and real-world use cases will be key to assessing the approach’s long-term viability.
Key Questions
How does Threlmark ensure data consistency without a server?
It uses atomic file writes—writing updates to temporary files and then renaming them—to prevent corruption during crashes. The system also employs a read-merge-write pattern, tolerating unknown fields and schema evolution.
Can external tools modify Threlmark data directly?
Yes, since all data is stored as JSON files in a shared directory, any tool that can read and write files can participate, enabling interoperability without special permissions.
What are the limitations of a disk-based approach for project management?
Potential challenges include handling very large projects, high concurrency, and real-time collaboration, which may require additional synchronization or conflict resolution mechanisms not yet detailed.
Is this approach suitable for team-based collaboration?
While the architecture supports external tool integration and portability, its effectiveness for team collaboration at scale remains to be tested in real-world scenarios.
Source: ThorstenMeyerAI.com
