📊 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 system based on the principle ‘disk is the contract,’ where the entire plan is stored as a JSON file on local disk. This approach emphasizes simplicity, durability, and interoperability, avoiding SaaS lock-in. The system is designed for small teams and operators, with potential limitations for large, collaborative environments.
Threlmark has introduced a new project management system based on the principle that ‘disk is the contract,’ where the entire roadmap is stored as a plain JSON file on the user’s local disk. This approach aims to eliminate vendor lock-in and improve interoperability by making the plan accessible to any tool capable of reading or writing JSON, without relying on SaaS APIs or proprietary formats.
The core innovation from Threlmark is that the roadmap exists as a simple, structured JSON file on the user’s disk, which can be read and modified by any compatible program or agent. This contrasts with traditional SaaS-based tools that store data in proprietary cloud environments, often leading to vendor lock-in and limited interoperability.
The system also incorporates a scored kanban board, where each task is prioritized with a score, enabling clear visibility of priorities and encouraging deliberate trade-offs. This scoring system is integrated into the same JSON file, allowing seamless updates by both humans and automated agents.
Threlmark emphasizes that this approach is local-first and provider-agnostic, meaning it requires no special SDKs, webhooks, or API integrations. The entire setup is designed for small teams or individual operators, with the understanding that it may not suit large-scale, real-time collaborative projects due to the limitations of file-based concurrency and conflict resolution.
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 Small Teams and Project Durability
This development is significant because it challenges the prevailing SaaS-centric model of project management tools, offering a more durable and open alternative. By owning the roadmap as a local file, users avoid risks associated with vendor deprecation, pricing changes, or service outages. It also simplifies integration with other tools that can read or write JSON, fostering interoperability and reducing lock-in.
For small teams and operators, this approach offers a straightforward, reliable way to manage and automate their planning processes. However, it may not fully replace SaaS tools for large organizations requiring real-time collaboration, conflict resolution, and permission management.
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 Roadmap Management and Threlmark’s Approach
Traditional project management tools often rely on cloud-based SaaS platforms with proprietary data formats and APIs, which can lead to vendor lock-in and limited interoperability. Threlmark’s approach builds on the idea that operational data, like roadmaps, should be owned and controlled by users, not vendors.
The concept of storing the roadmap as a plain JSON file aligns with broader local-first and open data principles, emphasizing durability and simplicity. Threlmark’s decision to make the entire product revolve around a single, shared file is a deliberate move to reduce complexity and ensure long-term access to project plans.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. Threlmark makes a deliberately different bet: the roadmap is a plain JSON file sitting on your own disk.”
— Thorsten Meyer, Threlmark
local disk 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 durability and interoperability, it is not suited for large, collaborative environments requiring real-time editing, conflict resolution, or permission controls. The risk of data corruption or mis-writes by automated agents also exists without proper safeguards. Details about how to manage concurrency and review updates are still emerging, and the system’s suitability for enterprise-scale projects remains untested. For more on Threlmark’s architecture, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture.
interoperable task management app
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Expected Adoption and Future Developments
Threlmark plans to release more detailed documentation and tools to support small teams adopting this approach. Future updates may include enhanced guardrails for agent interactions and integrations with existing project management workflows. Broader community feedback and case studies will help determine the scalability and practicality of this model for various organizational sizes.
Ampad Gold Fibre Designer, Project Planner,Size 9-1/2 x 7-1/4, Asst Covers, 84 Sheets per Notebook (20-817),White
Confidently track and manage large jobs with ease
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Can this system support large, distributed teams?
Currently, the system is designed for small teams or individual operators. Large, distributed teams may face challenges with concurrent editing and conflict resolution, which are not the focus of this approach.
How does it handle conflicts or simultaneous updates?
The system relies on the file being the single source of truth, so proper review processes are recommended. Automated conflict detection and resolution are not yet built-in, requiring manual oversight for critical updates.
Is the roadmap format open and extendable?
Yes, the JSON format is open source under MIT license, allowing users to adapt or extend the structure as needed.
What are the security implications of using a local file?
Since the roadmap is stored locally, security depends on local access controls. It avoids cloud-based vulnerabilities but requires users to manage file security appropriately.
Source: ThorstenMeyerAI.com
