📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark announces a radical shift in roadmap management with ‘disk is the contract,’ making project plans simple, open, and owner-controlled via plain JSON files. This approach emphasizes interoperability and durability but trades off some collaborative features.
Threlmark has introduced a new approach to project roadmapping, where the entire plan is stored as a plain JSON file on the user’s disk, making the file the definitive contract for project data. This shift aims to enhance interoperability, durability, and ownership of project plans, moving away from SaaS-based tools.
Threlmark’s new product, described as ‘disk is the contract,’ centers on storing the project roadmap as a simple, structured JSON file on the user’s local disk. This file serves as the single source of truth, enabling any program capable of reading or writing JSON to interact with the roadmap without needing APIs or vendor-specific SDKs. The approach emphasizes local control, open standards, and long-term access, reducing dependence on SaaS vendors that may change or deprecate their services. The product also features a scored kanban system, where each task carries a priority score, facilitating clear prioritization and trade-offs. Because the roadmap is a shared file, it can be directly manipulated by human operators or automated agents, creating a live, collaborative workspace that integrates decision-making and execution seamlessly. This model is designed primarily for small teams or operators managing their own data, not large-scale enterprise environments requiring real-time multi-user editing or conflict resolution.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 Roadmap Management
This approach matters because it fundamentally shifts control over project data from SaaS vendors to users, ensuring long-term access and interoperability. By using a plain JSON file as the contract, teams can avoid vendor lock-in, simplify integrations, and improve data durability. It also introduces a new operational paradigm where automation and human input share a common, transparent data structure, potentially reducing complexity and increasing flexibility in project workflows.
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 Threlmark’s Roadmap Philosophy
Traditional project management tools rely heavily on SaaS platforms with proprietary APIs, which can pose risks of vendor lock-in, deprecation, or service discontinuation. Threlmark’s philosophy has long emphasized open standards and local control, but this latest move formalizes that stance by making the roadmap a simple, shareable file. The concept aligns with broader trends toward local-first, provider-agnostic data management, and is a response to frustrations with SaaS dependencies.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. ‘Disk is the contract’ makes that explicit and simple.”
— Thorsten Meyer, Threlmark
local disk roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Risks of a File-Based Roadmap System
It is not yet clear how well this system scales for large teams or complex projects requiring concurrent editing and conflict resolution. The approach is tailored for small teams or operators managing their own data, and may face challenges in multi-user environments. Additionally, the risk of mis-writes or corruption by automated agents requires careful management, and tools for conflict detection or versioning are not part of the core design.
Project Planner Notepad – Project Management Organizer Desk Pad – Manage Project Tasks and Meeting Deadlines Effectively – 50 Sheets of Premium 120gsm Paper | Management | A4 Mono
Comprehensive Project Planning: Plan for success with a dedicated project timeline and task sections to track milestones and…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Integration
Threlmark plans to release the full open-source implementation and detailed documentation, enabling users to experiment with the approach. Future developments may include enhanced guardrails for agent writes, version control features, and integrations with existing project management workflows. The company also intends to gather user feedback to refine the system’s usability and robustness.
version control JSON project files
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does this approach compare to traditional SaaS roadmap tools?
Unlike SaaS tools that store data on external servers and rely on APIs, Threlmark’s approach keeps the roadmap as a local, plain JSON file. This provides greater control, durability, and interoperability, but may lack some collaborative features of cloud-based solutions.
Can multiple people edit the roadmap simultaneously?
Not easily. The file-based system is designed for small teams or individual operators. For multi-user editing, additional conflict resolution or version control mechanisms would be necessary, which are not part of the current system.
What are the security implications of storing the roadmap locally?
Storing the roadmap as a local file means security depends on the user’s environment. It reduces exposure to cloud-based breaches but requires proper access controls on the local machine.
Is this system suitable for large enterprise projects?
Currently, the system is best suited for small teams or individual operators. Large enterprises may find the lack of real-time collaboration and conflict management limiting.
Source: ThorstenMeyerAI.com
