📊 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 employs a local-first architecture where project data is stored as JSON files on disk, making the system portable, inspectable, and restartable without a database. This design supports external tools and AI integration while ensuring data safety.
Threlmark has introduced a novel architecture in which all project data is stored directly on disk as JSON files, with no server or centralized database involved. This approach makes the system highly portable, inspectable, and resilient, supporting external tools and AI agents that interact directly with the file system. The key design decision is that the on-disk layout itself acts as the API, establishing a ‘disk is the contract’ model that underpins the entire system.
The core of Threlmark’s design is that all project artifacts—such as cards, dependencies, and lane configurations—reside in individual JSON files within a dedicated directory, defaulting to ~/.threlmark. This directory contains a manifest (threlmark.json), a dependency graph (links.json), and folders for each project, with files for each roadmap card, suggestions, handoffs, reports, and shared items. This structure ensures that every artifact is fully inspectable, portable, and interoperable, enabling users to back up, migrate, or integrate with other tools easily.
Two key techniques make this architecture safe and reliable. First, atomic file writes are achieved by writing to temporary files and renaming them atomically, preventing corruption during crashes. Second, the system uses read-merge-write updates with tolerant normalization, allowing for forward compatibility and preserving unknown fields, so external tools can evolve without breaking existing integrations. The system also employs a self-healing board that reconciles its state on each read, adding missing items and removing nonexistent ones, ensuring consistency without locks or shared memory.
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.
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
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 management tools
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.
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
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.
Smart Keypad Door Lock with Handle, Smart Door knobs with Lock, Auto Door Lock with Code and App, Keyless Entry Door Knob for Bedroom, Front Door, Smart Home, Apartment, Local Data Storage
3-in-1 Smart Access Upgrade for Every Space – Transform your entryway experience with the KLLOQUE door lock, designed…
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-First Design Transforms Project Management
This architecture shifts the paradigm from centralized databases to a decentralized, file-based approach, giving users full control over their project data. It enhances portability, allowing easy backups and migrations, and fosters interoperability with external tools and AI agents that directly manipulate JSON files. By avoiding server reliance, Threlmark offers a resilient, restartable system that can adapt to various workflows and environments without lock-in, potentially influencing future project management tools to adopt similar local-first principles.
The Evolution of Local-First and File-Based Systems
Traditional project management tools often rely on cloud-based servers and databases, which can introduce lock-in, reduce transparency, and complicate backups. Threlmark’s approach builds on the growing trend of local-first applications that store data locally and synchronize selectively. Its design echoes principles from version control and local development environments, emphasizing data ownership, inspectability, and robustness. The decision to make the disk layout the API represents a deliberate move toward simplicity and interoperability, contrasting with more complex, server-dependent architectures.
“The on-disk layout is the API. That choice cascades into how concurrency is handled, why there’s one file per card, and how external tools can participate without permission.”
— Thorsten Meyer
Remaining Questions About Threlmark’s Scalability and Adoption
While the architecture promises robustness and flexibility, it is not yet clear how well this approach scales with very large projects or teams. There is also limited information on how external tools and AI agents will handle complex, concurrent updates in practice, or how users will manage conflicts and versioning at scale. Further testing and real-world adoption will clarify these issues.
Next Steps for Threlmark’s Development and Community Adoption
Threlmark plans to release detailed documentation and tooling to support external integrations, along with real-world case studies demonstrating its scalability. User feedback and community engagement will likely shape future enhancements, including improved conflict resolution and multi-user support, as the project matures and gains wider adoption.
Key Questions
How does Threlmark ensure data safety without a database?
Threlmark uses atomic file writes—writing to temporary files and renaming them atomically—to prevent corruption during crashes. Its read-merge-write approach with tolerant normalization also preserves data integrity and forward compatibility.
Can external tools modify Threlmark data safely?
Yes. Since each artifact is a separate JSON file, external tools can read and write files directly. The system’s design ensures that updates are collision-free and self-healing, maintaining consistency without locks.
What are the limitations of this file-based architecture?
While promising, it remains to be seen how well this approach handles very large projects or high concurrency scenarios. Scalability and conflict management in multi-user environments are areas for further testing.
Will Threlmark support multi-user collaboration?
Current design favors single-user or controlled environments. Future updates may introduce more robust multi-user support, but details have not yet been announced.
How does this approach compare to traditional cloud-based tools?
Unlike cloud tools that store data remotely, Threlmark’s local-first approach offers full data ownership, easier backups, and interoperability, reducing lock-in and increasing control.
Source: ThorstenMeyerAI.com
