📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark announces a novel approach to roadmapping: the roadmap is a plain JSON file stored locally, making it open, durable, and agent-friendly. This shifts control from SaaS tools to users’ own files.
Threlmark has launched a new approach to roadmapping, where the entire plan resides as a plain JSON file on the user’s disk, making it accessible, durable, and open for integration without relying on SaaS APIs.
The core innovation from Threlmark is that the roadmap is a simple JSON file stored locally, which acts as the contract for all tools and agents interacting with the plan. This approach eliminates dependency on proprietary SaaS APIs, enabling any program capable of reading or writing JSON to access and modify the roadmap. The design prioritizes interoperability, durability, and user ownership, with the roadmap serving as a shared, version-controlled artifact. The system also includes a scored kanban board where each item is prioritized by a score, facilitating clear decision-making and trade-offs. This setup allows both humans and automated agents to read and update the plan directly via file operations, creating a live, collaborative workspace.Threlmark emphasizes that this method is well-suited for small teams or operators who prefer local control over their planning data, acknowledging that it does not support multi-user real-time editing or large-scale permission management typical of SaaS tools. The open-source project is available under MIT license at threlmark.com, with detailed documentation explaining its internals and usage.
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 ‘Disk Is the Contract’ for Roadmapping
This approach fundamentally shifts control over planning data from SaaS vendors to users, ensuring long-term access, interoperability, and reduced lock-in. It enables automated agents to participate directly in plan updates, streamlining workflows for small teams and operators. However, it also introduces limitations in real-time collaboration and conflict resolution, making it suitable primarily for smaller-scale use cases. For organizations seeking open, durable, and flexible planning tools, this model offers a compelling alternative to traditional SaaS solutions, emphasizing ownership and simplicity.JSON file editor for project planning
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background and Evolution of Roadmapping Tools
Traditional roadmapping tools are often SaaS-based, offering real-time collaboration, permissioning, and conflict management. While effective for large teams, these solutions can lead to vendor lock-in, limited data ownership, and dependency on proprietary APIs. Threlmark’s approach challenges this paradigm by proposing a local, file-based method rooted in open standards. The concept aligns with broader movements toward local-first, open data, and interoperability in software design. The idea of using plain files for operational data has gained traction in recent years, especially among small teams and operators seeking control over their data without relying on cloud services.“A roadmap that lives inside your disk and is just a JSON file fundamentally changes how you control and integrate planning data. It’s about ownership, durability, and simplicity.”
— Thorsten Meyer, Threlmark founder
local JSON roadmap management tool
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Risks of the ‘Disk Is the Contract’ Model
It is not yet clear how well this approach scales for larger teams or complex projects requiring real-time collaboration, conflict resolution, or permission controls. The system’s reliance on file-based updates may introduce risks of data corruption or inconsistency if multiple agents or users modify the file simultaneously without guardrails. Additionally, the effectiveness of scoring and prioritization depends heavily on how accurately scores are set, which could lead to suboptimal planning if misused. The approach is primarily designed for small teams or operators and may not suit enterprise-level needs requiring robust collaboration features.
version control software for JSON files
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Development of the Approach
Threlmark is expected to release detailed documentation, including best practices for managing and safeguarding the JSON roadmap file. The community may begin experimenting with integrations, testing the approach in real-world scenarios. Future updates could include tools for conflict detection or multi-user editing, addressing current limitations. Monitoring how small teams adopt this model will inform potential enhancements and broader applicability. Threlmark also plans to engage with open-source contributors to expand the ecosystem of tools that can work with the JSON contract.
Kanban board software with JSON export
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 roadmapping tools?
Unlike SaaS tools that store data on proprietary servers, Threlmark’s method keeps the roadmap as a local JSON file, giving users ownership, durability, and interoperability without vendor lock-in.
Can multiple people edit the roadmap simultaneously?
Not easily. The file-based approach is best suited for small teams or operators; it does not inherently support real-time collaboration or conflict resolution, which are typical features of SaaS tools.
What are the security implications of using a local JSON file?
Security depends on how the file is managed. Since it’s stored locally, users retain control over access, but they must implement safeguards against accidental corruption or unauthorized modification.
Is this approach suitable for enterprise or large-scale projects?
Currently, it is primarily designed for small teams or operators. Large organizations needing advanced collaboration, permissioning, and audit trails may find the method limited without further development.
Source: ThorstenMeyerAI.com
