📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark unveils a new roadmap approach where the plan is a JSON file stored locally, making it accessible, editable, and durable without vendor lock-in. This shifts how teams and agents coordinate on projects.
Threlmark has introduced a new approach to project roadmaps called ‘disk is the contract,’ where the entire plan exists as a plain JSON file stored locally on a user’s disk, eliminating reliance on SaaS APIs or vendor-specific tools. This innovation aims to enhance interoperability, durability, and control for small teams and operators.
The core idea is that the roadmap is a simple JSON file, which any program that can read or write JSON can access. The file’s structure acts as the contract, enabling seamless integration with various tools and agents without needing SDKs or webhooks. The approach is open source under MIT license, available at threlmark.com, and designed for local-first, provider-agnostic operation. Threlmark’s system also incorporates scoring of tasks, allowing prioritized planning. The scored items are reflected visually on a kanban board, which is just a view over the JSON file. This setup supports a live, shared workspace where humans and automated agents can read, update, and write back to the roadmap, creating a continuous loop of planning and execution. However, the model is not suited for large, collaborative, real-time editing environments. It emphasizes simplicity and durability over features like conflict resolution, permissioning, or audit trails at scale. The approach requires careful management of agent permissions and scoring accuracy to prevent misalignment or corruption of plans.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.
Why ‘Disk Is the Contract’ Changes Project Management
This new model shifts the control and longevity of project plans away from vendor SaaS tools towards user-owned files, reducing lock-in and increasing resilience. It enables teams to maintain their roadmap independently, ensuring access and control over the plan long-term, even if vendors change or shut down. For small teams and operators, this approach simplifies integration and automates workflows without complex technical overhead. However, it also introduces limitations in real-time collaboration and requires careful management of scoring and write permissions, making it more suitable for smaller, more controlled environments.
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.
Background of Roadmap Tools and the ‘Disk’ Approach
Traditional project management tools rely on SaaS platforms with APIs, SDKs, and real-time collaboration features. While these tools offer convenience and scale, they often create vendor lock-in and pose risks if the service is discontinued or changes pricing. Threlmark’s approach challenges this paradigm by proposing that the roadmap itself is a simple, structured file on disk, which any compatible program can access. This concept aligns with local-first principles and emphasizes interoperability, durability, and user ownership. The idea draws from broader trends favoring open standards and minimal dependencies, especially for small teams or individual operators.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives.”
— Thorsten Meyer, Threlmark
Limitations and Risks of the ‘Disk Is the Contract’ Model
It is not yet clear how well this approach scales for larger teams requiring real-time collaboration, conflict resolution, or permission management. The reliance on a single JSON file on disk may pose challenges in multi-user environments, especially across different locations or time zones. Additionally, the effectiveness of scoring and the risk of accidental corruption depend heavily on careful management and review, which could limit its suitability for complex projects or enterprise settings. Further development and real-world testing are needed to fully understand these limitations.
Next Steps for Adoption and Testing of the Approach
Threlmark plans to release the open-source implementation and documentation on their website, encouraging small teams and operators to experiment with the model. Future updates may include tools for version control, conflict resolution, and enhanced permission management, aimed at broadening applicability. Community feedback and case studies will be critical to refine the approach and assess its practicality in diverse project environments. Meanwhile, users are advised to consider the model’s limitations before adopting it for large-scale or highly collaborative projects.
Key Questions
How does the ‘disk is the contract’ approach differ from traditional project management tools?
It replaces SaaS-based tools with a simple, structured JSON file stored locally, enabling direct read/write access by any compatible program, thus reducing vendor lock-in and increasing control.
What are the main advantages of this approach?
It offers durability, interoperability, simplicity, and ownership of the roadmap, making it accessible and easy to integrate with automated agents and other tools.
What limitations should users be aware of?
It is less suitable for large, collaborative, real-time editing environments and requires careful management of scoring and permissions to prevent data corruption.
Is this approach suitable for enterprise project management?
Currently, it is more suited for small teams or individual operators. Its scalability and conflict management features are limited compared to traditional SaaS tools.
Source: ThorstenMeyerAI.com
