📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark announces a new roadmap methodology where the plan is a plain JSON file stored locally, making it accessible, durable, and vendor-agnostic. This shifts control from SaaS tools to users’ own systems.
Threlmark has unveiled a new product philosophy stating that “disk is the contract” for roadmaps, meaning the entire planning artifact is a plain JSON file stored locally on the user’s machine. This approach is explained in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. This approach eliminates reliance on SaaS APIs, enabling interoperability and durability.
Threlmark’s product is built around the idea that a roadmap should be a simple, structured JSON file residing on the user’s disk. The roadmap acts as the single source of truth, with tools and agents capable of reading and writing to this file without needing API integrations or vendor lock-in. The system supports scoring and prioritization, with each item carrying a score that determines its importance, facilitating clear trade-offs. This is part of the broader discussion on raw-feed licensing and how data contracts are evolving. Because the roadmap is a plain file, it remains accessible and durable over time, independent of any specific tool or platform. The architecture is designed for small teams or operators managing automated workflows, not for large, multi-user enterprise environments requiring real-time collaboration or conflict resolution. Threlmark emphasizes that this approach provides interoperability by default, as any program capable of handling JSON can interact with the roadmap, making it provider-agnostic and local-first. The company acknowledges that this simplicity comes with trade-offs, including limitations in concurrent editing and conflict management, which are not suited for large-scale enterprise use.Threlmark — disk is the contract
The roadmap is a plain JSON file on your disk. The board is just a view over it — and your tools and your agents read and write the same file directly.
Independent commentary, produced with AI assistance under human editorial oversight. The views are the author’s own and may change. Threlmark is open source under MIT, provided “as is” without warranty; see the repository LICENSE. Automated agents that read and write the roadmap file may introduce errors — treat agent writes as changes to review, not facts to trust. Product and company names are trademarks of their respective owners; mention does not imply endorsement.
Implications for Small Teams and Automation
This approach shifts control of the roadmap from SaaS vendors to users, ensuring long-term access and interoperability. It simplifies automation workflows, allowing agents and human users to read and update the plan directly via JSON files, reducing dependencies and vendor lock-in.
However, it also means sacrificing features like real-time collaboration, conflict resolution, and audit trails that are common in enterprise-grade tools. For small teams or operators managing automated processes, this method offers a straightforward, durable, and flexible solution that emphasizes ownership and longevity of planning data.
JSON file editor for Windows
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The Shift Toward Local-First Roadmaps
Traditional roadmap tools often rely on SaaS platforms with APIs, which can lead to vendor lock-in, API deprecation, and data portability issues. Threlmark’s philosophy challenges this by proposing that the roadmap should be a simple, structured file that the user owns and controls.
This idea builds on principles of local-first data management and interoperability, similar to other open-source or decentralized tools. The concept is not entirely new but represents a significant shift in how operational planning artifacts are stored and shared.
“A roadmap that lives inside your disk and is just a JSON file is a different kind of contract—one that’s open, durable, and vendor-agnostic.”
— Thorsten Meyer, Threlmark founder
local-first project management software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Risks of Disk-Based Roadmaps
It remains unclear how well this approach scales for large, multi-user teams requiring real-time collaboration and conflict resolution. The effectiveness of agent automation and safeguards against data corruption are still under evaluation, and there is no mention of built-in version control or audit trails.
Additionally, the practical implications of managing manual updates and ensuring consistency across tools are still being explored.
version control for JSON files
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Development
Threlmark plans to release the full open-source implementation and documentation, allowing users and developers to experiment with the approach. Future updates may include tools for version control, conflict management, and multi-user support, though the core philosophy remains focused on simplicity and owner control.
User feedback and community engagement will likely shape further iterations of the product, especially regarding scalability and safety features.
offline roadmap planning tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does this approach handle multiple users editing the roadmap?
Currently, it is designed for small teams or automation workflows. Handling concurrent edits and conflict resolution is not built-in and remains a challenge for larger teams.
Can existing project management tools integrate with this JSON-based roadmap?
Any tool capable of reading and writing JSON can interact with the roadmap file, enabling integration with various custom or open-source tools.
What are the main advantages of using a disk-based roadmap?
Ownership, durability, vendor independence, and simplicity. The roadmap remains accessible long-term, independent of SaaS platform changes.
Are there any security or permission controls with this approach?
Since the roadmap is a local file, security depends on local file permissions. There are no built-in permissioning or audit trail features like those in SaaS tools.
Is this approach suitable for large enterprise projects?
Not currently. It is best suited for small teams or automation workflows that do not require real-time multi-user collaboration.
Source: ThorstenMeyerAI.com
