📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark has announced a new roadmap methodology where the roadmap is a simple JSON file stored locally, making it accessible and modifiable by any tool that reads JSON. This approach emphasizes durability, interoperability, and user ownership over traditional SaaS tools.
Threlmark has introduced a novel approach to project roadmaps, asserting that the roadmap should be a plain JSON file stored locally on a user’s disk, rather than hosted inside a SaaS platform. This approach is similar to the ideas discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. This shift aims to enhance interoperability, ownership, and durability, making project plans accessible and editable by any tool capable of reading or writing JSON.
The core idea behind Threlmark’s ‘disk is the contract’ approach is that the project roadmap exists as a simple, structured JSON file on the user’s local disk. This file serves as the single source of truth, with the roadmap’s schema acting as the integration contract. Any program that can interpret JSON can read or modify the roadmap, eliminating dependency on proprietary SaaS APIs or SDKs.
Threlmark’s product also features a scored kanban board, where each task carries a priority score, facilitating better decision-making through visible trade-offs. The system supports a live agent loop, allowing automated agents to read, update, and write back to the JSON file, enabling real-time collaboration between humans and AI agents without complex integrations.
This approach emphasizes local-first and provider-agnostic design principles, meaning the roadmap file is owned by the user and can be used with any compatible tool, ensuring long-term access and avoiding vendor lock-in. However, it also acknowledges limitations, such as reduced support for concurrent multi-user editing and conflict resolution, which are typical advantages of SaaS tools.
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 Project Data Ownership and Interoperability
This development matters because it shifts control of project data from SaaS platforms to the user, reducing dependency on vendor-specific tools and APIs. It echoes the principles outlined in The referral. How AI search severs the content-for-traffic contract that funded the open web. It promotes durability, as the roadmap exists as a simple, portable file that can outlive any single tool or service. For small teams and operators, this approach simplifies automation and collaboration, enabling seamless integration with any JSON-compatible system.
However, it also introduces challenges related to multi-user collaboration, such as conflict management and real-time presence, which are less robust compared to traditional SaaS solutions. The approach prioritizes long-term ownership and interoperability over real-time, large-scale collaboration features.

AI TOOLS FOR THE MODERN BUSINESS: The Complete Step-by-Step Blueprint to Automating Marketing, Client Work, and CRM with ChatGPT, n8n, and Make.com.
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The Evolution of Roadmap Management and Open Data Principles
Traditional project management tools rely heavily on SaaS APIs, SDKs, and proprietary formats, which can lead to vendor lock-in and data portability issues. This is part of the broader conversation about open data principles, as discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Threlmark’s approach builds on open data principles, emphasizing local control and simplicity. The concept of representing a roadmap as a plain JSON file aligns with broader movements toward open standards and data durability, especially for small teams or individual operators.
This idea is a response to the limitations of SaaS tools, which, while offering collaboration features, often sacrifice long-term access and control. Threlmark’s method reintroduces the fundamental principle that operational data should be owned and portable, resisting the trend toward vendor lock-in.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. Threlmark makes a deliberately different bet: the roadmap is a plain JSON file sitting on your own disk.”
— Thorsten Meyer, Threlmark
local-first project roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations of Local-First Roadmap Approach
It remains unclear how well this approach scales for large, distributed teams requiring simultaneous editing, conflict resolution, and real-time collaboration. The system’s effectiveness in enterprise environments with complex permissioning and audit needs is also still untested. Additionally, the impact of potential agent mis-writes and how to manage such risks is an open question.
Kanban board with scoring
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Tool Integration
Threlmark plans to release detailed documentation and open-source tools to facilitate adoption of the ‘disk is the contract’ model. Future developments may include enhanced conflict management, version control, and collaborative editing features, aiming to bridge the gap between simplicity and large-team needs. Monitoring user feedback and real-world use cases will shape the evolution of this approach.
AI collaboration tools for project planning
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 simultaneously?
Currently, the approach is optimized for small teams or individual operators. Handling concurrent edits and conflict resolution is acknowledged as a limitation, and future features may address this, but it is not yet part of the core system.
Can existing project management tools integrate with this JSON-based roadmap?
Yes. Since the roadmap is a plain JSON file, any tool capable of reading or writing JSON can potentially integrate, making it highly interoperable. However, specific integrations are yet to be developed or documented.
What are the main advantages of owning my roadmap as a file?
Ownership ensures long-term access, durability, and freedom from vendor lock-in. You control the data directly, and it can be used with any compatible tool, reducing dependency on proprietary SaaS platforms.
What risks come with allowing agents to write to the roadmap?
Agents that mis-write or corrupt the JSON file pose a risk of data inconsistency or loss. Proper guardrails, review processes, and safeguards are necessary to mitigate these risks.
Source: ThorstenMeyerAI.com