📊 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 new architecture makes disk storage the definitive data source, removing reliance on traditional databases. This approach improves offline use, data portability, and system transparency. The development emphasizes a shift toward file-based, local-first systems.
Threlmark’s latest system design treats local disk storage as the definitive source of truth for data, eliminating the need for traditional databases or cloud servers. This approach enhances offline usability, simplifies data synchronization, and offers greater transparency and portability, making it a significant shift in how project management tools can operate.
Threlmark’s architecture is built around the principle that the disk itself is the ultimate contract for data. Instead of relying on centralized databases, each piece of data—such as project cards, lane orders, or metadata—is stored in individual files, often in plain text or JSON formats. Changes to data are handled through atomic file operations, ensuring consistency even during crashes or power failures. The directory structure acts as a formal contract, defining how data is organized and accessed, which promotes interoperability with external tools.
This design simplifies synchronization, as tools can read and write files directly without complex APIs or middle-layer databases. It also enhances offline capabilities, allowing users to work without network connectivity while maintaining data integrity. Threlmark employs strategies like atomic writes and tolerant merging to prevent corruption and handle concurrent edits. This makes the system resilient to external interference and easy to extend or inspect manually.
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.
external 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.
Contemporary Project Management (MindTap Course List)
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.
![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.
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.
Local Data Storage in Kotlin: Managing Databases in Android Environments (The Android Developer's Playbook)
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-Centric Approach Reshapes Data Management
This shift to a disk-as-the-contract model fundamentally changes how data persistence, collaboration, and tool integration are approached. By avoiding traditional databases, Threlmark reduces vendor lock-in, increases transparency, and improves data portability. It enables faster recovery from failures, easier manual editing, and seamless integration with other tools that understand the file structure. However, it also requires careful handling of concurrent edits and conflict resolution, which can introduce new complexities but ultimately leads to a more flexible and resilient system.
Background and Evolution of Threlmark’s Local-First Philosophy
Traditional project management and productivity tools rely heavily on centralized databases and cloud servers, which can introduce issues of lock-in, latency, and offline limitations. Threlmark’s approach is part of a broader movement toward local-first architectures, emphasizing user control, data transparency, and resilience. The idea of treating local disk storage as the primary data source has been explored in various open-source projects but has gained renewed interest with Threlmark’s latest implementation. This development builds on prior efforts to simplify data handling and improve interoperability by making the storage layer explicit and file-based.
Previous versions relied on external databases or proprietary formats, which often complicated synchronization and hindered offline use. The new architecture replaces these with a structured directory of plain files, each representing an individual data item, which can be manually inspected, edited, or merged. This evolution reflects a shift toward more open, transparent, and user-controlled data management practices.
“Treating the disk as the contract allows for a more transparent, resilient, and portable system that sidesteps many issues associated with traditional databases.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Areas for Further Development
While the architecture offers many advantages, several aspects remain under development or unproven at scale. Managing a large number of small files can introduce filesystem overhead and performance issues, especially on slower devices or networked filesystems. Conflict resolution during concurrent edits, particularly when external tools modify files outside the system’s control, is complex and still evolving. Additionally, the long-term robustness of self-healing mechanisms and manual file edits remains to be thoroughly tested in diverse real-world scenarios.
Upcoming Improvements and Testing Phases for Threlmark’s Architecture
Threlmark plans to refine conflict resolution strategies, optimize file handling for large projects, and improve user interfaces for manual editing and inspection. Further testing is expected in real-world environments to evaluate system resilience, performance, and interoperability with external tools. The development team is also exploring automation of consistency checks and enhanced self-healing features to simplify maintenance. Community feedback and open-source collaboration will likely shape future iterations of this architecture.
Key Questions
How does Threlmark handle data synchronization across devices?
Threlmark relies on the file system itself for synchronization. Changes are made directly to files, and the system can detect modifications through timestamps or checksums, enabling it to sync data across devices or with external tools that adhere to the directory structure.
Can I manually edit files in Threlmark’s system?
Yes, the directory structure is transparent, and individual files can be opened, edited, and merged manually. However, care must be taken to maintain data consistency, especially during concurrent edits.
What are the main technical challenges of this approach?
Handling concurrent edits, conflict resolution, and managing filesystem overhead for many small files are key challenges. Ensuring data integrity during crashes and updates also requires careful implementation of atomic operations and tolerant merging.
Is this approach suitable for large-scale projects?
While promising, performance and scalability depend on implementation details. Ongoing testing aims to address these issues, but large projects may require additional optimizations.
Source: ThorstenMeyerAI.com
