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

Threlmark has introduced a new approach to project roadmaps: the entire plan is a plain JSON file stored locally on the user’s disk, making it accessible and modifiable without reliance on SaaS APIs. This shift aims to enhance interoperability and durability, allowing any tool capable of reading or writing JSON to interact with the roadmap directly.

The core innovation from Threlmark is that the roadmap is no longer housed within a SaaS platform but is a simple, structured JSON file on the user’s local storage. This file acts as the single source of truth, with its format serving as the contract for all tools and agents that interact with it.

This approach enables any program or agent that can handle JSON to read and update the roadmap without requiring SDKs, webhooks, or API authentication. It aligns with principles of open-source, local-first, and provider-agnostic design, giving users full control over their project data.

Threlmark also introduces a scored kanban system, where each item carries a priority score, promoting clear trade-offs and intentional prioritization. The system supports automation, with agents able to read, modify, and update the roadmap file directly, creating a shared workspace for humans and AI agents alike.

Implications of ‘Disk Is the Contract’ for Project Management

This new model shifts the control and ownership of project data back to users, reducing dependency on vendor SaaS platforms that can change or discontinue features. It enhances durability and interoperability, making project plans portable and future-proof. However, it also introduces limitations in multi-user, real-time collaboration, which is less suited for large teams or enterprise environments.

For small teams and operators, this approach simplifies automation and integration, potentially reducing costs and increasing flexibility. It emphasizes core principles of open data and local control, which are increasingly valued in software development and project management communities.

Background and Rationale Behind Threlmark’s Approach

Traditional roadmap tools rely heavily on SaaS platforms, which centralize data but also create lock-in and dependency risks. Threlmark’s philosophy challenges this by proposing that the roadmap should be a simple, portable file, ensuring long-term access and interoperability. The concept aligns with broader movements toward open data, local-first architecture, and automation-friendly workflows.

This development builds on existing ideas of open formats and local control, but uniquely emphasizes that the contract—the structure of the roadmap—is the file itself, not a proprietary API or platform. The approach aims to reduce vendor lock-in and increase resilience against platform deprecation or changes.

“A roadmap is only useful if the thing that updates it and the thing that reads it agree on where it lives. Threlmark’s approach makes the entire plan a plain JSON file on your disk, ensuring durability and interoperability.”

— Thorsten Meyer, Threlmark

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

It remains unclear how well this approach scales for large, distributed teams needing real-time collaboration or conflict resolution. The system is designed for small teams or operators, and may not support simultaneous multi-user editing effectively. Additionally, the risk of data corruption or mis-writes by agents requires guardrails and review processes, which are not yet detailed.

Further, the effectiveness of the scoring system depends heavily on how well priorities are set, which could lead to misprioritization if scores are poorly managed. The approach also presumes that users are comfortable managing local files and manual synchronization.

Upcoming Developments and Adoption Strategies

Threlmark plans to release detailed documentation, open-source tools, and guardrails for managing agent interactions to mitigate risks. They will likely explore integrations with existing project management tools and automation platforms to expand usability.

Further updates may include features for better multi-user support or conflict resolution, but the core remains the local file contract model. Adoption will depend on how well small teams and operators embrace this minimalist, open approach.

Key Questions

How secure is storing project data as a local JSON file?

Storing data locally reduces exposure to SaaS platform breaches but introduces risks related to file corruption or loss. Users should implement backup strategies and guardrails for agent interactions.

Can this approach support large teams working simultaneously?

Currently, the model is best suited for small teams or operators. Large, distributed teams requiring real-time collaboration may find it limited, as conflict resolution and concurrent editing are not inherently supported.

Is this compatible with existing project management tools?

Yes, any tool that can read and write JSON can potentially integrate, making it highly interoperable. However, specific integrations are yet to be developed or documented.

What happens if an agent corrupts the roadmap file?

Since agents can write directly to the file, safeguards such as review processes or version control are recommended to prevent corruption or unintended changes.

Will Threlmark add features for multi-user editing?

There is no indication yet, but future updates may explore ways to support multi-user workflows or conflict resolution within this local-file paradigm.

Source: ThorstenMeyerAI.com