📊 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 designates the local disk as the primary data source, avoiding traditional databases. This approach improves offline capabilities, simplifies synchronization, and enhances data portability, making systems more resilient and transparent.
Threlmark’s new architecture designates the local disk as the definitive source of data, eliminating reliance on traditional databases. This approach aims to simplify synchronization, improve offline usability, and make data more portable, which could reshape how project management tools are built and used.
Threlmark’s system treats each data item as a separate file stored directly on the user’s disk, with the file system serving as the single source of truth. Instead of a centralized database, this design uses one file per item, such as cards or project metadata, with atomic write operations to prevent corruption. The directory structure acts as a formal contract, allowing external tools to read and modify data without proprietary APIs.
To ensure data safety, Threlmark employs techniques like atomic file writes—writing to a temporary file before renaming to prevent corruption during crashes—and tolerant merging that handles missing or inconsistent data gracefully. This setup supports offline work, as all data resides locally, and synchronization is achieved through self-healing mechanisms that reconstruct state from individual files if needed.
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 2TB 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-2T00-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.
Password Keeper Stick with Type-C Port, Password Storage Device, Offline Password Manager, Portable Password Organizer for Accounts, Banking & Login Information
Offline Local Storage for Privacy:This Password Keeper stores all your login credentials directly on the device, with no…
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.
Project Planner: Management Notebooks Organizer & Work Log Book Tracker With Checklist Brainstorming for Entrepreneurs, Managers & Small Business Owners
TURN YOUR IDEAS INTO REALITY: Unleash your creativity with this unique planning notebook, consisting of 224 pages divided…
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 storage system
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.
Impacts of Disk as the Single Data Source
This approach shifts the complexity from managing a centralized database to ensuring file integrity and consistency, resulting in systems that are more transparent, resilient, and portable. For more details, see this article. It reduces vendor lock-in and enhances offline capabilities, which is critical for remote or unreliable network environments. However, it also introduces new challenges around handling concurrent edits and managing many small files, requiring careful design and conflict resolution strategies.
Evolution of Local-First Data Architectures
Threlmark’s design builds on the broader trend of local-first architectures, which prioritize local data storage with eventual synchronization. Learn more about local-first architectures. Traditionally, project tools relied on cloud-hosted databases, but recent developments emphasize local files to improve speed and reliability. This shift is driven by the need for offline access, data portability, and transparency, especially as users demand more control over their data.
Previous efforts in local-first systems have faced challenges around data conflict resolution and safety, but Threlmark’s implementation of atomic writes and directory-based contracts aims to address these issues explicitly, offering a practical example of how to manage data integrity without a centralized server.
“Treating the disk as the contract fundamentally simplifies data management and enhances offline resilience.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges in File-Based Data Management
While Threlmark’s architecture offers many advantages, it remains unclear how well it handles complex merge conflicts in multi-user scenarios or large-scale data. The effectiveness of self-healing mechanisms and conflict resolution strategies in real-world, high-collision environments is still being tested. Additionally, managing a large number of small files could introduce filesystem overhead and performance issues, especially on slower devices.
Next Steps for Threlmark’s Local-First System
Threlmark plans to further refine its conflict resolution algorithms and optimize filesystem interactions to handle larger datasets efficiently. They will also explore integrations with external tools that respect the directory contract, aiming to demonstrate broader interoperability. User feedback and real-world testing will guide future improvements, with potential for expanding the architecture to more complex use cases.
Key Questions
How does Threlmark ensure data consistency with multiple tools editing files?
Threlmark uses atomic writes and tolerant merging to prevent corruption and handle concurrent edits, but complex conflict resolution may require manual intervention in some cases.
Can this architecture scale for large projects or teams?
While suitable for many use cases, performance and filesystem overhead could become concerns with very large datasets. Ongoing optimizations are expected to address these issues.
How does this approach compare to traditional cloud-based project tools?
It offers greater offline capabilities, data transparency, and portability, but may require more careful conflict management and manual synchronization in multi-user environments.
Is this system compatible with existing tools and workflows?
Yes, because it relies on standard files and directory structures, external tools can read and write data directly, provided they follow the established contract.
Source: ThorstenMeyerAI.com
