📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

Threlmark has unveiled a new approach to project roadmaps, where the entire plan is stored as a plain JSON file on the user’s local disk, eliminating reliance on SaaS APIs and vendor lock-in. This shift emphasizes ownership, interoperability, and durability, making the roadmap accessible and modifiable by any compatible tool or agent.

The core idea behind Threlmark’s approach is that the roadmap exists as a structured JSON file on the user’s machine, which can be read and written by any program capable of handling JSON. This contrasts with conventional SaaS-based tools that store data in proprietary cloud services, often limiting control and flexibility.

The system uses a scored kanban board where each item carries a priority score, ensuring clear prioritization and facilitating decision-making through visible trade-offs. The board is simply a view over the JSON file, allowing seamless integration with existing tools and automation agents.

Threlmark emphasizes that this model is local-first and provider-agnostic, meaning it does not depend on any specific cloud service or API, reducing lock-in risks and future-proofing the roadmap data. However, it also acknowledges limitations, such as challenges with concurrent multi-user editing and conflict resolution, which are not addressed by this approach.

Implications for Project Management Ownership

This approach shifts control of project data back to users, reducing dependence on vendor-specific SaaS tools that may change pricing, deprecate features, or disappear. By owning the roadmap as a simple file, teams gain durability, interoperability, and flexibility, which are critical for long-term project continuity and automation.

For small teams and operators, this model offers a straightforward, transparent way to manage priorities and automate workflows. It also encourages a more disciplined decision process by forcing explicit prioritization through scoring, making trade-offs more visible and manageable.

Python in Action: 60 Mini Projects to Automate Everything (Part 1): Practical CLI Tools, File Automation, and Data Cleaning with CSV, Excel, and JSON

AmazonView Latest Price

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Traditional Roadmap Tools and the Case for Simplicity

Most existing project management tools rely on cloud-based SaaS platforms with APIs, SDKs, and real-time collaboration features. While these tools excel at multi-user collaboration and conflict resolution, they often introduce vendor lock-in, data silos, and dependency on external infrastructure.

Threlmark’s philosophy challenges this paradigm by proposing a simple, open format—JSON—that any tool can access, modify, and persist locally. This aligns with a broader movement toward local-first, open standards for operational data, emphasizing durability and interoperability over real-time collaboration features.

“A roadmap is only useful if everyone agrees on where it lives. Our approach makes the roadmap a simple file on your disk, accessible by any tool that can handle JSON.”

— Thorsten Meyer, Threlmark founder

Limitations and Risks of the ‘Disk Is the Contract’ Model

It is not yet clear how well this approach will scale for large, multi-user teams requiring real-time collaboration and conflict management. The system does not inherently support concurrent editing or permissioning, which could pose challenges in collaborative environments.

Additionally, the reliance on scoring for prioritization depends heavily on the quality of the scoring process, which remains an external, manual step. There is also a risk that mis-writes by automation agents could corrupt the plan if not properly managed.

Upcoming Developments and Adoption Pathways

Threlmark plans to release the open-source implementation and documentation, encouraging developers and teams to experiment with the system. Future updates may include tools for better conflict resolution, multi-user editing, and enhanced validation of agent writes.

Adoption will likely depend on how well small teams and operators find the approach suits their workflows, and whether the limitations in multi-user scenarios can be addressed through supplementary tools or best practices.

Key Questions

How does ‘disk is the contract’ improve project management?

It gives teams full ownership of their roadmap data, ensures durability beyond any single tool, and allows seamless interoperability with any JSON-compatible tool or agent.

What are the main limitations of this approach?

It is less suited for large, collaborative teams requiring real-time updates, conflict resolution, and permissioning. Automation agents also pose risks if not carefully managed.

Can this system integrate with existing project tools?

Yes, since the roadmap is a JSON file, any tool or script that can read and write JSON can integrate with it, making it highly flexible and open.

Is this approach suitable for enterprise project management?

Currently, it is best suited for small teams or operators. Large enterprises needing advanced collaboration features may find it insufficient without additional support tools.

Source: ThorstenMeyerAI.com