📊 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 local-first architecture makes the disk the primary data source, using one file per item with atomic writes for safety. This approach improves offline capability, data portability, and system transparency, shifting complexity to file management.

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 Disk Is the Contract: Inside Threlmark’s Local-First Architecture. This approach simplifies data synchronization, enhances offline usability, and makes data portable across tools, marking a significant shift in how project data is managed.

Threlmark’s system operates by storing each data item in individual files, using atomic write operations to prevent corruption and race conditions. The directory structure acts as a formal contract, making data organization transparent and accessible for manual editing or external tool integration. This design reduces dependency on proprietary databases, allowing users to work with plain files directly, which improves resilience during system failures and enhances interoperability. To ensure safety, Threlmark employs techniques like temporary file writes and tolerant merging, which handle concurrent edits and data conflicts without locking the entire system. This architecture shifts complexity from centralized data management to careful file handling, requiring developers to design robust directory structures and update mechanisms.
Disk is the contract: inside Threlmark’s architecture — ThorstenMeyerAI.com
ThorstenMeyerAI.com
Threlmark · Technical Deep-Dive
Threlmark · 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.

Next.js · TypeScript · JSON-on-disk · MIT · part 2 of the Threlmark series
01The core decision

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.

~/.threlmark/ ├─ threlmark.json # manifest ├─ links.json # dependency graph ├─ projects// │ ├─ project.json # meta + wipLimits │ ├─ board.json # lane ordering │ ├─ items/.json # ONE card per file ← source of truth │ ├─ suggestions/ # the Inbox (drop-zone) │ ├─ handoffs/ # recorded agent handoffs │ ├─ reports/ # agent report drop-zone │ └─ ROADMAP.md # human-readable mirror ├─ shared/items/ # cards many projects ref └─ archive/ # archived, still readable

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.

02Making files safe
Samsung T7 Portable SSD, 1TB External Solid State Drive, Speeds Up to 1,050MB/s, USB 3.2 Gen 2, Reliable Storage for Gaming, Students, Professionals, MU-PC1T0T/AM, Gray

Samsung T7 Portable SSD, 1TB External Solid State Drive, Speeds Up to 1,050MB/s, USB 3.2 Gen 2, Reliable Storage for Gaming, Students, Professionals, MU-PC1T0T/AM, Gray

MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to…

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.

Pattern 1

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.

write .tmp-pid-rand fsync rename() over target
Pattern 2 · one file per item

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.

The payoff: an external tool never touches 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.
03Derived, never stored
PNY 256GB Attaché X USB 3.2 Gen 1 Flash Drive, Advanced Performance Up to 130MB/s Read, Everyday Data Store & Transfer, Reliable Portable Storage, Durable, Type-A, Computers, Laptops, Desktops

PNY 256GB Attaché X USB 3.2 Gen 1 Flash Drive, Advanced Performance Up to 130MB/s Read, Everyday Data Store & Transfer, Reliable Portable Storage, Durable, Type-A, Computers, Laptops, Desktops

Performance: Advanced read speeds of up to 130MB/s for everyday data storage & transfers²

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.

priority = max(0, round(impact·3 + evidence·2 + fit·2effort·1.5))
a 5 / 5 / 5 / 4 card 29
work-item age
now − lane-entry time. Past threshold (dev 7d, ranked 21d, idea 60d) → stale.
cycle time
first DevelopmentDone. Derived from append-only transitions[].
throughput
items reaching Done per ISO week, 8-week window.
WIP
count per lane; over the cap shows 3 / 2 in red.
04The closed agent loop · press play
Siveit CD/DVD Case Binder - 400 Capacity Disc Storage Holder, Black PU Binder

Siveit CD/DVD Case Binder – 400 Capacity Disc Storage Holder, Black PU Binder

The Sivet CD/DVD case bag is made of durable, moisture-proof, and tear resistant silk fabric, which can be…

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.

Ranked
Add price-drop alertsscore 31 · ready
Development
Handed off 🤖
Done
▶ preferred — REST
POST /api/projects/:id/
items/:itemId/report

Direct call. Applied immediately.

▶ fallback — filesystem
drop reports/.json
→ ingested on read

Robust even if the server’s down at finish time.

🤖 claude done: price-drop alerts shipped · typecheck + lint + build passed — card moved to Done
05Portfolio score & deployment
USB 3.0 to SATA IDE Bay Docking Station for 2.5 or 3.5in HDD SSD, Support 20TB, Hot Swap, Offline Clone, Tool Installation (US Plug)

USB 3.0 to SATA IDE Bay Docking Station for 2.5 or 3.5in HDD SSD, Support 20TB, Hot Swap, Offline Clone, Tool Installation (US Plug)

