📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark announced a new roadmap approach: the plan is a plain JSON file on disk, making it simple, durable, and vendor-agnostic. This shifts how teams and agents coordinate work, emphasizing local control and interoperability.
Threlmark has introduced a new approach to project roadmaps, asserting that „disk is the contract“—the entire roadmap is a plain JSON file stored locally on a user’s disk, replacing conventional SaaS tools with a simple, interoperable format. You can learn more in Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
The core idea is that the roadmap exists as a structured JSON file, which can be read and written by any program capable of handling JSON. This design eliminates dependencies on vendor-specific APIs, SDKs, or webhooks, promoting durability and long-term access to planning data.
The product includes a scored kanban board, where each item has a priority score, enabling clear prioritization and trade-offs. The roadmap acts as a shared workspace for both humans and automated agents, which can directly modify the JSON file, closing the loop between planning and execution without intermediary systems.
Threlmark emphasizes local-first architecture and provider-agnostic interoperability, meaning the plan file can be owned and managed by small teams or individual operators without vendor lock-in. However, this approach acknowledges limitations in real-time multi-user collaboration and conflict resolution, which are not suited for large, distributed teams.
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 for Project Management and Automation
This development offers a fundamentally different way to manage project roadmaps, emphasizing ownership, durability, and interoperability. By using a plain JSON file as the contract, teams can avoid vendor lock-in, ensure long-term access to their plans, and facilitate automation through agents that read and write directly to the plan.
While this simplifies technical integration and enhances control, it also shifts the responsibility for conflict resolution and multi-user editing to the team, making it less suitable for large, distributed organizations. The approach is particularly relevant for small teams and operators seeking a lightweight, resilient planning tool.
JSON file editor for project management
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The Shift Toward Local-First, Open Data Roadmaps
Traditional roadmap tools rely heavily on SaaS platforms, offering features like real-time collaboration, conflict resolution, and permission management, but often at the cost of vendor lock-in and dependency on proprietary APIs. For a broader discussion on open data principles, see The referral. How AI search severs the content-for-traffic contract that funded the open web..
Threlmark’s approach revisits the fundamental idea of operational data as a simple, accessible artifact—namely, a JSON file stored locally—drawing on principles of open data, durability, and interoperability. This concept aligns with broader trends toward local-first tools and open formats, aiming to give users more control over their planning data.
Previous developments in project management emphasized cloud-based solutions, but Threlmark’s model challenges that paradigm by prioritizing ownership and longevity of the data itself.
„A roadmap is only useful if everyone agrees on where it lives. Our approach makes the plan a simple file on disk, ensuring durability and interoperability.“
— Thorsten Meyer, Threlmark founder
local-first project roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations of Disk-Based Roadmaps for Large Teams
It remains unclear how well this model scales for large, distributed teams requiring real-time collaboration, conflict resolution, and permission management. The approach is optimized for small teams or individual operators, but its effectiveness in complex, multi-user environments is still to be tested. For related insights, see Raw-feed licensing. The contract that doesn’t exist yet..
Additionally, the risks associated with agent-written updates—such as potential corruption or conflicts—require guardrails and review processes, which are not yet specified.
vendor-agnostic JSON project planner
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Expected Adoption and Development of Guardrails
Threlmark is likely to focus on refining tools for local editing, conflict management, and review workflows, especially for small teams. Future updates may include features to support multi-user editing or integrations that preserve data integrity without sacrificing the core simplicity.
Further community feedback and real-world testing will shape how this approach evolves, particularly regarding automation and collaborative workflows.
Kanban board with JSON integration
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 project management?
It simplifies data ownership, enhances durability, and promotes interoperability by making the roadmap a plain, accessible JSON file that any compatible tool can read or modify.
What are the main limitations of this approach?
It is less suited for large teams requiring real-time collaboration, conflict resolution, or permission controls. Managing concurrent edits and preventing data corruption requires additional guardrails.
Can this system integrate with existing project tools?
Yes, since the core format is JSON, any tool capable of reading and writing JSON can potentially integrate, making it highly flexible and vendor-agnostic.
Is this approach suitable for enterprise-scale project management?
Currently, it is best suited for small teams or individual operators. Large, enterprise environments may find the limitations in multi-user collaboration and conflict management prohibitive.
Source: ThorstenMeyerAI.com