📊 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 centers on using the local disk as the primary data source, avoiding traditional databases. This approach improves offline access, data portability, and system transparency. The article explores how this design impacts data safety, concurrency, and integration.
Threlmark has adopted a system where the local disk is the definitive source of truth, replacing traditional databases and cloud reliance. This approach is detailed in the original analysis. This design simplifies data synchronization, enhances offline capabilities, and ensures data portability, making the system more resilient and transparent. The approach is a significant shift in how project management tools handle data persistence and collaboration.
Threlmark’s architecture treats each piece of data as a separate file stored directly on the user’s disk, with one file per item such as cards or project metadata. This structure acts as a formal contract, enabling external tools and manual edits to interact seamlessly without proprietary databases or cloud dependencies. For a deeper dive, see this internal overview. The system employs atomic file writes—writing to a temporary file then renaming—to prevent corruption during updates, and merges changes carefully to tolerate conflicts or missing data. This approach reduces race conditions and simplifies recovery from errors.
By organizing data in explicit directory structures, Threlmark enhances transparency and interoperability. External tools can read and write files directly, fostering a flexible ecosystem. The design also incorporates self-healing mechanisms that reconstruct project views from individual files, ensuring consistency even if some files are corrupted or missing. This setup allows offline work, faster access, and easier data migration, aligning with local-first principles.
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.
SANDISK 128GB Ultra Flair USB 3.0 Flash Drive, SDCZ73-128G-G46, Black
High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard…
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.
Advanced File Recovery – #1 Data Recovery Software | Recover Deleted Files, Photos, Documents, Audio, Videos & More | 1 PC 1 Year | (License Key Via Postal Service – No CD)
Recover deleted files, photos, documents, audio, videos & more
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.
GODIAG GT111 for VW Audi Skoda Seat CAN-Bus 3rd & 3.5th Generation Dashboard IM-MO Key Matching Test Platform Cable with POGO PIN to Read & Write Data
Supports VW Audi Skoda Seat: Performs offline key and IM-MO instrument synchronization test, intelligent IM-MO system emergency start…
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 a Disk-Centric Data Model
This architecture fundamentally changes how data is managed in project tools, emphasizing resilience, portability, and transparency. By making the disk the contract, Threlmark reduces vendor lock-in and simplifies synchronization across devices and tools. It also enables users to work offline without losing data integrity, which is critical for remote or mobile workflows. However, this approach shifts complexity to handling concurrency and conflict resolution, requiring careful design of file operations and merging strategies.
Background and Evolution of Local-First Systems
Traditional project management and collaboration tools rely heavily on centralized databases and cloud servers, which can introduce latency, dependency on internet connectivity, and vendor lock-in. This trend is explored in this detailed article. The local-first movement advocates for storing data locally, with synchronization as a secondary concern. Threlmark’s approach builds on this philosophy, emphasizing a file-based, transparent data model that prioritizes user control and system resilience. This aligns with broader trends in decentralized and open data architectures, but Threlmark offers a specific implementation tailored for project management.
Previous efforts in local-first design have highlighted benefits such as offline access and ease of data migration. Threlmark’s innovation lies in formalizing the disk as the contract, with explicit directory structures and file-level safety mechanisms, making it suitable for complex, multi-tool environments.
“Treating the disk as the contract simplifies synchronization and enhances offline usability, making data more accessible and resilient.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges and Potential Limitations
While the approach offers many benefits, questions remain about how well it scales with very large datasets or complex conflict scenarios. Managing many small files can introduce filesystem overhead, and manual conflict resolution may become cumbersome at scale. It is also not yet clear how seamless integration with existing tools and workflows will be in practice, or how the system handles simultaneous external edits in high-collaboration environments.
Future Developments and Adoption Roadmap
Threlmark plans to refine its conflict resolution algorithms and improve tooling for manual and automatic merge handling. Further testing in real-world, multi-user environments will determine scalability and robustness. The company also aims to develop integrations with popular external tools, leveraging the explicit directory structure and file-based data model. Monitoring user feedback and addressing edge cases will be key steps in evolving this architecture into a standard for local-first project management.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark uses atomic file writes—writing to a temporary file then renaming it over the original—to prevent corruption. It also merges changes carefully to tolerate conflicts, ensuring data integrity even during concurrent edits.
Can Threlmark’s system work offline without any internet connection?
Yes, since all data is stored locally in files, users can work offline without losing access or risking data inconsistency.
What are the main tradeoffs of using a file-based architecture?
The approach simplifies data portability and resilience but increases complexity in managing file conflicts, filesystem overhead, and ensuring consistency across many small files.
How does external tool integration work in Threlmark?
External tools can read and write files directly within the directory structure, as long as they adhere to the established data contract, enabling flexible extension and automation.
Source: ThorstenMeyerAI.com
