📊 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 a JSON file stored locally, making it accessible, durable, and vendor-agnostic. This shifts the paradigm from SaaS APIs to file-based contracts, enabling better interoperability and control.
Threlmark has unveiled a new approach to managing project roadmaps, emphasizing that the roadmap is a plain JSON file stored directly on the user’s disk, rather than a cloud-based or API-driven tool. This approach is similar to the ideas discussed in Disk Is the Contract: Inside Threlmark’s Local-First Architecture. This shift aims to enhance interoperability, durability, and control over planning data, making it accessible to any tool capable of reading or writing JSON.
The core of Threlmark’s system is that the entire roadmap exists as a structured JSON file on local storage. This file acts as the definitive contract for the plan, allowing any compatible program or agent to read or modify it without dependency on SaaS APIs or proprietary formats. The approach promotes open standards and reduces vendor lock-in, ensuring the plan remains accessible and durable over time. Additionally, Threlmark integrates a scored kanban system where each task carries a priority score, enabling clear prioritization and trade-offs. This scoring enforces discipline by making priorities explicit, and the entire setup supports automation, as agents can read, update, and write back to the roadmap file directly, closing the loop between planning and execution. The design is intended for small teams or operators, emphasizing local-first architecture and provider-agnostic interoperability.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 approach matters because it shifts control of planning data from vendor-controlled SaaS platforms to the user’s own infrastructure. By using a plain JSON file as the contract, teams gain full ownership, reduce dependency on external services, and improve long-term durability of their plans. It also enables seamless automation and integration with any tool that can handle JSON, fostering interoperability and reducing lock-in risks.
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 APIs, which can introduce vendor lock-in, API deprecation, and dependency risks. For more on how AI search is changing content access, see The referral. How AI search severs the content-for-traffic contract that funded the open web. Threlmark’s philosophy centers on simplicity and durability, advocating for a local-first, open format approach. The company previously emphasized the importance of having control over operational data, and this new system extends that philosophy to roadmaps, making the plan a portable, interoperable artifact.
“A roadmap is only useful if everyone agrees on where it lives. Our approach makes the plan a simple file on disk, accessible to any tool that understands JSON.”
— Thorsten Meyer, Threlmark founder
local-first roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations of File-Based Roadmap Systems
It is not yet clear how well this system scales for large, collaborative teams requiring real-time concurrent editing, conflict resolution, or permission management. For insights into licensing and contracts related to data feeds, see Raw-feed licensing. The contract that doesn’t exist yet. The approach is designed for small teams or operators, and handling multiple simultaneous users may require additional safeguards or tools. Moreover, the reliability of automated agents writing to the file depends on guardrails and review processes, which are still being developed and tested.
S&O Project Management Planner – Work Organizer Daybook– Assignment Schedule Notebook – Task Manager – Activity Notebooks for Work – Project Management Journal- 200 Pages, 8.25" x 9.3”
Essential to High Productivity — Take your efficiency to the next level with this work notebook organizer planner….
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Integration Testing
Threlmark plans to release the full open-source system, along with documentation and best practices for integration. Early adopters are expected to test the approach in small team environments, providing feedback on scalability and conflict management. Future updates may include tools for multi-user collaboration and enhanced version control, but the core remains a simple, file-based contract.
Personal Kanban: Mapping Work | Navigating Life
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does this approach handle multiple users editing the roadmap?
Currently, the system is optimized for small teams or operators. Handling multiple simultaneous edits requires additional conflict resolution mechanisms, which are not yet part of the core design.
Can existing project management tools integrate with this JSON-based roadmap?
Yes. Any tool capable of reading and writing JSON files can integrate, making it highly interoperable with custom or existing tools.
What are the main advantages over SaaS roadmap tools?
Ownership of data, durability beyond vendor platforms, no dependency on APIs, and ease of automation and integration.
Are there any risks or downsides to this approach?
Yes. It lacks real-time collaboration features, and automated writing can introduce errors if not carefully managed. It is best suited for small-scale use cases.
Source: ThorstenMeyerAI.com
