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

Threlmark has unveiled a radically different approach to project roadmaps, where the entire plan is stored as a plain JSON file on the user’s local disk, rather than within a SaaS platform. Disk Is the Contract: Inside Threlmark’s Local-First Architecture This shift aims to give users full control, durability, and interoperability by removing dependencies on proprietary APIs and vendor-specific tools.

The core principle of Threlmark’s approach is that the roadmap is a simple, structured JSON file that any program capable of reading or writing JSON can access. This means that the plan is not locked inside a vendor’s SaaS environment but is instead owned directly by the user. The roadmap’s structure serves as the integration point, enabling any compatible tool or agent to read or update it without requiring special SDKs or webhooks.

Threlmark’s system also incorporates scoring of items on the roadmap, allowing prioritization and trade-offs to be visible. The ranked list helps teams focus on what matters most, enforcing discipline through subtraction—if everything is high priority, nothing is prioritized. The roadmap is designed to support automated agents that can read, modify, and update the file directly, creating a live, shared workspace for humans and AI agents alike.

While this approach emphasizes simplicity and durability, Threlmark acknowledges limitations, such as the lack of real-time collaboration features found in SaaS tools. It is targeted at small teams or operators who value control and longevity over large-scale concurrent editing. The approach also requires careful management of scores and guardrails to prevent corruption or misprioritization.

Implications for Project Management Control

This development matters because it shifts project planning from vendor-controlled SaaS environments to user-owned files, enhancing durability, interoperability, and independence. It reduces lock-in risks, allowing teams to maintain their roadmap regardless of platform changes or vendor discontinuation. For small teams and operators, this provides a simplified, reliable foundation for automation and collaboration without the complexity of traditional tools.

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.

Background on Roadmap Tools and Data Portability

Traditional project management tools rely heavily on SaaS platforms that store roadmaps within proprietary environments, often leading to vendor lock-in and dependency on APIs. For more on how open standards improve data portability, see The referral. How AI search severs the content-for-traffic contract that funded the open web. Threlmark’s approach is a response to these limitations, emphasizing local control and open standards. The concept builds on ongoing discussions about data portability, durability, and interoperability in project planning, aiming to empower users with more direct control over their planning artifacts.

“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 deliberate choice: the roadmap is a JSON file on your disk.”

— Thorsten Meyer, Threlmark

Limitations and Challenges of Disk-Based Roadmaps

It is not yet clear how well this approach scales for large, distributed teams requiring real-time collaboration or conflict resolution. To understand the importance of local-first architecture, see Disk Is the Contract: Inside Threlmark’s Local-First Architecture. The reliance on local files may hinder multi-user concurrent editing and audit trails at enterprise scale. Additionally, the risks associated with agent writes—such as accidental corruption—necessitate guardrails and careful management, which are still being developed.

Next Steps for Adoption and Tool Integration

Threlmark plans to release detailed documentation and open-source tools to facilitate adoption. Future developments may include enhanced guardrails, version control features, and integrations with existing project management workflows. The community and early adopters will likely experiment with the approach, providing feedback on its practicality for different team sizes and workflows.

Key Questions

How does this approach handle multiple users editing the roadmap?

Currently, the approach is best suited for small teams or operators. It does not support real-time concurrent editing natively, so managing simultaneous updates requires manual coordination or guardrails to prevent conflicts.

Can existing project management tools integrate with this JSON-based roadmap?

Yes, any tool capable of reading or writing JSON can potentially integrate, making it highly flexible. However, dedicated plugins or scripts may be needed for seamless workflows.

What are the risks of using a plain JSON file for critical project data?

The main risks include potential data corruption from agent errors, lack of real-time collaboration features, and the need for manual management of access and updates.

Is this approach suitable for large-scale enterprise project management?

Threlmark acknowledges that this approach is primarily designed for small teams or individual operators. Large enterprises may find the lack of concurrency and audit features limiting.

Source: ThorstenMeyerAI.com