📊 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 ultimate data contract, replacing databases with file-based storage. This approach enhances offline capability, data portability, and system transparency, with specific safety mechanisms in place.
Threlmark’s latest approach treats the local disk as the definitive source of truth for data, fundamentally shifting away from traditional database reliance. This design is discussed in the original analysis. This design enhances offline usability, simplifies data synchronization, and promotes data portability, making the system more resilient and transparent.
Threlmark’s architecture centers on storing each data item as a separate file within a structured directory hierarchy, with atomic file operations ensuring data integrity. This approach avoids common issues like race conditions and data corruption, even during concurrent edits or system failures.
Key safety mechanisms include atomic writes—writing to a temporary file before renaming it to prevent corruption—and tolerant merging, which allows the system to handle missing or inconsistent data gracefully. These techniques ensure that data remains consistent and recoverable.
The directory structure itself acts as a formal data contract, providing transparency and facilitating interoperability with external tools. Files contain metadata, project states, and individual items, which can be manually inspected or edited without specialized software.
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.
AmberPRO Personal Cloud Storage Device + AC2600 WiFi Router. Dual 2TB Hard Drives with RAID 1 or Optional 4TB with RAID 0. Plex and Home Assistant. iOS/Android/Windows/Mac Compatible. AM1211-2TB
Store your data locally and access it from anywhere with this smart personal cloud device.
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.
BALEINE File Organizer Box with Lid, Collapsible File Folder Organizer with Plastic Slide, Hanging File Folder Box for Office Document Storage (1 Pack, Black, S)
[UNIVERSAL SIZE] Our file box with lid fits letter-sized files. It is designed for efficiency and functionality, with…
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.
atomic file write hardware
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.
GODIAG GT111 for VW Audi Skoda Seat CAN-Bus 3rd & 3.5th Generation Dashboard IM-MO Key Matching Test Platform Cable with POGO PIN to Read & Write Data
Supports VW Audi Skoda Seat: Performs offline key and IM-MO instrument synchronization test, intelligent IM-MO system emergency 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.
Why Making Disk the Single Source of Truth Matters
This approach fundamentally changes how data persistence and collaboration work in project management tools. For more details, see this overview of local-first architectures. By removing dependency on centralized databases or cloud servers, systems become more resilient to network disruptions and easier to extend or modify. Data portability is improved, as users can directly manipulate files with standard tools, reducing vendor lock-in.
However, this shift also introduces challenges, such as managing concurrent edits and ensuring consistency across multiple files. Threlmark’s safety techniques aim to mitigate these issues, providing a more transparent and flexible architecture that can adapt to various workflows and environments.
Background and Evolution of Local-First Data Architectures
Traditional project management tools rely heavily on centralized databases or cloud services, which can create bottlenecks, lock-in, and offline limitations. The concept of local-first architecture emerged as a response, emphasizing local storage with eventual synchronization. Threlmark’s implementation builds on this trend by making the local disk the ultimate contract, with a focus on simplicity, transparency, and resilience.
The idea of treating files as the primary data format is gaining traction in the developer and open-source communities, with other projects exploring similar principles. You can read more in the original analysis. Threlmark’s approach exemplifies how a disciplined directory structure and safety mechanisms can create a robust local-first system.
“Treating the disk as the contract simplifies synchronization and enhances offline usability, making data more portable and systems more resilient.”
— Thorsten Meyer, Threlmark Developer
Unresolved Challenges and Open Questions
While Threlmark’s approach offers many advantages, questions remain about how it handles high-volume data, large-scale concurrency, and manual file edits that could introduce inconsistencies. The effectiveness of conflict resolution in complex scenarios is still being tested, and real-world adoption may reveal unforeseen issues.
Additionally, the performance implications of managing many small files versus a centralized database are not fully documented, and integration with existing tools requires adherence to strict directory and file conventions.
Next Steps for Adoption and Development
Threlmark plans to further refine its safety mechanisms, improve user tools for manual file management, and develop integrations with popular project management platforms. Community feedback and real-world use cases will shape ongoing improvements.
Expect upcoming releases to include enhanced conflict resolution, better performance handling for large data sets, and expanded documentation to facilitate broader adoption.
Key Questions
How does Threlmark ensure data consistency across files?
Threlmark uses atomic writes—writing to a temporary file before renaming it—and tolerant merging to prevent corruption and handle concurrent edits safely.
Can I manually edit the files to modify my project data?
Yes, the directory structure is transparent, and files can be manually inspected or edited, provided users understand the data format and conventions.
What are the main benefits of this architecture?
Improved offline capability, data portability, transparency, and resilience against network or server failures.
Are there any limitations or risks?
Managing many small files can introduce filesystem overhead, and manual edits or misaligned tools could cause inconsistencies if not carefully managed.
Will this approach work for large-scale or enterprise systems?
This approach is best suited for small to medium projects; scaling to large enterprise systems may require additional infrastructure and conflict management strategies.
Source: ThorstenMeyerAI.com
