📊 Full opportunity report: Disk Is the Contract: Inside Threlmark’s Local-First Architecture on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
Get hardware and tech essentials delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
TL;DR
Threlmark’s new approach makes disk storage the primary contract for data, eliminating traditional databases. This enhances offline capability, simplifies sync, and promotes data portability, offering a resilient alternative for project management tools.
Threlmark has introduced a novel architecture that treats local disk storage as the definitive source of truth for data, moving away from traditional databases and cloud-based systems. This approach is detailed in the original analysis. This approach simplifies data synchronization, enhances offline usability, and ensures data portability across tools, marking a significant shift in how project management and similar tools handle data persistence.
At the core of Threlmark’s design is the principle that each data item resides in its own file, with atomic write operations ensuring data integrity during updates. The directory structure acts as a formal contract, making the data transparent and easily accessible for manual editing or external tool integration. This setup reduces complexity associated with concurrency and race conditions, as each file is an isolated unit, preventing conflicts during simultaneous edits.
To maintain safety, Threlmark employs techniques like atomic file writes—writing to a temporary file before renaming—and tolerant merging, which allows for the safe handling of missing or unknown data fields. These mechanisms ensure consistency even when multiple tools or users modify data concurrently. The directory layout itself is designed to be explicit, with clear organization of project metadata, cards, and dependencies, fostering interoperability and ease of manual inspection.
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.
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.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.
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/<file>.json
→ ingested on readRobust even if the server’s down at finish time.
A small formula, and an honest hosting caveat
Because items are globally addressable (<projectId>/<itemId>), the Portfolio ranks everything together by a status-weighted score — finishing beats starting, blockers get a boost.
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 Changes Data Management
This approach shifts the complexity from managing centralized databases to ensuring file-level integrity and consistency. For a deeper understanding, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. It provides greater data transparency, reduces vendor lock-in, and improves offline capabilities. For users and developers, this means more resilient tools that can operate without constant network access, and easier integration with external systems through straightforward file manipulation. However, it also introduces new challenges, such as handling many small files efficiently and resolving conflicts in concurrent environments.
As an affiliate, we earn on qualifying purchases.
Background and Evolution of Local-First Data Architectures
Traditional data management relies heavily on centralized databases and cloud services, which can create dependencies, lock-in, and issues with offline access. This evolution is part of the broader local-first data architectures movement. The local-first movement emerged to address these concerns, promoting systems that prioritize local storage and synchronization. Threlmark’s architecture builds on these principles, emphasizing the disk as the ultimate authority for data, with a focus on simplicity, transparency, and resilience. This design aligns with recent trends toward more open, portable, and offline-capable tools, reflecting a broader industry shift.
“Treating the disk as the contract simplifies synchronization and makes data more portable and resilient.”
— Thorsten Meyer, Threlmark developer
As an affiliate, we earn on qualifying purchases.
Unresolved Challenges and Implementation Details
It is not yet clear how Threlmark manages large-scale projects with thousands of files or how conflict resolution is handled in complex concurrent editing scenarios. Details about performance optimization, handling file system limitations, and integration with existing tools remain under development or are not publicly detailed.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Tool Integration
Threlmark plans to continue refining its file-based architecture, improving conflict resolution, and expanding integration options with external tools. Wider adoption will depend on how well the system scales and how easily existing workflows can transition to this model. Future updates may include enhanced conflict management and performance tuning for larger projects.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Threlmark ensure data safety with file-based storage?
Threlmark uses atomic write operations—writing to a temporary file then renaming it—and tolerant merging to prevent corruption and handle concurrent edits safely.
Can external tools modify Threlmark data?
Yes, the explicit directory structure and file format allow external tools to read and write data directly, provided they adhere to the established contract.
What are the main benefits of this architecture?
It offers improved offline capability, data portability, transparency, and resilience against network failures or cloud outages.
What challenges might this approach face?
Managing many small files efficiently, resolving conflicts during concurrent edits, and scaling to large projects are potential challenges.
Source: ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
