📊 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 makes the disk the primary data source, avoiding traditional databases. This approach improves offline capability, data portability, and system transparency, with some challenges in concurrency management.
Threlmark’s new architecture design treats the local disk as the sole source of truth for project data, avoiding traditional databases and cloud dependencies. This approach is detailed in the original analysis. This approach aims to simplify synchronization, improve offline usability, and enhance data portability, making the system more resilient and transparent.
Threlmark’s system operates with a file-per-item model, where each project component—such as cards or metadata—is stored in individual files. It employs atomic write operations to prevent data corruption during updates, and uses directory structures as explicit data contracts to facilitate interoperability. This design allows users to edit files directly with any text editor, enabling offline work and easy data migration.
Key safety mechanisms include atomic file writes, which involve writing to temporary files before renaming to prevent corruption, and tolerant merging strategies that handle missing or unknown data fields. The directory layout serves as a formal contract, making the data structure transparent and accessible for external tools, fostering extensibility and manual intervention when needed.
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.![WavePad Audio Editing Software - Professional Audio and Music Editor for Anyone [Download]](https://m.media-amazon.com/images/I/B1fcLEGCs6S._SL500_.png)
WavePad Audio Editing Software – Professional Audio and Music Editor for Anyone [Download]
Full-featured professional audio and music editor that lets you record and edit music, voice and other audio recordings
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.
Json Genie Premium: JSON Editor, Viewer & Formatter
Open, view, and edit JSON and JSONC files with a fast tree-based interface
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.
WORKPRO W051003 8 In. Half Round File, Durable Steel File for Concave, Convex & Flat Surfaces, Comfortable Anti-Slip Grip, Double Cut & Single Cut, Tool Sharpener for Pro's and DIY (Single Pack)
HALF ROUND FILE – Easily shape curves or make straight edges on wood, metal, and plastic with this…
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.
Impacts of Local-First Design on Data Management
This architecture shifts the paradigm of data management from centralized databases to decentralized, file-based storage, resulting in systems that are more resilient to network failures and easier to extend or modify. For a deeper dive, see this internal link. For users, it means greater control over their data, faster offline access, and reduced vendor lock-in. For developers, it introduces new challenges in handling concurrency, conflict resolution, and filesystem overhead, but ultimately offers a more transparent and flexible system that can better adapt to diverse workflows.
Evolution of Data Storage in Project Tools
Traditional project management tools rely heavily on centralized databases or cloud services, which can introduce latency, dependency on network connectivity, and vendor lock-in. Learn more about local-first architectures at this site. Recent movements toward local-first architectures aim to address these issues by shifting data storage to the user’s device, with systems like Threlmark pioneering this approach. The core idea has gained traction as users seek more control, privacy, and offline capabilities, prompting developers to explore file-based data models that treat the disk as the definitive contract.
“Treating the disk as the ultimate source of truth simplifies synchronization and makes data more portable and resilient.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges in File-Based Synchronization
It is still unclear how Threlmark will handle complex conflict resolution in multi-user scenarios, especially when external tools modify files concurrently. The scalability of managing numerous small files and the potential filesystem overhead are also areas needing further evaluation. Details about how the system ensures consistency across devices in real-time remain to be fully disclosed.
Upcoming Developments in Threlmark’s Data Protocols
Threlmark is expected to release more detailed documentation on conflict resolution strategies and synchronization protocols. Future updates may include enhanced tools for managing large projects with many files and improved mechanisms for integrating external tools without risking data integrity. Monitoring these developments will clarify how the architecture scales and adapts to complex workflows.
Key Questions
How does Threlmark prevent data corruption during updates?
Threlmark uses atomic write operations, where data is first written to a temporary file and then renamed to replace the original, preventing corruption if a crash occurs during the write process.
Can external tools safely modify Threlmark’s files?
Yes, the directory structure is designed as a clear data contract, allowing external tools to read and write files directly. However, careful adherence to the structure is necessary to prevent inconsistencies.
What are the main tradeoffs of this approach?
While it enhances portability and offline capabilities, managing many small files can introduce filesystem overhead and complexity in conflict resolution, especially in multi-user environments.
How does Threlmark handle conflicts when multiple tools edit the same data?
The system employs tolerant merging strategies that can handle missing or unknown data fields, but detailed conflict resolution mechanisms are still under development.
Source: ThorstenMeyerAI.com
