📊 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, interoperability, and durability, diverging from traditional SaaS tools.
Threlmark has introduced a new project management paradigm where the roadmap is a plain JSON file stored on the user’s disk, making it the definitive contract for project planning and execution.
The core innovation from Threlmark is the principle ‘disk is the contract,’ meaning the entire roadmap resides as a structured JSON file on the user’s local disk. This file acts as the single source of truth, accessible by any program capable of reading or writing JSON, eliminating reliance on SaaS APIs or vendor-specific tools. The approach ensures the roadmap’s durability and ownership, as it remains independent of any vendor or cloud service. Threlmark’s system includes a scored kanban board, where each task carries a priority score, facilitating clear prioritization and trade-offs. The board is a view over the JSON file, which can be directly manipulated by humans or automated agents, enabling a live, shared workspace. This setup is designed for small teams or operators who value simplicity, local control, and interoperability. However, it is acknowledged that this approach is less suited for large, collaborative, real-time environments where conflict resolution and permissioning are critical.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 Project Planning
This approach emphasizes ownership, durability, and interoperability, reducing dependency on proprietary SaaS tools that can change or disappear. It offers a straightforward, future-proof way to manage roadmaps, especially for small teams or individual operators, by ensuring the plan exists as a portable, editable file. However, it sacrifices some features like real-time collaboration and conflict management, which are typical in enterprise tools. This shift could influence how small teams and independent operators approach project management, favoring simplicity and control over advanced collaboration features.
JSON file project management tool
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background and Rationale Behind Threlmark’s Approach
Traditional roadmap tools rely heavily on SaaS platforms with APIs, which can introduce vendor lock-in, deprecation, and access issues. Threlmark’s philosophy challenges this by making the roadmap a simple, structured file that any compatible tool can access, modify, or read. The concept builds on the idea that operational data should outlive the tools that create it, providing long-term ownership and interoperability. The company highlights that this approach is particularly suited for small teams or individual operators who prioritize simplicity and control over complex, multi-user, real-time features.
“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. Our approach makes the roadmap a plain JSON file on your disk, ensuring ownership and durability.”
— Threlmark spokesperson
local disk project roadmap software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limitations and Risks of the ‘Disk as Contract’ Model
It is not yet clear how well this approach scales for large, distributed teams requiring real-time collaboration, conflict resolution, or permission controls. There are also concerns about the potential for agent mis-writing or corrupting the plan, which necessitates guardrails and review processes. Additionally, the effectiveness of scoring and prioritization depends on proper setup, which may be challenging for some users. The approach is primarily designed for small teams or operators, and its suitability for enterprise environments remains uncertain.
Kanban board with JSON integration
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 detailed documentation and tooling to facilitate adoption of the ‘disk is the contract’ system. Future updates may include safeguards for agent writes, enhanced version control, and integrations with existing project management workflows. The company is also inviting feedback from early adopters to refine the approach and explore how it can be adapted for larger, more collaborative environments.
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 this approach handle multiple users editing the roadmap?
Currently, the system is best suited for small teams or individual operators. Handling concurrent edits at scale requires additional conflict resolution and permission controls, which are not built into the core model but may be considered for future development.
Can existing project management tools integrate with this JSON-based roadmap?
Yes, any tool capable of reading and writing JSON can potentially integrate, making the system highly interoperable. However, custom integrations may be needed to match specific workflows.
What are the security implications of storing the roadmap as a local file?
Storing the roadmap locally gives control over access, but also places responsibility on the user to secure the file. It is less suitable for environments requiring strict permissioning or audit trails.
Is this approach suitable for large, enterprise-scale projects?
Not currently. The model favors small teams or individual operators. Large-scale, real-time collaboration with conflict management would require additional features not yet implemented.
Source: ThorstenMeyerAI.com
