📊 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 introduces a local-first, file-based architecture that treats disk storage as the definitive contract for project data. This approach enhances portability, safety, and interoperability, eliminating the need for a central database.
Threlmark’s new project management system is built entirely on local disk storage, with no reliance on servers or cloud databases, making the disk itself the authoritative source of project data. This design choice allows for a portable, restartable, and interoperable architecture that fundamentally redefines how project tools can operate.
The core of Threlmark’s architecture is that all project data resides in JSON files stored directly on the user’s disk, specifically within a directory structure under ~/.threlmark. The system uses a manifest (threlmark.json), a dependency graph (links.json), and individual files for each project and task, such as items/
Key to its safety and reliability are two disciplined patterns: atomic file writes and read-merge-write updates. Files are written atomically via temporary files and rename operations, preventing corruption during crashes. Updates merge with existing data, preserving crucial fields and tolerating unknown keys, which ensures forward compatibility. The system’s design allows external tools to participate seamlessly by reading and writing JSON files, enabling interoperability and open data access.
Furthermore, the architecture includes mechanisms for self-healing and consistency. The lane ordering in the project board is dynamically reconciled against existing items on each read, automatically adding missing items or dropping nonexistent ones. This approach reduces conflicts and maintains integrity without locks or complex synchronization.
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.
portable external SSD drive
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.JSON file management software
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.
atomic file write tools
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-first project management software
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 Local-First Architecture Matters for Project Tools
Threlmark’s approach demonstrates a shift toward decentralized, file-based project management that prioritizes data portability, safety, and simplicity. By removing the dependency on databases or cloud services, it enables users to have full control over their data, reduces vendor lock-in, and simplifies backup and migration. This architecture also facilitates interoperability, allowing diverse tools to read and modify project data directly, which can foster an ecosystem of integrated, open-source project management solutions.
In addition, the restartable nature ensures resilience; since all state is stored on disk, the system can recover from crashes without data loss. This design could influence future project management tools seeking more robust and user-controlled architectures, especially in privacy-sensitive or offline scenarios.
Background and Foundations of Threlmark’s Design
Traditional project management tools often rely on centralized servers or cloud databases, which introduce dependencies, lock-in, and potential security concerns. Threlmark’s design is inspired by principles from battle-tested file-based apps, emphasizing data as files that are atomic, mergeable, and portable. The concept of treating disk as the contract builds upon prior work in version control and local-first applications, aiming to address fragmentation in roadmaps and improve AI integration in project workflows.
The decision to avoid a server-of-record aligns with trends toward decentralization and user sovereignty over data, as discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Threlmark’s architecture reflects a deliberate choice to prioritize safety, interoperability, and resilience, making it suitable for developers and teams who prefer local control over their project data and automation pipelines.
“The core idea is that the on-disk layout itself is the API, making the data portable, safe, and open to any tool that can read and write files.”
— Thorsten Meyer
Unresolved Questions About Threlmark’s Scalability and Ecosystem
While the architecture’s benefits are clear, it remains uncertain how well this approach scales with very large projects or complex workflows. There are also questions about how external tools and integrations will evolve over time, and whether the approach can support real-time collaboration or multi-user scenarios without additional synchronization mechanisms. Further developments and community feedback are needed to evaluate these aspects fully.
Next Steps for Adoption and Ecosystem Development
Threlmark’s team plans to release more detailed documentation and encourage community experimentation with the file-based architecture. Future updates may include enhanced tooling for versioning, collaboration, and automation, aiming to expand the ecosystem around this local-first approach. Observers will watch for adoption in real-world projects and potential integration with other open-source tools.
Key Questions
How does Threlmark handle concurrent updates?
It uses atomic file writes and a self-healing board that reconciles changes on read, reducing conflicts without locks.
Can external tools modify Threlmark data?
Yes, since all data is stored as JSON files, any tool that can read and write files can participate in managing project data.
Is this approach suitable for team collaboration?
While designed for local control, multi-user collaboration at scale may require additional synchronization mechanisms, which are still under consideration.
What are the main advantages over traditional database-backed tools?
Portability, safety, interoperability, and resilience are key benefits, along with avoiding vendor lock-in and simplifying backups.
Source: ThorstenMeyerAI.com
