📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark has unveiled a new roadmap system based on storing the plan as a JSON file on local disk, emphasizing simplicity, interoperability, and ownership. This change shifts how teams and agents coordinate on projects.
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 the roadmap the definitive contract. This development emphasizes ownership, interoperability, and durability, diverging from conventional SaaS-based tools.
The core innovation is that the roadmap is a JSON file sitting on the user’s computer, not hosted or managed through a SaaS API. This file serves as the single source of truth, with its structure being the integration contract. Any program capable of reading or writing JSON can interact with it, eliminating the need for SDKs, webhooks, or authentication systems. The roadmap is also scored, with each item assigned a priority, facilitating clear prioritization and trade-offs. Because the file is local and plain, it remains accessible and durable beyond any specific tool or vendor, reducing lock-in risks. The system supports automated agents that can read and update the file, enabling seamless collaboration between humans and AI agents. However, the approach is designed for small teams or operators, as it does not support real-time multi-user editing or conflict resolution at scale. The simplicity comes with trade-offs, including potential risks of file corruption or mis-scoring, and the need for careful management of agent permissions.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 Management and Tool Interoperability
This shift to a disk-based roadmap fundamentally changes how teams manage project plans, emphasizing ownership and interoperability. It reduces dependence on vendor-specific SaaS solutions, allowing users to maintain control over their data and integrate with any JSON-compatible tool. For small teams and operators, this approach offers a lightweight, durable, and flexible alternative, potentially increasing resilience and reducing lock-in. However, it also introduces challenges in collaboration and conflict management, which are not addressed by this simple model.
JSON file project management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background on Roadmap Tools and Data Ownership
Traditional project management tools rely heavily on SaaS platforms, with features like real-time collaboration, conflict resolution, and permissioning built into their APIs. While these features support large, distributed teams, they can also create lock-in and dependency on specific vendors. The concept of storing the roadmap as a plain JSON file on disk is a response to these limitations, emphasizing data ownership and long-term durability. Threlmark’s approach aligns with a broader movement toward local-first, provider-agnostic data management, aiming to give users more control over their operational artifacts.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. That’s why we made ‘disk is the contract’ the whole product.”
— Thorsten Meyer, Threlmark founder
local disk roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Risks of the Disk-Based Approach
It is not yet clear how well this approach scales for larger teams or organizations requiring real-time collaboration. The system does not inherently support concurrent multi-user editing, conflict resolution, or permission management at scale. There is also a risk of file corruption or mis-scoring by agents, which requires careful management and guardrails. The long-term stability of this system depends on how users handle these challenges.
version control for project plans
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Integration Testing
Threlmark plans to release the full open-source implementation and documentation, encouraging small teams and operators to adopt and test the system. Future developments may include tools for conflict management and enhanced collaboration features, but the core remains a simple, local-first JSON file. Monitoring user feedback will shape subsequent iterations, especially regarding scaling and multi-user support.
agent automation 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 collaboration among multiple team members?
Currently, the system is designed for small teams or operators. It does not support real-time multi-user editing or conflict resolution, so collaboration relies on manual coordination and careful management of the JSON file.
What are the main advantages of using a JSON file on disk for roadmaps?
This approach offers ownership, durability, and interoperability. The roadmap is not tied to a vendor or SaaS platform, making it accessible and long-lasting, with any JSON-compatible tool able to read or update it.
What risks are associated with this system?
Risks include potential file corruption, mis-scoring by agents, and limited support for large-scale, real-time collaboration. Proper management and guardrails are necessary to mitigate these issues.
Is this system suitable for enterprise-level project management?
No, it is primarily designed for small teams or individual operators. Large organizations requiring advanced collaboration features may find this approach insufficient.
Source: ThorstenMeyerAI.com
