📊 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 innovative approach uses the local disk as the single source of truth, avoiding databases. This design improves offline capabilities, simplifies data sync, and enhances portability, making systems more resilient and transparent.
Threlmark has adopted a local-first architecture that treats the local disk as the definitive source of truth for data, eschewing traditional databases and server reliance. This approach enhances offline usability, simplifies synchronization, and improves data portability, making systems more resilient and transparent.
The core idea behind Threlmark’s architecture is that each piece of data is stored directly on disk as a plain file, with the system designed to treat these files as the authoritative source. This eliminates the need for centralized databases or cloud servers, allowing users to work offline seamlessly and ensuring data remains accessible and portable across tools.
Threlmark employs techniques such as atomic file writes—writing to temporary files before renaming—to prevent corruption during updates. It also uses a ‘one file per item’ model, which reduces conflicts during concurrent edits and simplifies recovery when files are corrupted or missing. The directory structure acts as a formal contract, providing transparency and enabling external tools to read and write data without proprietary formats. For more on this approach, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
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.
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.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.
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.
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 Data Source
This design fundamentally shifts how data persistence and collaboration are handled. The original analysis details how treating the disk as the contract simplifies synchronization and makes the system more resilient to failures. By making the disk the primary contract, Threlmark enables faster, more reliable, and more flexible tools that work offline and avoid vendor lock-in. It also simplifies data recovery and enhances interoperability, but introduces new challenges in managing file integrity, merge conflicts, and filesystem overhead.
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
- High-Speed NVMe Performance: Up to 1050MB/s read, 1000MB/s write
- Durable and Water Resistant: IP65 water and dust resistance, 3-meter drop protection
- Portable and Secure: Includes carabiner loop for easy attachment
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background on Local-First and Data Management Trends
Traditional data management relies heavily on centralized databases and cloud storage, which can introduce latency, lock-in, and dependency on network connectivity. The local-first paradigm, championed by projects like Threlmark, emphasizes storing data directly on local devices, enabling offline work, faster access, and greater control. This approach has gained traction as a way to improve resilience and user autonomy, especially in environments with unreliable internet or strict privacy requirements.
“Treating the disk as the contract simplifies synchronization and makes the system more resilient to failures.”
— Thorsten Meyer, Threlmark developer
NEWQ 2TB External Hard Drive for iPhone, USB-C & Lightning Compatible Photo Storage Device, One-Click Backup Photos/Videos to Free Up Phone Space, Offline Transmission Support, No Computer Required
- Wide Compatibility: Supports iPhone, Android, Windows, Mac
- Dual Interface Support: Works with USB-C and Lightning devices
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Remaining Challenges and Unanswered Questions
While the architecture promises resilience and simplicity, it remains unclear how Threlmark handles complex merge conflicts in multi-user scenarios or large datasets. The scalability of managing many small files and ensuring consistency across external tools also needs further clarification as the system evolves.
Blink USB Flash Drive for local video storage with Blink Sync Module 2
- Compatibility with Sync Module 2: Enables local storage for Blink devices
- Storage Capacity: 64 GB for video clips
- Includes USB Drive: One USB flash drive included
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Future Developments and Adoption Pathways
Threlmark plans to refine conflict resolution mechanisms and improve tooling support for managing directory structures. There is also potential for broader adoption as the approach demonstrates its benefits in real-world applications, with further case studies and community feedback shaping future enhancements.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Threlmark prevent data corruption during updates?
Threlmark uses atomic file writes, where data is first written to a temporary file and then renamed to replace the original, preventing corruption if the process is interrupted.
Can external tools modify Threlmark data safely?
Yes, the directory structure acts as a formal contract, allowing external tools to read and write data directly, provided they follow the agreed formats and protocols.
What are the main tradeoffs of using disk as the source of truth?
While it improves transparency and offline capability, managing many small files and conflict resolution in concurrent editing scenarios can be complex and requires careful design.
How does Threlmark handle merge conflicts?
The system employs tolerant merging techniques that preserve essential data fields and allow for smooth upgrades, though detailed conflict resolution strategies are still under development.
Is this approach suitable for large-scale or enterprise systems?
Currently, the approach is optimized for personal and small-team workflows; scalability and performance in large enterprise environments remain areas for further testing and development.
Source: ThorstenMeyerAI.com
