📊 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 project management system where disk-based JSON files serve as the sole record, enabling portability, safety, and external tool integration. This approach challenges traditional database reliance and offers a new architecture for flow management.
Threlmark’s latest architectural design centers on using disk-based JSON files as the definitive record for project data, eliminating the need for a server or database. This approach enables external tools and AI agents to interact directly with project state, making the system highly portable, restartable, and open. The design marks a significant departure from conventional cloud-based or database-driven project management tools, emphasizing local control and simplicity.
Threlmark is a multi-project roadmap tool that operates entirely through JSON files stored on the user’s disk, with no backend server involved. Disk Is the Contract: Inside Threlmark’s Local-First Architecture Its core principle is that the disk itself is the contract—meaning all project data, including cards, dependencies, and AI interactions, are represented as files within a designated directory, typically ~/.threlmark. This setup allows for full inspectability, easy backups, and interoperability, since any tool capable of reading and writing files can participate.
The system employs atomic file writes by first writing to a temporary file and then renaming, ensuring data integrity even during crashes. It also uses a read-merge-write pattern for updates, preserving unknown fields and supporting forward compatibility. Each project card is stored as a separate JSON file, and the system dynamically reconciles the project board on each read, automatically repairing inconsistencies and ensuring the data remains consistent without locks or complex coordination.
This architecture supports external participation, such as AI agents, which can modify project files directly, and external tools, which can sync or back up data without proprietary formats or centralized servers. The design also includes shared items and archiving features, making it suitable for complex workflows involving multiple projects and external integrations.
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.
Advanced System Disc CD – File & Drive Backup/Restore/Recover/Clone
Backup and Restore: Seamlessly back up your entire system or select files and restore them with confidence.
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.
Heavy Duty Job File Folders for Project Tracking Donkey Auto Products (100 Count) (Blue)
HEAVY DUTY CONSTRUCTION: Made from robust 100 lb paper stock that withstands frequent handling, active job files, and…
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 Files Reshape Project Management
This approach fundamentally shifts how project data is stored, accessed, and manipulated, emphasizing control, safety, and interoperability. By eliminating reliance on databases or cloud services, Threlmark reduces dependencies, enhances security, and simplifies backup and migration. It also enables AI agents and external tools to participate seamlessly, potentially automating workflows more effectively. For users and developers, this architecture offers a transparent, restartable, and future-proof system that can adapt as project needs evolve.
The Evolution and Foundations of Local-First Systems
Traditional project management tools often depend on cloud servers or centralized databases, which can introduce lock-in, reduce transparency, and complicate backups. Threlmark’s design draws from broader local-first principles, emphasizing user control and data portability. Its focus on file-based state aligns with recent trends toward open, interoperable systems that prioritize user sovereignty and resilience. The architecture’s emphasis on atomic operations and tolerant merging builds on established practices in file-based databases and version control, adapted for project management workflows.
“The core idea is that the disk is the contract. All project data lives as files, making everything inspectable, portable, and safe from the middleman.”
— Thorsten Meyer, creator of Threlmark
Unanswered Questions About Threlmark’s Architecture
While the design principles are clear, it is not yet confirmed how well the system handles extremely large projects or concurrent external modifications in practice. The scalability and robustness of the read-merge-write pattern under heavy use remain to be tested in diverse real-world scenarios. Additionally, how external AI agents and tools will be secured or controlled to prevent data corruption is still under discussion.
Next Steps for Threlmark’s Development and Adoption
Threlmark plans to release more detailed documentation and user guides to demonstrate the system’s robustness and ease of use. Future updates may include formal security and concurrency guarantees, integration with popular external tools, and performance benchmarks. Broader adoption will depend on community testing and feedback, especially regarding scalability and external integrations.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark uses atomic file writes and a read-merge-write pattern to prevent corruption and ensure data integrity even during crashes or concurrent modifications.
Can external tools or AI agents modify project data?
Yes, since all data are stored as files, external tools and AI agents can directly read and write project files, enabling flexible automation and participation.
Is this architecture scalable for large projects?
It remains to be seen how well the system performs with very large datasets or highly concurrent external modifications, as real-world testing is ongoing.
How does this approach compare to traditional cloud-based tools?
Unlike cloud or server-based tools, Threlmark offers full local control, portability, and no lock-in, but may require more manual management for backups and synchronization.
Source: ThorstenMeyerAI.com
![GPT-5.6 Sol Ultra produces proof of the Cycle Double Cover Conjecture [pdf]](https://deepintellica.com/wp-content/uploads/2026/07/gpt-5-6-sol-ultra-produces-proof-of-the-cycle-double-cover-conjecture-pdf-featured-1-260x140.jpg)
