📊 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 new approach uses disk-based JSON files as the single source of truth, enabling portable, inspectable, and restartable project management without a database. This design allows external tools and AI agents to interact directly with project data.
Threlmark has adopted a novel local-first architecture that treats disk-based JSON files as the definitive source of project data, eliminating the need for a server or database. Disk Is the Contract: Inside Threlmark’s Local-First Architecture This approach enables open, portable, and restartable project management, supporting external tools and AI agents directly interacting with files.
Threlmark’s core design decision is that the on-disk layout is the API, with no server-of-record. The system organizes project data into a directory structure under ~/.threlmark, including a manifest, dependency graph, project metadata, and individual item files. Each project has its own folder, with one JSON file per roadmap card, facilitating inspectability and portability. This setup allows tools to read, write, and synchronize data without lock-in or server dependencies. The architecture emphasizes data safety through atomic file writes, achieved by writing to temporary files and renaming them atomically. Updates are handled via read-merge-write cycles, preserving data integrity and forward compatibility by retaining unknown fields. The system’s design ensures that external tools can participate seamlessly, as each file is a self-contained, versioned artifact, enabling the entire project state to be reconstructed reliably after crashes or interruptions.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.
JSON file editor for project management
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.portable JSON data viewer
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 Disk as the Contract Transforms Project Management
This architecture shifts the paradigm from cloud-based or server-dependent project tools to a decentralized, file-based system. It enhances data portability, making it easy to back up, migrate, and integrate with other tools. The approach also improves resilience, as the entire project state is stored locally in simple files, reducing reliance on external services and increasing control for users. For AI and automation, it opens new possibilities for direct manipulation and understanding of project data without intermediary layers.
Historical Challenges with Fragmented Roadmaps and Centralized Data
Traditional project management tools often fragment roadmaps across multiple platforms, such as Notion, Trello, or local files, with no unified source of truth. Cloud-based solutions introduce dependency and lock-in, while local tools typically lack portability and interoperability. Threlmark’s approach responds to these issues by creating a unified, portable format based on plain JSON files, inspired by previous local-first applications but uniquely applied to multi-project roadmaps and AI integration.
“The core idea is that the disk is the contract, not a database or server. This makes the data open, portable, and resilient, while enabling external tools and AI agents to participate directly.”
— Thorsten Meyer, creator of Threlmark
Remaining Questions About Scalability and External Tool Support
It is not yet clear how well this architecture scales with very large projects or numerous concurrent external tools. The robustness of file-based concurrency under high load remains to be tested, and user experience details for managing complex multi-project setups are still emerging.
Next Steps for Adoption and Tool Integration
Threlmark plans to release further documentation and developer APIs to facilitate broader tool integration. User feedback will guide enhancements in handling larger projects and more complex workflows. Additionally, testing with AI agents and external automation tools will continue to expand the system’s capabilities.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes—writing to a temporary file and then renaming it atomically—to prevent corruption during crashes or interruptions.
Can external tools modify Threlmark data?
Yes, since the data is stored in plain JSON files, any tool that can read and write JSON can participate, enabling interoperability and automation.
What are the limitations of this architecture?
Scalability with very large projects or high concurrency scenarios remains untested, and managing complex workflows may require additional tooling or interface improvements.
How does this approach support AI agents?
AI agents can directly read, modify, and move JSON files, enabling automated workflows that close the loop without intermediary servers or databases.
Source: ThorstenMeyerAI.com
