Threlmark: Disk Is the Contract

📊 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 system based on the principle ‘disk is the contract,’ where project plans are stored as plain JSON files on local disks. This approach emphasizes simplicity, interoperability, and durability, moving away from traditional SaaS tools.

Threlmark has introduced a new approach to project roadmapping, where the entire plan is stored as a plain JSON file on the local disk, making it the definitive contract for project data. This shift emphasizes simplicity, interoperability, and durability, and marks a departure from SaaS-based roadmap tools.

The core idea behind Threlmark’s new system is that the roadmap is a plain JSON file sitting on the user’s own disk. This file acts as the single source of truth, accessible by any program capable of reading or writing JSON, eliminating dependence on proprietary SaaS APIs. The approach supports open source principles, with the format under MIT license, and enables seamless integration with various tools and agents that can manipulate JSON files. The roadmap is also scored, meaning each task carries a priority, which helps teams focus on the most important work and facilitates decision-making through visible trade-offs. This system allows humans and automated agents to read and update the roadmap directly, making it a live coordination layer rather than a static document. Threlmark claims this design offers interoperability by default, durability independent of vendor changes, and local-first operation, as the file resides on the user’s machine. However, it is acknowledged that this approach may not suit large teams requiring real-time collaboration or conflict resolution, and that improper scoring or mis-writes by agents could introduce risks.

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 for Project Management and Data Ownership

This development matters because it challenges the conventional SaaS-based approach to project planning, emphasizing data ownership, longevity, and interoperability. By making the roadmap a simple, open format stored locally, Threlmark reduces vendor lock-in and increases control over project data. This approach could influence how teams manage operational plans, especially smaller teams or those prioritizing durability and flexibility over real-time collaboration. It also raises questions about how large-scale, multi-user environments will adapt to such a system, given its limitations in concurrent editing and conflict management.

Amazon

JSON file project management tool

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Traditional Roadmap Tools and the Shift Toward Simplicity

Most project management tools rely on cloud-based SaaS platforms, offering features like real-time collaboration, conflict resolution, and permission management. These tools often lock users into vendor ecosystems, risking data loss if the service terminates or changes policies. Threlmark’s approach, announced in March 2024, proposes a paradigm where the roadmap exists as a plain JSON file, owned by the user, and accessible by any compatible tool. This concept aligns with open-source and local-first philosophies, emphasizing durability and interoperability. The idea builds on broader trends favoring minimal, reliable data artifacts over complex, vendor-dependent solutions.

“A roadmap is only useful if everyone agrees on where it lives. Our approach makes the roadmap a simple file on your disk, removing dependencies on SaaS APIs.”

— Thorsten Meyer, Threlmark founder

Amazon

local disk roadmap software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Limitations and Risks of Disk-Based Roadmaps

It is still unclear how well this approach scales for large, distributed teams requiring real-time collaboration. There are also concerns about potential risks if agents mis-write the JSON files or if scoring mechanisms are misused, which could corrupt the plan. Furthermore, the system does not inherently support multi-user conflict resolution or permissioning at scale, making it less suitable for enterprise environments with complex workflows.
Amazon

open source JSON project planner

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Integration Testing

Threlmark plans to release the open-source JSON schema and tools to facilitate adoption. Future developments may include safeguards for agent writes, improved conflict detection, and integrations with existing project management workflows. Observers will watch for user feedback on practical challenges and scalability, especially in multi-user contexts. The company may also explore hybrid models combining local files with cloud synchronization for larger teams.
Amazon

version control JSON files

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 roadmaps?

It replaces cloud-based APIs with a plain JSON file stored locally, emphasizing ownership, durability, and interoperability, but may lack features like real-time collaboration and conflict resolution.

Is this system suitable for large teams or enterprise use?

Currently, the system is optimized for small teams or individual operators. Large teams requiring concurrent editing and conflict management may find it less suitable without further development.

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

Yes, any tool capable of reading or writing JSON can interact with the roadmap, provided it adheres to the specified format, supporting interoperability.

What are the main risks of using a disk-based roadmap?

The primary risks include potential data corruption from mis-writes by agents, lack of real-time conflict handling, and limitations in multi-user environments.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

Succession Planning for Founders and Leaders

Great leaders plan ahead—discover how strategic succession planning can safeguard your company’s future and ensure seamless leadership transitions.

Customer Concentration Risk Planning: Where Most Teams Go Wrong

Bridging the gap in customer diversification is crucial, but many teams overlook key risks that could threaten their stability—discover how to avoid this mistake.

TAM SAM SOM Estimates Without Hype: the Practical Guide for Lean Teams

How to accurately estimate TAM, SAM, and SOM without hype—discover practical steps to ground your market sizing in reliable data and actionable insights.

Category Creation Strategies for Challenger Brands: Why It Matters More Than You Think

Sparking innovation through category creation can redefine your brand’s future, but understanding why it matters more than you think is the key to success.