📊 Full opportunity report: Threlmark: Disk Is the Contract on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Threlmark announces a new roadmap approach where the plan is a JSON file on disk, making it open, durable, and easily integrated with any tool that reads JSON. This shifts control from SaaS tools to the user’s own files.
Threlmark has unveiled a new approach to project roadmapping, where the roadmap is a plain JSON file stored locally on a user’s disk. This design eliminates reliance on SaaS APIs, offering a simple, interoperable, and durable solution for small teams and operators.
The core innovation from Threlmark is that the entire roadmap exists as a JSON file on the user’s local disk, serving as the definitive contract for project planning. This file can be read and written by any tool capable of handling JSON, removing dependencies on proprietary SaaS APIs and vendor lock-in. The roadmap is visualized through a scored kanban board, where each task carries a priority score, facilitating clear prioritization and trade-offs. Because the roadmap is just a file, it remains accessible and durable over time, outliving specific tools or platforms. The system supports automated agents that can read and update the roadmap directly, enabling a live, shared workspace for humans and AI agents alike. Threlmark emphasizes local-first and provider-agnostic architecture, reducing complexity and increasing control for small teams and operators. However, it is acknowledged that this approach may not suit large, multi-user environments requiring real-time collaboration and conflict resolution. The company also notes that scoring accuracy depends on proper setup and that agent updates require careful management to avoid corruption.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 developed privately and is not publicly available. 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 Local-First Roadmapping Changes Project Control
This approach shifts control of project plans from SaaS vendors to the users, offering increased durability and interoperability. It reduces vendor lock-in, enabling long-term access and flexibility. For operators and small teams, it simplifies integration with automation and AI agents, potentially improving efficiency and transparency. However, it may not meet the needs of large, collaborative organizations that require real-time editing and conflict management.
As an affiliate, we earn on qualifying purchases.
The Evolution of Roadmapping Tools and Open Data
Traditional project management tools rely heavily on SaaS platforms with proprietary APIs, which can introduce lock-in, deprecation risks, and limited durability. This shift towards local-first data aligns with broader trends towards open and interoperable data management. Threlmark’s approach draws inspiration from the principle that operational data should be owned and controlled by the user. The concept of making the roadmap a simple, structured file aligns with broader trends towards local-first, open, and interoperable data management. This development builds on ongoing discussions about reducing dependency on vendor-specific ecosystems and increasing resilience through open formats.
“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 roadmap a plain JSON file on your disk.”
— Thorsten Meyer, Threlmark
As an affiliate, we earn on qualifying purchases.
Limitations of Disk-Based Roadmaps for Large Teams
It remains unclear how well this approach scales for large, distributed teams requiring simultaneous editing, conflict resolution, and real-time collaboration. For more on the challenges of AI and content licensing, see Raw-feed licensing. Threlmark acknowledges that a JSON file on disk is not suited for high concurrency environments, and the effectiveness depends on proper scoring and management of agent updates. The specifics of how to implement safeguards and review processes are still being developed.
As an affiliate, we earn on qualifying purchases.
Next Steps for Adoption and Tool Integration
Threlmark plans to release the full documentation, enabling users to adopt the approach. Future developments may include enhanced guardrails for agent updates, integrations with existing project tools, and community feedback to refine scoring and collaboration workflows. The company will also explore how to support larger teams despite the inherent limitations of local files.
Kanban board with JSON integration
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
How does this approach compare to traditional SaaS roadmapping tools?
Unlike SaaS tools that store data on proprietary servers, Threlmark’s approach uses a plain JSON file stored locally, giving users full ownership, durability, and interoperability with any JSON-compatible tool.
Can multiple users collaborate on the roadmap simultaneously?
Not easily. Since the roadmap is a local file, real-time multi-user editing with conflict resolution is limited. It is best suited for small teams or operators managing automated agents.
What are the risks of using a disk-based roadmap?
Risks include potential corruption if agents miswrite the file, and limitations in handling concurrent edits. Proper management and review processes are necessary to mitigate these issues.
Will Threlmark support larger organizations in the future?
While the current design favors small teams and operators, future updates may introduce features to support larger, distributed teams, but the core philosophy remains focused on simplicity and control.
Source: ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
