📊 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 uses the local disk as the primary data source, avoiding databases. This approach improves offline capability, simplifies synchronization, and enhances data portability, making systems more resilient and transparent.
Threlmark’s new architecture designates the local disk as the definitive source of truth for all data, eliminating reliance on traditional databases. This approach enhances offline usability, simplifies synchronization, and promotes data portability, making systems more resilient and transparent. For a detailed overview, see the original analysis.
Threlmark’s system treats each data item as a separate file stored directly on the disk, with atomic write operations ensuring data safety. The directory structure acts as a formal contract, enabling external tools to read and modify data without proprietary interfaces. This design simplifies concurrency management by assigning one file per item, reducing race conditions and enabling easy recovery from corruption or conflicts.
To safeguard data integrity, Threlmark employs techniques like atomic file writes—writing to a temporary file before renaming it—and tolerant merging that preserves essential metadata. These mechanisms allow the system to handle concurrent edits and external interference gracefully. The directory layout is explicitly structured, making data accessible and understandable to both users and external tools, fostering interoperability and manual editing if needed.
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 1TB 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-1T00-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.![Express Rip Free CD Ripper Software - Extract Audio in Perfect Digital Quality [PC Download]](https://m.media-amazon.com/images/I/41xx28xHa+L._SL500_.jpg)
Express Rip Free CD Ripper Software – Extract Audio in Perfect Digital Quality [PC Download]
Perfect quality CD digital audio extraction (ripping)
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.
Data Recovery Stick | USB Data Recovery Device | Windows Data Recovery Software | Recover SD Card, Photos, Files
The Data Recovery Stick requires no technical skills — simply plug it into your Windows computer, click Start,…
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.
Local AI with VS Code: Mastering Private, Offline LLM Development: Run Open-Source Models Securely with Ollama, Continue, Llama.cpp, and Zero-Cloud Extensions – Keep Your Code and Data 100% Private
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.
Transforming Data Persistence and Tool Integration
This architecture shifts the paradigm from centralized databases to a decentralized, file-based system, offering benefits such as increased transparency, portability, and offline resilience. It reduces vendor lock-in and makes data more accessible for manual editing and external integrations, which is especially valuable for complex or collaborative workflows.
However, this approach introduces challenges in managing many small files and ensuring consistency across concurrent edits. It also requires careful design of directory structures and conflict resolution strategies. Overall, this method could influence future development of offline-first, resilient tools that prioritize user control over data.
Evolution of Data Storage in Local-First Systems
Traditional project management and collaboration tools rely heavily on centralized databases and cloud infrastructure, which can limit offline access and introduce vendor lock-in. Recent trends favor local-first architectures, where data resides primarily on the user’s device, syncing only when necessary.
Threlmark’s approach builds on this trend by treating the disk as the contract for data integrity and consistency. This design aligns with principles seen in other local-first tools but emphasizes explicit directory structures and file-level safety mechanisms to ensure robustness and interoperability.
“Treating the disk as the contract simplifies synchronization and makes data more portable and resilient.”
— Thorsten Meyer, Threlmark developer
Unresolved Challenges in File-Based Data Management
It is not yet clear how Threlmark handles large-scale data or complex merge conflicts in practice. The specific strategies for conflict resolution, versioning, and manual recovery are still under development or not fully detailed. Additionally, the impact on performance with many small files and the scalability of the directory structure remain to be seen.
Future Developments and Adoption Strategies
Threlmark plans to refine its conflict resolution mechanisms and improve scalability. Further documentation and user feedback will clarify how well the system performs in diverse workflows. Broader adoption and integration with external tools are expected to follow, potentially influencing other local-first projects.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark uses atomic file operations—writing to temporary files before renaming—to prevent corruption. It also employs tolerant merging to handle concurrent edits safely.
Can I manually edit data files in Threlmark?
Yes, the explicit directory structure makes manual editing possible, promoting transparency and interoperability.
What are the main advantages of this disk-as-contract approach?
It improves offline usability, simplifies synchronization, enhances data portability, and reduces vendor lock-in.
What challenges might this architecture face?
Managing many small files, resolving conflicts during concurrent edits, and scaling for large datasets remain potential challenges.
Source: ThorstenMeyerAI.com
