📊 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 methodology where the roadmap is a plain JSON file stored locally. This approach emphasizes simplicity, interoperability, and durability, challenging traditional SaaS tools.

Threlmark has introduced a novel approach to project roadmapping, asserting that “disk is the contract.” The company’s new product design centers on storing the entire roadmap as a plain JSON file on local disk, allowing human and automated agents to read and update it directly without reliance on SaaS APIs. This shift aims to enhance interoperability, durability, and control over project data.

Threlmark’s new methodology departs from traditional SaaS-based roadmap tools by making the roadmap a simple, structured JSON file stored locally. The file’s format acts as the definitive contract, enabling any compatible program or agent to read or modify it without needing specialized SDKs or API integrations.

The approach emphasizes local-first, provider-agnostic architecture, meaning the roadmap is owned and controlled by the user, not a vendor. This ensures longevity and reduces lock-in risks, as the data can be accessed with any standard JSON parser in the future. The roadmap also incorporates a scored kanban system, where each item has a priority score, facilitating clear trade-offs and focus.

Threlmark claims this design simplifies automation and collaboration, as agents can directly read, write, and update the roadmap file, closing the loop between planning and execution. However, the approach is acknowledged to have limitations, such as reduced support for real-time multi-user editing, conflict resolution, and permissioning, which are more suited to small teams or individual operators.

Threlmark — Disk Is the Contract · Built in Public Day 7/19
Built in Public · Day 7 / 19 ThorstenMeyerAI.com · the operator portfolio
The Decision Layer · Day 07 Dispatch

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.

01 One file. Everything reads & writes it.
Threlmark UI+ your tools
{ }
roadmap.json
the contract
Agentsread · act · write
read → act → write · no API, no lock-in — a plain file any program can honor
Backlog
Bulk CSV importer
score 49
Niche export format
score 58
Scored← council
Build: validated idea X
score 87
Build: validated idea Y
score 74
Doing
Ship feature Z
score 91
Done
Launch W
✓ shipped
1 filethe whole roadmap, on disk scoredevery item ranked MITopen source · agent-readable
02 Why a file beats a database here
JSON
the contract is a file format, not a vendor — anything that reads JSON is a client.
own it
a text file you own, that outlives any tool — no API, no rate limit, no lock-in.
agent-native
the roadmap is a shared workspace — humans and agents write to the same file.
03 The thesis the whole series inherits
01
Local-first
The roadmap is literally a file on your machine — not a row in someone else’s database.
02
Provider-agnostic
The contract is a format, not a vendor. Any agent, any tool that speaks JSON is first-class.
03
Non-developer build
Radical simplicity by design — the least lock-in-prone thing there is: a plain file.
04
Edit by subtraction
Scoring forces ranking. A board where everything is “high priority” has no priorities.
04 The operator constellation
18 products · one foundation
Today: Threlmark lit — where the council’s verdicts become an ordered plan. IdeaClyst → Threlmark.
Content
DojoClaw
RoundupForge
Stenvrik
ChannelHelm
IdeaNavigator
Decision
IdeaClyst
Threlmark
Outcome-First
Platform
Grimfaste
Delvasta
Open / Reg
Glasspane
QAtrial
Markets
Polybot
TradingAgents
Defense / Intel
Argus
VigilSAR
VigilSAR-Bench
Diagnostic
World Model Readiness
Local-first · Provider-agnostic foundation

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.

ThorstenMeyerAI.com · Built in Public · Day 7 of 19 · © 2026 Thorsten Meyer

Implications of ‘Disk as the Contract’ for Project Management

This development matters because it challenges the dominant SaaS paradigm for project planning tools, offering a more open, durable, and flexible alternative. By making the roadmap a simple file, users gain control over their data, reduce dependency on vendor-specific platforms, and enable seamless automation with any JSON-compatible tools. This approach could influence future tools to prioritize local, open formats over cloud-centric solutions, especially for small teams and operators.

Amazon

JSON file editor for project management

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on Roadmap Tools and Data Ownership

Traditional project management tools rely heavily on SaaS platforms with proprietary APIs, which can lead to vendor lock-in, data silos, and dependency on continuous service availability. Recent discussions in the tech community have emphasized the importance of data portability and ownership, especially as organizations seek more control over their operational data. Threlmark’s approach aligns with these concerns by proposing a simple, open format as the core artifact of planning.

Historically, roadmaps have been stored within complex systems with layered APIs, making interoperability and long-term access challenging. Threlmark’s decision to use a plain JSON file aims to address these issues by providing a transparent, durable, and easily accessible data format for project planning.

“A roadmap is only useful if everyone agrees on where it lives. Our approach makes the roadmap a simple, shared file on disk, ensuring durability and interoperability.”

— Thorsten Meyer, Threlmark founder

Amazon

local JSON roadmap tool

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

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

It is not yet clear how well this approach scales for larger teams requiring real-time collaboration, conflict resolution, and permission management. The reliance on local files may pose challenges for distributed, multi-user environments, and the risk of file corruption or mis-writes by agents needs further assessment. Additionally, the effectiveness of scoring and manual review processes in complex projects remains to be demonstrated.

Amazon

interoperable project planning software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Testing of the Approach

Threlmark plans to release the full open-source implementation and documentation on their website, inviting small teams and early adopters to test the approach. Future updates may include tools for conflict resolution, version control, and enhanced multi-user support. Observers will watch for feedback on how well the model works in real-world scenarios and whether it gains broader acceptance.

Amazon

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 ‘disk is the contract’ improve project management?

It offers a simple, durable, and open format for storing and sharing project roadmaps, reducing vendor lock-in and enabling seamless automation with any JSON-compatible tool.

What are the main limitations of this approach?

It is less suitable for large, distributed teams that require real-time collaboration, conflict resolution, or permission controls. Managing concurrent edits and preventing data corruption are ongoing challenges.

Can existing project tools adopt this approach?

Since the core artifact is a plain JSON file, any tool that reads or writes JSON can potentially integrate, but full adoption depends on developing or adapting tools to work with the specific schema.

Is this approach secure?

Security depends on how the files are stored and accessed. Since it relies on local files, it can be secured via standard file system permissions, but it does not inherently provide multi-user permissioning or encryption.

Source: ThorstenMeyerAI.com

You May Also Like

The Defender’s Counter-Cascade.

Google discloses the first confirmed AI-built zero-day exploit, highlighting the critical deployment gap in AI-driven cybersecurity defenses as of May 2026.

AMÁLIA · The Three Hard Questions.

Portugal’s €5.5M AMÁLIA project, a European Portuguese LLM, faces key structural questions about openness, native data, and objectives, impacting national AI policy.

The 2028 Model Lab Endgame: How Six Becomes Two, Three, or Twelve

Thorsten Meyer forecasts three possible futures for Western frontier AI labs by 2028, highlighting implications for global AI leadership and investment.

The Roblox Cheat That Broke Vercel.

A Roblox auto-farm script downloaded by an employee led to a two-month breach of Vercel, exposing customer credentials across multiple cloud platforms.