📊 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 treats local disk storage as the primary source of truth, avoiding traditional databases. This design simplifies synchronization, improves offline capabilities, and makes data portable and transparent. The approach shifts complexity to ensuring file integrity and conflict resolution.
Threlmark has adopted a local-first architecture that treats disk storage as the definitive source of truth, bypassing traditional databases and cloud dependencies. This approach is detailed in the original analysis. This approach enhances offline usability, simplifies data synchronization, and improves portability, making the system more resilient and transparent.
Threlmark’s system stores each data item as an individual file on disk, using atomic write operations to prevent corruption during updates. The directory structure acts as a formal contract, defining how data is organized and accessed, which supports interoperability with external tools. The system employs self-healing mechanisms to reconstruct state from files, ensuring consistency even after failures or conflicts.
To ensure data safety, Threlmark uses two key techniques: atomic file writes, which write to temporary files before replacing originals, and tolerant merging, which allows safe updates despite missing or conflicting data. These methods mitigate risks associated with concurrent edits and external interference, providing a resilient environment for multi-tool workflows.
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.
ValueMax 7PCS Interchangeable Needle File Set, Small File Set Includes Flat, Flat Warding, Round, Half-Round, Square, Triangular File and A Handle, Suitable for Shaping Metal, Wood, Jewelry, Plastic
Versatile File Set: This ValueMax needle file set includes flat file, flat warding file, round file, half-round file,…
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.
offline data synchronization software
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.
atomic file write utilities
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 Disk as the Single Source of Truth
This approach fundamentally changes data management by removing reliance on centralized databases, reducing vendor lock-in, and increasing transparency. It enables faster, offline-capable tools that are easier to inspect and extend. However, it also shifts complexity to handling file integrity, concurrency, and conflict resolution, requiring careful design and robust safety mechanisms.
Background and Development of Threlmark’s Architecture
Traditional project management tools rely heavily on centralized databases and cloud servers, which can introduce latency, lock-in, and dependency issues. For more context, see the original analysis. Threlmark’s architecture emerged as a response to these limitations, emphasizing local storage and file-based data management. This design aligns with the broader trend of local-first principles, prioritizing user control, offline access, and data portability.
Since its inception, Threlmark has focused on creating a transparent, flexible system where data can be manually inspected, edited, and integrated with external tools through straightforward file operations. The architecture is still evolving, with ongoing improvements in conflict handling and self-healing features.
“Treating disk as the contract simplifies synchronization and enhances offline resilience.”
— Thorsten Meyer, Threlmark developer
Remaining Challenges and Unknowns in the Architecture
While Threlmark’s approach offers many benefits, it remains unclear how well it scales with very large datasets or complex concurrency scenarios. The effectiveness of conflict resolution and self-healing mechanisms under high contention or manual user intervention is still being tested. Additionally, the impact on filesystem performance and management of numerous small files requires further evaluation.
Upcoming Developments and Future Directions
Threlmark plans to refine its conflict resolution strategies and optimize file management for larger projects. Further integration with external tools and automation workflows is expected, along with user interface improvements to aid manual conflict resolution. The team will also explore formal standards for directory structures to enhance interoperability and extensibility.
Key Questions
How does Threlmark ensure data safety 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 during crashes or interruptions.
Can this architecture handle large projects with many files?
While designed for scalability, the performance implications of managing many small files are still being evaluated, especially in very large datasets or high concurrency scenarios.
How does Threlmark manage conflicts when multiple tools edit files simultaneously?
The system employs tolerant merging techniques that preserve data integrity and allow safe concurrent edits, but complex conflicts may require manual resolution.
Is manual editing of files safe in Threlmark’s system?
Yes, as long as users follow the directory structure and avoid corrupting files, manual edits can be safely performed, thanks to the system’s safety mechanisms.
What are the main benefits of treating disk as the contract?
It simplifies synchronization, enhances offline capabilities, improves data portability, and makes the system more transparent and easy to extend.
Source: ThorstenMeyerAI.com
