📊 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 uses the disk as the primary data source, avoiding traditional databases. This approach improves offline usability, data portability, and system transparency, with a focus on safety and simplicity.
Threlmark’s latest approach treats local disk storage as the ultimate source of truth, removing the need for traditional databases and cloud servers. This approach is detailed in the original analysis. This design simplifies data synchronization, enhances offline usability, and makes data more portable across tools, marking a significant shift in how project management and data systems operate.
Threlmark’s architecture centers on storing each data item as a separate file on the disk, with atomic write operations ensuring data integrity. The directory structure functions as a formal data contract, allowing external tools to read and write files directly without special permissions. The system employs self-healing mechanisms to reconstruct views and maintain consistency, even amid concurrent edits or file corruption.
This approach shifts complexity from managing a centralized database to handling file-level integrity, conflict resolution, and directory organization. Developers must implement strategies like tolerant merging and atomic file operations to prevent data corruption and race conditions. The design offers high resilience and portability but requires careful management of numerous small files and adherence to directory conventions.
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.
Seagate Portable 2TB External Hard Drive HDD — USB 3.0 for PC, Mac, PlayStation, & Xbox -1-Year Rescue Service (STGX2000400)
Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external…
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 1TB Portable SSD – Up to 800MB/s, USB-C, USB 3.2 Gen 2, Updated Firmware – External Solid State Drive – SDSSDE30-1T00-G26
Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance…
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.
Windows NT File System Internals: A Developer's Guide
Used Book in Good Condition
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.
JSON file editor for data projects
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 Disk as the Single Source of Truth
This architecture fundamentally changes data management by removing reliance on databases, enabling greater flexibility, offline access, and data portability. For a deeper dive, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. It reduces vendor lock-in and simplifies system inspection and extension. However, it also introduces new challenges in concurrency control and conflict resolution, requiring careful design of file handling and merge strategies. For users and developers, this means more transparent data workflows and potentially faster, more reliable tools.
Background and Evolution of Threlmark’s Data Model
Traditional project management tools rely on centralized databases or cloud services, which can limit offline access and create vendor lock-in. Threlmark’s design, inspired by local-first principles, shifts the paradigm by treating disk storage as the definitive data contract. This approach aligns with trends toward decentralized, resilient systems and has been gradually adopted in the developer community to improve flexibility and control over data.
Recent developments include the implementation of atomic file operations and directory-based data contracts, allowing external tools to interact seamlessly with the system. More details can be found in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. These innovations aim to create a more transparent, resilient, and user-controlled data environment, contrasting with conventional database-centric architectures.
“Treating the disk as the contract simplifies synchronization and makes data more portable, without sacrificing safety or clarity.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Areas for Further Development
While the approach offers many benefits, questions remain about how effectively it scales with large datasets or complex concurrency scenarios. The system’s conflict resolution strategies and performance under high load are still being tested, and manual intervention may be required in some cases. Additionally, the impact on user workflows and integration with existing tools is still evolving.
Future Steps for Threlmark’s Local-First Architecture
Threlmark plans to refine its conflict resolution mechanisms and optimize performance for larger projects. Further development will focus on enhancing automation for self-healing and integrating with more external tools through standardized file formats. Community feedback and real-world testing will guide these improvements, aiming to make the system more robust and user-friendly.
Key Questions
How does Threlmark prevent data corruption?
Threlmark uses atomic write operations, where data is first written to a temporary file before replacing the original, preventing corruption during crashes or interruptions.
Can external tools modify Threlmark data?
Yes, the directory structure acts as a data contract, allowing external tools to read and write files directly, provided they adhere to the established format.
What are the limitations of a disk-as-the-contract approach?
Managing many small files can introduce filesystem overhead, and conflict resolution during concurrent edits remains a challenge that requires careful handling.
Is this approach suitable for large-scale projects?
While promising, scalability is still under evaluation. The system’s performance with extensive data and complex concurrency scenarios is an area of ongoing development.
Source: ThorstenMeyerAI.com
