📊 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 disk storage as the definitive data source, replacing traditional databases. This approach enhances offline capabilities, simplifies synchronization, and promotes data portability, all while maintaining system transparency.
Threlmark has adopted a novel architecture where the disk itself is treated as the definitive source of truth for all data, eliminating the need for traditional databases or cloud servers. This design is explained in the original analysis. This design simplifies synchronization, enhances offline usability, and makes data more portable and transparent, according to the company.
Threlmark’s approach centers on storing each data item in individual files, with atomic write operations ensuring data integrity during updates. The directory structure acts as a formal contract, providing clarity and interoperability for external tools and manual editing. The system employs self-healing mechanisms to keep project views consistent, reconstructing state from individual files when needed.
By avoiding centralized databases, Threlmark aims to create more resilient, flexible, and user-controlled systems. The architecture reduces vendor lock-in and simplifies data management, especially in offline or multi-tool environments. However, this approach shifts complexity toward managing file-level concurrency, conflict resolution, and directory structure design.
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 1TB 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-1T00-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.![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
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.
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 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.
iodd MINI Pro External encrypted SSD (1TB) – USB-C 3.1 Gen 1 | Bootable Virtual ODD/HDD (ISO, VHD, VMDK) | AES256-XTS Hardware Encryption (76 Digits) | Hardware Write-Blocker | Made in Korea
Advanced Hardware Encryption: AES256-XTS encryption with 38-digit PIN plus device-bound secondary password for maximum data security
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 Disk as the Single Source of Truth Matters
This architecture fundamentally changes how data persistence and collaboration are handled in project management tools. For a detailed overview, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. By making the disk the ultimate contract, Threlmark enables faster, more reliable offline access and simplifies data portability across different tools and platforms. It reduces dependency on proprietary databases and cloud services, giving users more control over their data.
While this approach enhances transparency and resilience, it also introduces challenges related to managing concurrent edits and ensuring consistency across many small files. Still, the overall impact could lead to more robust, adaptable systems suited for a variety of workflows and environments.
Background and Evolution of Local-First Data Management
Traditional project management tools rely heavily on centralized databases or cloud-based servers, which can create lock-in, slow offline access, and complicate data portability. This shift toward local-first systems is part of broader trends in open data and offline-first architectures. Recent movements toward local-first architectures aim to address these issues by prioritizing local storage and direct file manipulation.
Threlmark’s approach builds on these principles by treating each data item as a separate file, with directory structures serving as explicit contracts. This design aligns with broader trends in open data, offline-first systems, and user-controlled data management, positioning Threlmark as a notable example of this shift.
“Treating the disk as the ultimate contract allows for a more transparent, resilient, and flexible system that empowers users to control their data directly.”
— Thorsten Meyer, Threlmark developer
Unresolved Aspects of Threlmark’s Architecture
It is not yet clear how Threlmark handles complex merge conflicts during concurrent edits or how the system scales with very large projects containing thousands of files. Details about conflict resolution strategies and performance benchmarks are still emerging.
Additionally, the long-term implications for integration with other tools and the ease of manual data recovery remain to be fully evaluated.
Next Steps for Threlmark’s Local-First System
Threlmark plans to release detailed documentation and open-source its core components, enabling community testing and feedback. Future updates may include enhanced conflict resolution mechanisms, performance improvements, and broader integration options. Monitoring how users adopt and adapt to this architecture will be crucial in assessing its viability at scale.
Key Questions
How does Threlmark ensure data integrity during file updates?
Threlmark employs atomic write operations, where updates are first written to a temporary file and then renamed over the original, preventing corruption from crashes or interruptions.
Can external tools modify Threlmark data safely?
Yes, the explicit directory structure acts as a contract, allowing external tools to read and write files directly, provided they follow the established format and conventions.
What are the main challenges of using a file-based approach?
Managing many small files can introduce filesystem overhead and complexity in maintaining consistency and relationships between data items, especially during concurrent edits.
Will this architecture work for very large projects?
While promising, scalability for large projects with thousands of files remains to be tested. Performance and conflict resolution strategies will be critical factors moving forward.
Source: ThorstenMeyerAI.com
