📊 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 local-first architecture makes disk the ultimate source of truth, eliminating traditional databases. This approach improves offline usability, data portability, and system transparency, with specific safety mechanisms in place.
Threlmark’s new architecture designates local disk storage as the definitive source of truth for its data, moving away from traditional database reliance. This approach is detailed in the original analysis. This shift enhances offline usability, simplifies synchronization, and increases data portability, making the system resilient and transparent.
Threlmark’s approach centers on treating each piece of data as a file stored directly on the disk, with one file per item. The system employs atomic write operations to prevent corruption during updates and uses tolerant merging to handle concurrent edits. Its directory structure acts as a formal contract, making data organization explicit and accessible for external tools. This design simplifies data synchronization, enhances system resilience, and promotes interoperability, all while avoiding vendor lock-in associated with conventional databases. The system also includes self-healing mechanisms that rebuild views from individual files, maintaining consistency even in the face of corruption or external interference.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.
SANDISK 512GB Ultra USB 3.0 Flash Drive – SDCZ48-512G-G46, Black
Transfer speeds up to 10x faster than standard USB 2.0 drives (4MB/s); up to 130MB/s read speed; USB…
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.
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.
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.
File Organization and Processing
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 for Data Management and Tool Integration
This approach fundamentally changes how data persistence and collaboration are managed, emphasizing transparency, resilience, and portability. It aligns with principles discussed in the internal site article. By making disk the contract, Threlmark reduces dependency on centralized servers and proprietary databases, enabling faster offline workflows and easier integration with external tools. However, it shifts complexity toward ensuring file safety and conflict resolution, requiring careful handling of concurrent edits and directory structure design. This model could influence future tool architectures by prioritizing local control and explicit data contracts, potentially redefining best practices in offline-first and distributed systems.
Background on Local-First Data Architectures
Traditional data management systems rely heavily on centralized databases and cloud services, which can introduce lock-in, latency, and offline limitations. For more context, see the original analysis. The local-first paradigm, championed by companies like Beaker Browser and others, prioritizes local storage as the primary data source, enabling offline access, faster sync, and greater user control. Threlmark’s implementation builds on these principles, emphasizing a file-based approach where the disk becomes the single source of truth. This approach aligns with recent trends toward decentralization and user sovereignty over data, but it also introduces new challenges in concurrency, conflict resolution, and data integrity management.
“Treating the disk as the contract simplifies synchronization and makes the system more resilient to disconnections.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Areas for Further Development
It is not yet clear how Threlmark’s system handles complex merge conflicts in multi-user environments or how scalable the directory-based contract approach is with very large datasets. The specifics of conflict resolution strategies and performance under heavy load remain to be fully tested and documented. Additionally, the long-term robustness of self-healing mechanisms in diverse real-world scenarios is still being evaluated.
Upcoming Developments and Next Steps for Threlmark
Threlmark plans to release detailed documentation on conflict resolution and merge strategies, as well as tools to assist manual recovery when needed. Further testing in multi-user environments is expected to refine the system’s resilience. The team also aims to develop standardized directory schemas to facilitate broader interoperability and integration with external tools, making the architecture more accessible for developers and users alike.
Key Questions
How does Threlmark prevent data corruption during updates?
It uses atomic write operations, where data is first written to a temporary file and then renamed over the original, preventing corruption if a write is interrupted.
Can Threlmark handle simultaneous edits by multiple users?
The system employs tolerant merging and conflict resolution strategies, but the specifics of multi-user collaboration are still under development.
What are the main benefits of making disk the contract?
It simplifies offline access, enhances data portability, reduces dependency on proprietary systems, and makes data more transparent and easier to inspect manually or with external tools.
Are there any performance concerns with many small files?
Managing numerous small files can introduce filesystem overhead, but careful directory structure design and update strategies can mitigate performance issues.
What is the future roadmap for Threlmark’s architecture?
Future plans include refining conflict resolution, expanding documentation, and developing standardized schemas to improve interoperability and scalability.
Source: ThorstenMeyerAI.com
