📊 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 has revealed a new local-first architecture where project data is stored entirely on disk as JSON files, making it portable, inspectable, and resilient. This approach challenges traditional server-based models and enables external tools and AI agents to participate seamlessly.
Threlmark has unveiled a novel architecture that treats disk storage as the definitive contract for project data, eschewing traditional server or cloud dependencies. This design allows external tools and AI agents to interact directly with data stored as JSON files on disk, enabling a portable, inspectable, and restartable workflow that fundamentally redefines project management tools.
The core of Threlmark’s approach is that the on-disk layout is the API, with each project consisting of a directory structure containing JSON files for project metadata, dependencies, and individual roadmap cards. This setup removes the need for a centralized database or server, making the entire system open and portable. Files are written atomically via rename operations, ensuring data integrity even during crashes or interruptions. The architecture supports multiple external tools, including AI agents, by reading and writing these files directly, fostering interoperability and collaboration.
Threlmark’s system organizes project data into a root directory (~/.threlmark), containing a manifest (threlmark.json), dependency graph (links.json), and project-specific folders. Each project folder holds metadata, lane configurations, and individual cards stored as separate JSON files in an items/ directory. Shared cards, archived projects, and external suggestions are managed within this structure, maintaining accessibility and version history. The design ensures that every artifact is inspectable, portable, and restartable, with no in-memory state that can be lost.
To ensure safety, Threlmark employs two disciplined patterns: atomic writes, which involve writing to temporary files before renaming, and read-merge-write updates that preserve unknown fields, allowing forward compatibility. The use of one file per item prevents race conditions during concurrent updates, and the self-healing board logic automatically reconciles discrepancies during reads, ensuring consistency without locks or complex coordination.
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.
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.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.
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.
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.
Implications of a Serverless, File-Based Data Model
This architecture challenges the conventional reliance on cloud servers and databases, offering a portable, inspectable, and resilient alternative. For developers and teams, it means greater control over data, easier backups, and seamless integration with external tools and AI agents. It also reduces dependencies, potentially simplifying deployment and improving robustness, especially in environments where server infrastructure is limited or undesirable.
By making data the source of truth stored directly on disk, Threlmark enables a new level of interoperability and flexibility, fostering innovation in project management workflows and automation. This approach could influence future tools to adopt similar local-first, file-based paradigms, especially as AI integration becomes more prevalent.
Python in Action: 60 Mini Projects to Automate Everything (Part 1): Practical CLI Tools, File Automation, and Data Cleaning with CSV, Excel, and JSON
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Evolution of Local-First and File-Based Project Tools
Traditional project management tools often rely on centralized servers, cloud storage, or proprietary databases, which can hinder portability and interoperability. Threlmark’s approach builds on prior trends toward local-first design, emphasizing data ownership and control. Its architecture echoes principles seen in version control systems like Git, where each artifact is stored as a file that can be inspected, versioned, and migrated easily.
Previous tools have experimented with file-based workflows, but Threlmark’s explicit design for concurrency, safety, and external tool participation marks a significant step forward. Its focus on making the on-disk layout the contract rather than a mere implementation detail aligns with broader movements toward open, interoperable software ecosystems.
This development comes amid increasing interest in AI-assisted workflows, where external agents need to read, modify, and act on project data without complex API layers. Threlmark’s architecture directly supports these trends by enabling AI agents to participate naturally through file operations.
“The on-disk layout is the API. This choice cascades into how concurrency, external tools, and AI agents participate without a server or database.”
— Thorsten Meyer, creator of Threlmark
local-first file-based data storage
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Unanswered Questions About Scalability and Adoption
It is not yet clear how well this architecture scales with very large projects or teams, or how it performs under high concurrency. The approach’s effectiveness in real-world, multi-user environments remains to be tested, and there is limited information on how external tools manage conflicts or synchronize changes at scale. Additionally, how this model integrates with existing workflows and tools is still under exploration.
![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]
- User-Friendly FTP Interface: Intuitive design similar to traditional FTP clients
- Reliable Site Management: Easy and dependable FTP site maintenance
- Automated File Transfers: FTP automation and synchronization
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Threlmark and Its Community
Threlmark plans to release more detailed documentation and developer tools to facilitate integration with external applications and AI agents. Future updates may include performance benchmarks, user feedback on scalability, and case studies demonstrating adoption in real projects. The community will likely experiment with the system’s portability and interoperability, shaping its evolution.
KALIM Needle File Set (10Pcs High Carbon Steel Files) and 1 Wire Cutter in A Carry Bag, File Tools for Soft Metal, Wood, Jewelry, Model, DIY, Hobby, etc.
- Compact Size: 10 high carbon steel needle files and wire cutter
- Delicate Work Suitable: Ideal for precise, detailed sanding and filing
- Versatile Applications: Perfect for jewelry, electronics, modeling, and DIY
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does Threlmark ensure data safety without a database?
It employs atomic file writes using temporary files and renaming to prevent corruption during crashes or interruptions.
Can external tools modify project data without conflicts?
Yes, since each item is stored in a separate file, concurrent modifications are collision-free, and the self-healing board reconciles discrepancies automatically.
Is this architecture suitable for large teams?
It is still uncertain how well this scales with large teams or complex projects; further testing and community feedback are needed.
How does this approach support AI integration?
AI agents can read and write JSON files directly, enabling seamless participation without specialized APIs.
Source: ThorstenMeyerAI.com