6Gbps Transfer Speed: USB transfer interface meets USB 3.0 standard specifications, supports 6Gbps transfer speed, fast file transfer,…

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 (/), the Portfolio ranks everything together by a status-weighted score — finishing beats starting, blockers get a boost.

Portfolio ranking — status-weighted

In-flight work floats to the top; bottlenecks cost the most, so blockers get nudged up.

score = priority · statusWeight (+ 0.1 · blockedCount · priority)
1.3
development
1.0
ranked
0.85
idea
0.15
done
Path 1

Static read-only demo

Seeded data, writes to localStorage. Try-before-you-clone.

Path 2

Personal Node instance

Password-gated, persistent backed-up THRELMARK_DATA_DIR.

Path 3

Multi-tenant SaaS

Add accounts + per-tenant isolation. A separate build.

The elegant part: the store interface 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.
ThorstenMeyerAI.com
Threlmark · open source (MIT) · github.com/MeyerThorsten/threlmark · part 2 of a series · file layout, formula, weights & agent-loop channels are Threlmark’s actual mechanics.

Impacts of a Disk-Centric Data System

Making the disk the primary contract changes the way data is stored, accessed, and shared. It reduces vendor lock-in, enhances offline capabilities, and improves transparency, making tools more resilient and flexible. This approach is particularly relevant for developers seeking lightweight, portable, and easily inspectable systems, especially in environments where internet access is unreliable or where data sovereignty is critical. However, it also introduces new challenges in managing file concurrency and conflict resolution, which require careful engineering.

Evolution Toward Local-First Data Management

Traditional project management tools rely heavily on centralized databases and cloud services, which can introduce dependencies, lock-in, and synchronization issues. This shift toward local-first principles is explained in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Threlmark’s approach draws from local-first principles, emphasizing the importance of treating local disk storage as the single source of truth. This paradigm shift aligns with broader trends toward offline-first and resilient software, offering a different perspective on data integrity and interoperability. The concept builds on prior efforts to improve data portability and reduce reliance on proprietary systems, but Threlmark’s implementation emphasizes explicit directory structures and file-based operations to achieve these goals.

“Treating the disk as the contract fundamentally simplifies data synchronization and enhances offline usability.”

— Thorsten Meyer, Threlmark developer

Unresolved Challenges in File-Based Data Integrity

While Threlmark employs atomic writes and tolerant merging to safeguard data, the system’s behavior under complex concurrent edits or manual manual file manipulations remains to be fully tested. For a detailed analysis, see the original analysis. It is also unclear how well the approach scales with very large datasets or complex directory structures, and whether manual interventions could introduce inconsistencies. Further real-world testing is required to validate these safety mechanisms across diverse use cases.

Next Steps for Adoption and Validation

Threlmark plans to continue refining its file management techniques and expand its user base to gather practical feedback. Future developments may include automated conflict resolution, enhanced recovery tools, and detailed documentation for manual editing. Additionally, broader adoption by external developers will test the system’s interoperability and robustness in varied environments. Monitoring how the architecture performs at scale will be critical to understanding its long-term viability.

Key Questions

How does Threlmark ensure data safety without a traditional database?

Threlmark uses atomic file writes and tolerant merging techniques to prevent data corruption and handle concurrent edits, ensuring data integrity directly at the file level.

Can I manually edit data files in Threlmark?

Yes, the directory structure is transparent and designed for manual editing, but users should understand the system’s merge and conflict mechanisms to avoid inconsistencies.

What are the main benefits of a disk-centric architecture?

It improves offline usability, data portability, transparency, and resilience against system failures or disconnections.

What challenges might arise from this approach?

Managing many small files, handling concurrent edits, and ensuring consistency across complex directory structures can be challenging and require careful system design.

Will this architecture scale for large projects?

Scalability is still being tested; while small to medium projects benefit, very large datasets may need additional optimization or management strategies.

Source: ThorstenMeyerAI.com

You May Also Like

Apple’s New SpeechAnalyzer API, Benchmarked Against Whisper And Its Predecessor

Apple’s new SpeechAnalyzer API is tested against Whisper and its predecessor, highlighting advancements in speech recognition technology.

The Memento Constraint: Why Continual Learning Is the Trillion-Dollar Bottleneck Nobody Is Pricing

Exploring how the inability of current AI models to learn continually could reshape the trillion-dollar enterprise AI economy, with insights from recent research.

Review response quality coach for local service businesses

Testing of a review response quality coach for local service businesses is underway, aiming to improve reply speed, professionalism, and compliance.

Corvus ISR Day 1: Crafting A WAMI Exploitation Stack Using Synthetic Data

Corvus ISR launches with a synthetic WAMI scene featuring live detection and tracking, demonstrating a new approach to exploitation software for wide-area motion imagery.