📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark has announced a new roadmap methodology where the roadmap is a plain JSON file stored on disk, making it open, durable, and agent-friendly. This approach emphasizes local ownership and interoperability, moving away from SaaS API dependencies.
Threlmark has introduced a new approach to roadmapping called ‘disk is the contract,’ where the entire roadmap is a plain JSON file stored locally on a user’s disk, eliminating reliance on SaaS APIs or vendor-specific tools. This shift emphasizes ownership, durability, and interoperability, making the roadmap accessible to any program that reads JSON. This shift emphasizes ownership, durability, and interoperability, making the roadmap accessible to any program that reads JSON.
The core idea behind Threlmark’s approach is that the roadmap’s structure is a known, open format stored as a JSON file on the user’s disk. This file acts as the single source of truth, enabling any compatible tool or agent to read or write to it without needing special integrations, SDKs, or API permissions.
The system also incorporates a scored kanban board, where each task carries a priority score, enforcing clear trade-offs and reducing ambiguity in planning. The roadmap can be updated directly by human or automated agents, allowing real-time coordination and decision-making without vendor lock-in.
While this approach offers advantages in durability and interoperability, Threlmark acknowledges that it is less suited for large, multi-user teams requiring real-time collaboration, conflict resolution, or permission controls. The method is designed primarily for small teams or operators who value local control and simplicity.
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 Roadmapping
This approach shifts the control and durability of the roadmap from SaaS vendors to the user, reducing lock-in and ensuring long-term access. It also simplifies integration and automation, allowing tools and agents to interact directly with the roadmap file. However, it trades off some collaborative features typical of cloud-based tools, making it more suitable for small teams or individual operators who prioritize ownership and interoperability over real-time multi-user editing.JSON file editor for project roadmaps
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background and Rationale for Threlmark’s Approach
Traditional roadmap tools rely on SaaS platforms with APIs that can change, deprecate, or become inaccessible, risking data lock-in and loss. For more on the importance of open standards, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. Threlmark’s philosophy emphasizes that operational data, like roadmaps, should be owned and controlled directly by users. This idea builds on the concept that a plain file format, such as JSON, offers durability, simplicity, and broad compatibility.
The company has previously highlighted the limitations of SaaS tools, especially their dependency on vendor-specific APIs and the risks of data silos. This is similar to issues discussed in The referral. How AI search severs the content-for-traffic contract that funded the open web. The ‘disk is the contract’ approach is a formalization of this philosophy, aiming to make roadmaps more resilient and accessible over time.
“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 core of our product.”
— 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-Based Roadmap System
While the approach offers durability and interoperability, it is less suited for large, collaborative teams needing real-time editing, conflict resolution, or permission controls. Threlmark acknowledges that a JSON file on disk cannot easily support concurrent multi-user updates or audit trails at scale. Additionally, the quality of automation depends on proper scoring and guardrails, which are not inherently enforced by the system. It remains to be seen how well this approach scales beyond small teams or individual operators.
Kanban board software with JSON export
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Development
Threlmark plans to release the open-source implementation of the ‘disk is the contract’ system, allowing users to experiment with the approach. The company will also gather feedback from early adopters to refine tools for scoring, conflict management, and agent interactions. Future updates may include enhanced safeguards for agent writes and integrations with existing project management workflows. Wider adoption will depend on how well small teams and operators find the system balances simplicity with practical needs.
version control for JSON project files
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does ‘disk is the contract’ improve roadmap durability?
By storing the roadmap as a plain JSON file on disk, it remains accessible regardless of SaaS platform changes, ensuring long-term ownership and control.
Can this system support large, collaborative teams?
It is primarily designed for small teams or individual operators. Large teams requiring real-time collaboration may find this approach less suitable due to its limitations in concurrent editing and conflict resolution.
How do agents interact with the roadmap?
Agents can read and write to the JSON file directly, updating task statuses or scores without needing special APIs, enabling automated coordination.
What are the main trade-offs of this approach?
It sacrifices some collaborative features like real-time conflict management for increased durability, ownership, and interoperability.
Source: ThorstenMeyerAI.com
