📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark announces a radical new roadmap system where the plan is a JSON file stored locally, making it open, simple, and vendor-agnostic. This shift emphasizes ownership and interoperability, but raises questions about collaboration and concurrency.
Threlmark has introduced a new approach to project roadmaps where the entire plan is stored as a plain JSON file on the user’s local disk, making ‘disk the contract.’ This design aims to provide a simple, open, and vendor-agnostic alternative to traditional SaaS roadmap tools, emphasizing ownership and durability.
The core idea is that the roadmap is a JSON file with a known structure, which any program capable of reading and writing JSON can access. This removes dependency on SaaS APIs, allowing users to maintain full control over their data and ensuring long-term accessibility. The system integrates scoring for prioritization, enabling ranked task management, and supports an agent loop where automated agents can read, update, and write back to the file, creating a live, shared workspace.
Threlmark emphasizes local-first architecture, meaning the roadmap resides on the user’s machine, and provider-agnostic design, as any tool that can handle JSON can interface with it. The approach is designed for small teams or operators who value simplicity and durability over real-time multi-user collaboration features. The company also highlights that this method sacrifices some SaaS advantages like conflict resolution, concurrent editing, and permission management, which are less suited for small-scale or individual use cases.
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 of a ‘Disk Is the Contract’ Roadmap System
This approach shifts control and ownership of project plans directly to users, reducing vendor lock-in and increasing data durability. It enables seamless interoperability with any JSON-compatible tool and simplifies automation through shared file access. However, it also introduces limitations in real-time collaboration, conflict management, and multi-user editing, making it more suitable for small teams or individual operators.
For organizations seeking simplicity, long-term data control, and tool independence, this model offers a compelling alternative. Yet, it may not meet the needs of large, distributed teams requiring advanced collaboration features, raising questions about its broader applicability.
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.
Background and Prior Developments in Roadmap Management
Traditional project management tools rely heavily on SaaS platforms, offering features like real-time collaboration, conflict resolution, and permission controls. However, these tools often create vendor lock-in and depend on APIs that can change or become deprecated. Threlmark’s new approach challenges this paradigm by proposing a local, file-based system that emphasizes ownership and interoperability. This concept aligns with broader trends favoring open formats and local-first architectures, but it is a departure from the collaborative features common in enterprise tools.
“A roadmap that lives inside your disk is a deliberate choice for ownership, durability, and interoperability. It’s about making your plan a real asset you control.”
— Thorsten Meyer, Threlmark founder
local JSON roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Challenges of the Local-File Roadmap Model
It is not yet clear how well this approach scales for larger teams or organizations that require real-time collaboration and conflict resolution. The system’s reliance on manual review of agent updates and scoring accuracy could pose risks of misprioritization or data corruption. Additionally, the lack of built-in permissioning and audit trails raises concerns about security and oversight in multi-user environments. Further testing and user feedback are needed to assess its practical viability for broader adoption.
Business Models and Strategies for Open Source Projects
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Development of the ‘Disk Is the Contract’ System
Threlmark plans to release the full open-source implementation on their website, including detailed documentation and deep technical dives. They will likely seek feedback from early adopters to refine the system’s robustness, especially in multi-user scenarios. Future updates may include optional features for conflict resolution or enhanced permission controls, but the core philosophy of simplicity and ownership will remain central. Monitoring user experiences will determine whether this approach can expand beyond small teams.
The Beginners Base Camp Guide For Businesses
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does the ‘disk is the contract’ approach handle multiple users editing the roadmap?
Currently, it relies on manual review and scoring to manage priorities, and does not support real-time conflict resolution. It is best suited for small teams or individual operators.
What are the main advantages of storing the roadmap as a JSON file?
Ownership, durability, interoperability, and simplicity. Any tool capable of reading or writing JSON can access and update the plan without vendor lock-in.
Are there any security concerns with this approach?
Yes, since updates are manual and there are no built-in permission controls, security depends on local file management and review processes.
Will this system support enterprise-scale collaboration?
It is unlikely in its current form, as it sacrifices features like concurrent editing and conflict management, which are essential for large, distributed teams.
Source: ThorstenMeyerAI.com
