📊 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 ultimate source of truth, avoiding traditional databases. This approach simplifies synchronization, boosts offline capabilities, and enhances data portability and transparency.
Threlmark has adopted a novel local-first architecture that treats disk storage as the definitive source of truth, bypassing traditional databases and cloud reliance. This approach is detailed in the original analysis. This design simplifies data synchronization, improves offline usability, and makes data more portable and transparent. The approach is already influencing how the system handles data consistency, concurrency, and integrations, marking a significant shift in data management philosophy for project tools.
Threlmark’s system operates directly on plain files stored on the user’s disk, with each item represented as a separate file. This eliminates the need for a centralized database, making data more accessible and portable. The architecture employs techniques such as atomic writes—writing to temporary files before replacing originals—to prevent corruption during crashes or interruptions. It also uses tolerant merging, allowing safe updates even when data is incomplete or conflicting.
The directory structure itself acts as an explicit contract, providing transparency and facilitating external tool integrations. This concept is also discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. By organizing data into well-defined folders and files, Threlmark ensures that data remains readable, modifiable, and easy to synchronize across different environments. This approach reduces complexity and vendor lock-in while enabling offline work and rapid recovery from errors.
Developers highlight that this model shifts some complexity from managing a centralized database to ensuring file-level integrity and conflict resolution. Managing many small files introduces filesystem overhead but offers benefits in resilience and flexibility. The system’s self-healing capabilities allow it to reconstruct state from individual files, even if some are corrupted or missing.
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.
Seagate Expansion 8TB External Hard Drive HDD – USB 3.0, with Rescue Data Recovery Services (STKP8000400)
Easy-to-use desktop hard drive—simply plug in the power adapter and USB cable
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.
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.
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.
TSUBOSAN Japan-Hardness Tester Checker File HRC40-HRC65 Set of 6
Item Category: Hardware Handle
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 approach fundamentally changes data persistence by removing dependency on proprietary databases and cloud servers, leading to systems that are more resilient, portable, and transparent. It allows users to edit data directly with simple tools like text editors, facilitating easier debugging, manual adjustments, and integrations. For developers, it simplifies deployment and reduces vendor lock-in, while for users, it enhances offline capabilities and data safety.
However, it also introduces challenges such as managing concurrent edits across multiple tools and ensuring consistent directory structures. The safety techniques like atomic writes and tolerant merging are critical to maintaining data integrity. Overall, this architecture promotes a more open, flexible, and user-controlled data environment, which could influence future project management tools and collaborative platforms.
Background and Evolution of Local-First Data Systems
Traditional project management tools rely heavily on centralized databases and cloud infrastructure, which can introduce latency, dependency, and lock-in issues. For more on local-first data systems, see this overview. The concept of local-first architecture has gained traction as a way to improve resilience and user control, with early implementations emphasizing synchronization and offline capabilities.
Threlmark’s approach builds upon these principles by making disk storage the primary data contract, rather than a secondary or auxiliary component. This design aligns with broader movements toward open data, interoperability, and user sovereignty, offering a practical implementation that addresses common pain points such as data corruption, merge conflicts, and system downtime.
While some systems have experimented with file-based storage, Threlmark’s explicit use of directory structures as a formal contract and its focus on atomic operations set it apart as a notable example of local-first architecture in action.
“Treating disk as the ultimate contract simplifies synchronization and enhances offline usability, making data more accessible and resilient.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Areas for Further Development
While the architecture demonstrates clear advantages, questions remain about how well it scales with very large datasets or complex concurrency scenarios. Managing many small files can introduce filesystem overhead, and conflict resolution in multi-tool environments may require further refinement. The long-term robustness of self-healing mechanisms and their performance in edge cases are still being evaluated.
Additionally, it is not yet confirmed how widespread adoption of this approach will be among other tools or how it will integrate with existing systems that rely heavily on databases or cloud services. These areas are actively being tested and developed.
Next Steps for Threlmark’s Local-First Architecture
Threlmark plans to continue refining its conflict resolution and self-healing mechanisms, aiming to improve scalability and performance. The team is also exploring broader integrations with external tools and formats, emphasizing adherence to the directory structure contract.
Future releases may include enhanced user interfaces for manual conflict resolution, better handling of large datasets, and more comprehensive documentation to facilitate third-party tool development. Monitoring real-world usage will inform further optimizations and stability improvements.
Key Questions
How does Threlmark prevent data corruption when editing files?
Threlmark employs atomic writes, where data is first written to a temporary file and then renamed to replace the original, preventing corruption during crashes or interruptions.
Can external tools modify Threlmark data safely?
Yes, the explicit directory structure and file-based format make it possible for external tools to read and write data, provided they follow the established contract and handle conflicts appropriately.
What are the main benefits of a disk-as-the-contract approach?
This approach offers increased resilience, offline capability, data portability, transparency, and reduced vendor lock-in, making systems more flexible and user-controlled.
Are there any drawbacks to this architecture?
Managing many small files can introduce filesystem overhead and complexity in conflict resolution, especially in environments with multiple concurrent editors.
Will this architecture work for large-scale or enterprise systems?
While promising for small to medium setups, scalability and performance in large datasets remain areas for ongoing testing and development.
Source: ThorstenMeyerAI.com
