📊 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 design treats local disk storage as the primary data source, avoiding traditional databases. This enhances offline capability, portability, and system transparency. The approach shifts complexity to managing file integrity and concurrency.
Threlmark’s new architecture design treats local disk storage as the definitive source of truth, eliminating the need for traditional databases or cloud servers. This approach is detailed in the original analysis. This approach simplifies data synchronization, improves offline usability, and enhances data portability across tools. The system relies solely on plain files stored directly on disk, making data accessible, transparent, and easy to inspect.
Threlmark’s design philosophy centers on using one file per data item, with atomic write operations to prevent corruption. Directory structures serve as explicit contracts, enabling external tools to read and modify data without proprietary interfaces. The system employs self-healing mechanisms that reconstruct views from individual files, ensuring consistency even when files are missing or corrupted.
Developers have implemented strategies such as atomic file writes—writing to a temporary file before renaming—to safeguard data integrity during updates. Merging changes from external sources is handled with tolerant algorithms that preserve essential metadata like IDs and timestamps, facilitating conflict resolution and smooth upgrades.
This architecture shifts the complexity from managing a centralized database to ensuring the correctness of file operations and directory structures, making the system more resilient and transparent. For a deeper dive, see this internal resource. It also allows for greater interoperability, as external tools can directly access and modify data files following the established directory layout.
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.
SANDISK 512GB Ultra USB 3.0 Flash Drive – SDCZ48-512G-G46, Black
Transfer speeds up to 10x faster than standard USB 2.0 drives (4MB/s); up to 130MB/s read speed; USB…
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.
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.
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-Driven Data Contract System
This approach fundamentally changes how data persistence and collaboration are handled in project management tools. By making disk storage the primary contract, Threlmark enables offline work, simplifies data portability, and reduces vendor lock-in. This can lead to faster, more reliable systems that are easier to inspect and extend.
However, it also shifts the development focus toward managing file integrity, handling concurrent edits, and designing robust conflict resolution mechanisms. The tradeoff involves balancing simplicity and transparency with the added complexity of file-based concurrency management.
Background and Development of Local-First Architecture
Traditional project management tools rely on centralized databases or cloud services, which can introduce latency, lock-in, and challenges with offline access. Local-first design principles, as discussed in this article, advocate for systems that prioritize local disk storage as the source of truth. Recent trends in local-first design advocate for systems that prioritize local disk storage as the source of truth, enabling seamless offline operation and data portability.
Threlmark’s architecture builds upon these principles by treating each data item as a separate file, with directory structures acting as explicit contracts. This design aligns with emerging best practices in local-first apps, emphasizing transparency, resilience, and interoperability.
“Treating the disk as the contract fundamentally simplifies data management and enhances offline capabilities.”
— Thorsten Meyer, Threlmark Developer
Unresolved Challenges and Open Questions
While the architecture demonstrates clear advantages, some aspects remain uncertain. It is not yet confirmed how well the system handles extremely high concurrency or large-scale data sets. The specific conflict resolution strategies and their effectiveness in complex collaboration scenarios are still being tested. Additionally, how this approach scales with more extensive integrations and external tools is yet to be fully demonstrated.
Future Developments and Next Steps for Threlmark’s Architecture
Threlmark plans to further refine its conflict resolution algorithms and improve the robustness of its self-healing mechanisms. Future updates may include enhanced tooling for manual conflict resolution and better support for large projects. The team also aims to expand interoperability with external editors and tools, leveraging the explicit directory structure as a formal data contract.
Key Questions
How does Threlmark ensure data consistency with file-based storage?
Threlmark employs atomic write operations—writing to a temporary file before renaming—to prevent corruption. It also uses tolerant merge algorithms that preserve essential metadata, ensuring consistency during concurrent edits.
Can external tools safely modify Threlmark’s data files?
Yes, the directory structure is designed as a clear contract, allowing external tools to read and write files directly, provided they follow the established format and conventions.
What are the main tradeoffs of using disk as the contract instead of a database?
The approach simplifies portability and offline access but shifts complexity toward managing file integrity, conflict resolution, and concurrency. It requires careful design of directory structures and update mechanisms.
Is this architecture suitable for large-scale or collaborative projects?
While promising, its scalability in high-concurrency environments remains under evaluation. Future enhancements aim to address these challenges more robustly.
Source: ThorstenMeyerAI.com
