📊 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 approach to roadmaps, where the plan is stored as a plain JSON file on disk, making it open, durable, and agent-friendly. This shifts control from SaaS tools to local, file-based management.
Threlmark has introduced a new approach to managing project roadmaps, where the entire plan is stored as a plain JSON file on the user’s local disk, rather than within a SaaS platform. This approach is similar to concepts discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. This design emphasizes ownership, interoperability, and durability, marking a significant departure from conventional cloud-based tools.
The core idea behind Threlmark’s ‘disk is the contract’ model is that the roadmap exists as a simple, structured JSON file on the user’s machine. The roadmap’s structure is the integration point, allowing any program capable of reading or writing JSON to access or modify it. This approach eliminates dependencies on SaaS APIs, reducing lock-in and increasing control over project data. The system also features a scored kanban board, where items are prioritized through a numerical score, facilitating clearer trade-offs and decision-making. Furthermore, because the roadmap is a file, it can be read and updated by human users or automated agents without needing special SDKs or webhooks. This makes it a shared workspace for both people and AI agents, enabling seamless, real-time collaboration. However, this simplicity comes with trade-offs: it is less suited for large teams requiring concurrent editing, conflict resolution, or permission controls. The approach is designed primarily for small teams or individual operators who prioritize local control and interoperability over enterprise-scale features. Threlmark emphasizes that this model is open source under the MIT license, allowing anyone to adopt or adapt it freely.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 Local-First Roadmaps Change Project Management
This development matters because it shifts control of project data from vendor-hosted SaaS tools to the user’s own environment, reducing lock-in and increasing resilience. By making roadmaps plain files, teams can ensure their project plans outlive any specific tool or platform, fostering greater independence and flexibility. Additionally, the scored, agent-readable format enables more automated workflows and transparent decision-making. However, it also means sacrificing some enterprise features like real-time collaboration and conflict management, making it more suitable for small, autonomous teams.
JSON project management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background of Roadmap Management and Open Data Movement
Traditional project management tools rely heavily on SaaS platforms, which centralize data and often lock users into specific vendors. This trend is explored in The referral. How AI search severs the content-for-traffic contract that funded the open web. This has led to concerns about data portability, vendor lock-in, and long-term durability of project plans. Threlmark’s approach builds on the open data movement, advocating for simple, interoperable formats like JSON that any tool can handle. The concept of local-first, provider-agnostic data management has gained traction among developers and operators seeking more control and resilience. Threlmark’s announcement positions itself within this trend, emphasizing simplicity and durability over feature-rich SaaS solutions.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. Threlmark’s approach makes the roadmap a plain file on disk, ensuring ownership and interoperability.”
— Thorsten Meyer, Threlmark founder
local file-based roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Risks of File-Based Roadmaps
While the approach offers many benefits, it is not suited for large-scale, multi-user environments requiring real-time collaboration, conflict resolution, or permission controls. There is also a risk that poorly scored items can lead to misprioritized plans, and automated agents with write access could potentially corrupt the roadmap if not properly managed. The system relies heavily on disciplined scoring and guardrails to prevent errors. Details about how conflicts are handled or how to secure the file in collaborative settings remain unclear at this stage. For more on managing data and licensing, see Raw-feed licensing. The contract that doesn’t exist yet.
Kanban board with scoring
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Community Feedback
Threlmark plans to open-source the full implementation and documentation, inviting developers and small teams to experiment with the model. Future updates may include tools for versioning, conflict management, and integration with existing workflows. The company also intends to gather user feedback to refine the approach and potentially develop complementary tools that mitigate current limitations for larger teams or enterprise use.
open source project planning software
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?
It shifts ownership from cloud platforms to local files, emphasizing control, durability, and interoperability over real-time collaboration features.
Is this system suitable for large teams or enterprise projects?
No, it is primarily designed for small teams or individual operators who prioritize local control and simple workflows. Large-scale collaboration features are limited.
What are the main risks of using a file-based roadmap?
Risks include potential data corruption from automated agents, difficulty managing concurrent edits, and reliance on disciplined scoring to avoid misprioritization.
Can I integrate this with existing project management tools?
Yes, since the roadmap is a JSON file, any tool capable of reading or writing JSON can potentially integrate, but it requires custom setup and does not support real-time sync out of the box.
Source: ThorstenMeyerAI.com
