📊 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 approach centers on using local disk storage as the primary data source, avoiding databases. This design simplifies sync, enhances offline use, and improves data portability. The system relies on file-based data management and explicit directory structures.
Threlmark’s new architecture design treats disk storage as the definitive source of truth for data, moving away from traditional databases and cloud dependencies. This approach is detailed in the original analysis. This approach enhances offline usability, simplifies synchronization, and makes data more portable, impacting how project management tools can operate with greater resilience and transparency.
Threlmark’s system employs a model where each data item, such as project cards, is stored as a separate file, with atomic write operations to prevent corruption. The directory structure functions as a formal contract, making data organization explicit and accessible for external tools. This design facilitates offline work, easy data inspection, and interoperability across different tools and environments.
Key safety mechanisms include atomic file writes—writing to a temporary file before renaming—and tolerant merging that preserves essential metadata like IDs and timestamps. These techniques ensure data integrity during concurrent edits and external modifications, reducing the risk of corruption or conflicts. The system’s reliance on small, individual files simplifies recovery and synchronization, as the state can be reconstructed from the existing files even if some are missing or corrupted.
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.
Samsung T7 Portable SSD, 1TB External Solid State Drive, Speeds Up to 1,050MB/s, USB 3.2 Gen 2, Reliable Storage for Gaming, Students, Professionals, MU-PC1T0T/AM, Gray
MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to…
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.
Project Planner Notepad – Project Management Organizer Desk Pad – Manage Project Tasks and Meeting Deadlines Effectively – 50 Sheets of Premium 120gsm Paper | Management | A4 Mono
Comprehensive Project Planning: Plan for success with a dedicated project timeline and task sections to track milestones and…
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.
Western Digital 10TB WD Gold Enterprise Class Internal Hard Drive – 7200 RPM Class, SATA 6 Gb/s, 256 MB Cache, 3.5" – WD102KRYZ
Available in 1TB to 20TB capacities. | 1As used for storage capacity, 1GB = 1 billion bytes and…
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.
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 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 Treating Disk as the Single Source of Truth Matters
This approach fundamentally shifts how data persistence and collaboration are handled in project management tools. For a deeper dive, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. By avoiding centralized databases, Threlmark offers a system that is more resilient to network failures, easier to inspect and modify manually, and free from vendor lock-in. It enables faster, more reliable offline workflows and greater flexibility in integrating with other tools, which can benefit users who require robust, portable, and transparent data management.
However, this design also shifts complexity to managing file integrity, concurrency, and directory structures. Developers need to implement careful conflict resolution and maintain explicit data contracts to prevent inconsistencies, which may require additional effort but ultimately results in a more open and adaptable system.
The Evolution of Local-First Data Architectures in Project Tools
Threlmark’s approach builds on the broader trend of local-first architectures, which prioritize local storage and offline capabilities over cloud reliance. Learn more about local-first data architectures at this site. Traditionally, project management tools have depended on centralized databases or cloud servers, creating dependencies that can hinder offline work and introduce lock-in. Threlmark’s design departs from this by treating disk storage as the primary contract, aligning with recent developments in resilient, offline-capable applications.
Prior to this, many tools struggled with data conflicts, synchronization issues, and vendor lock-in, especially in collaborative environments. Threlmark’s explicit directory structure and file-based data model aim to address these limitations, offering a transparent, flexible alternative rooted in simple file operations and clear data contracts.
“Treating disk as the contract simplifies data management, making systems more resilient and portable.”
— Thorsten Meyer, Threlmark developer
Unresolved Questions About Threlmark’s Architecture Scalability
It is not yet clear how well Threlmark’s file-based system scales with very large datasets or high concurrency scenarios. While the design emphasizes safety and simplicity, the impact on performance and responsiveness in extensive projects remains to be tested in real-world use cases. Additionally, the handling of complex merge conflicts and manual interventions is still being refined, and the long-term robustness of the directory contracts under various workflows is uncertain.
Next Steps for Adoption and Development of Threlmark’s System
Threlmark plans to release further documentation and tooling to support external integrations, as well as to refine conflict resolution strategies for large-scale projects. User feedback and real-world testing will likely shape future improvements, especially around performance optimization and conflict management. Monitoring how the system handles diverse workflows will be key to assessing its broader applicability and robustness.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark employs atomic file writes—writing to a temporary file before renaming it over the original—to prevent corruption. It also uses tolerant merging techniques that preserve essential metadata, ensuring data integrity during concurrent edits and failures.
Can Threlmark handle large projects with many items?
This remains to be fully tested. While the small-file approach simplifies concurrency and recovery, performance in very large datasets or highly concurrent environments is still being evaluated.
How does the directory structure act as a data contract?
The directory layout explicitly defines where data files are stored and how they relate, making data organization transparent and accessible for manual editing and external tools, provided they follow the same structure.
What are the main benefits of this approach?
Benefits include offline capabilities, improved data portability, transparency, and resilience against network failures or cloud outages, with simplified data inspection and manual editing.
What challenges might arise from this architecture?
Challenges include managing concurrency at scale, handling conflicts during simultaneous edits, filesystem overhead from many small files, and ensuring all tools adhere to the explicit directory contract to prevent inconsistencies.
Source: ThorstenMeyerAI.com
