📊 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 architecture makes disk storage the primary source of truth, replacing databases with file-based data management. This approach improves offline usability, simplifies sync, and enhances transparency, with ongoing development around data safety and integration.
Threlmark has adopted a novel architecture where the local disk is treated as the definitive source of truth, eliminating the need for traditional databases or server-based storage. This approach is detailed in the original analysis. This approach emphasizes file-based data management, making data more accessible, portable, and resilient, which could significantly impact how project management tools operate offline and across tools.
Threlmark’s system organizes data into individual files per item, with atomic write operations to prevent corruption. The directory structure acts as a formal data contract, allowing external tools to read and modify data directly without proprietary APIs or databases. This design simplifies synchronization, enhances offline capabilities, and reduces vendor lock-in, as data remains in plain, human-readable files.
To ensure data safety, Threlmark employs atomic file writes—writing to temporary files before renaming—and tolerant merging that preserves key fields like IDs and timestamps. The approach also leverages self-healing mechanisms for reconciling data views, making the system resilient to corruption or external interference. Managing many small files introduces filesystem overhead and requires careful directory design but offers improved concurrency and conflict avoidance compared to monolithic data stores.
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.
SANDISK 1TB Extreme Portable SSD (Old Model) – Up to 1050MB/s, USB-C, USB 3.2 Gen 2, IP65 Water and Dust Resistance, Updated Firmware – External Solid State Drive – SDSSDE61-1T00-G25
Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity…
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.
Hands-on Data Analytics for Business
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.
offline data synchronization software
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.
Data Recovery Stick | USB Data Recovery Device | Windows Data Recovery Software | Recover SD Card, Photos, Files
The Data Recovery Stick requires no technical skills — simply plug it into your Windows computer, click Start,…
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.
Implications of Making Disk the Single Source of Truth
This architecture shifts the complexity from managing centralized databases to ensuring file integrity and consistency. It enables faster, offline-capable tools that are easier to extend and integrate, reducing vendor lock-in and increasing transparency. However, it requires careful handling of concurrent edits, merge conflicts, and directory structure adherence, which can pose challenges for developers and users.
Evolution Toward File-Based Data Management in Project Tools
Traditional project management tools rely on databases or cloud servers for data storage, often creating lock-in and limiting offline functionality. For a broader context on local-first architectures, see this overview. Recent efforts, including Threlmark’s, explore local-first principles, where data is stored directly on disk as files, enabling greater control, portability, and offline operation. This approach aligns with broader trends in decentralized data management and user sovereignty, though it introduces new technical challenges around file safety and synchronization.
“Treating the disk as the contract simplifies data management and enhances offline resilience.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Ongoing Developments
While Threlmark’s approach shows promise, it remains unclear how well it scales with very large data sets or complex collaboration scenarios. The effectiveness of conflict resolution, merge strategies, and self-healing mechanisms in diverse real-world environments is still under evaluation. Additionally, the impact of manual file edits and potential inconsistencies has yet to be fully tested at scale.
Upcoming Enhancements and Adoption Strategies
Threlmark plans to refine conflict resolution methods, improve user-facing tools for manual data management, and expand integration capabilities with external tools. Further testing in collaborative environments will help determine how well the system maintains data integrity under concurrent edits. Broader adoption may depend on community feedback and the development of best practices for directory structure and file management.
Key Questions
How does Threlmark prevent data corruption during file writes?
It uses atomic write operations—writing data to a temporary file and then renaming it over the original—to ensure atomicity and prevent corruption if a write is interrupted.
Can external tools modify Threlmark’s data safely?
Yes, because the data is stored in plain files following a clear directory structure, external tools can read and write files directly, provided they adhere to the agreed-upon format and conventions.
What are the main challenges of a file-based data system?
Managing many small files can introduce filesystem overhead, and ensuring consistency during concurrent edits requires careful conflict resolution and merge strategies.
Is this approach suitable for large, collaborative projects?
This is still under evaluation; while the approach offers benefits in offline and portable scenarios, its scalability and conflict management in large teams are areas of ongoing development.
How does Threlmark handle versioning or history of data changes?
The current focus is on real-time synchronization and data safety; explicit versioning or history features are not yet detailed but could be integrated through file management practices.
Source: ThorstenMeyerAI.com
