Thorsten Meyer AI has introduced Threlmark, an MIT-licensed, local-first roadmap tool whose central product decision is that the roadmap lives as a plain JSON file on the user’s disk rather than inside a hosted database. The announcement matters for teams and solo builders testing AI-assisted planning workflows because it makes the file itself the shared contract for the board, other tools and agents, according to the source material.

The confirmed product description is narrow and specific: Threlmark’s kanban board is a view over a local roadmap file, identified in the source material as roadmap.json. The announcement says outside tools and automated agents can read from and write to that same file directly, without using a SaaS API, webhook, vendor SDK or hosted authentication flow.

The source material also describes Threlmark as a scored kanban system. Items on the board carry priority scores, and the example board shown in the announcement includes columns for backlog, scored work, active work and completed work. Thorsten Meyer AI says that scoring is meant to make trade-offs visible by forcing roadmap items into a ranked order rather than treating all cards as equal priorities.

The announcement places Threlmark inside a broader product set called the operator portfolio and links it to IdeaClyst, another decision-layer tool in the series. In that workflow, IdeaClyst produces verdicts and Threlmark turns those verdicts into ordered roadmap items, according to the source material.

File-Based Roadmaps Reduce Lock-In

For readers following AI-assisted product operations, the key claim is that a roadmap file can become a stable integration point. If the file format is open and documented, any tool that can parse JSON can inspect the plan, and any authorized workflow can propose changes. That model could appeal to builders who want planning data to remain readable outside the app that created it.

The product’s anti-lock-in argument is explicit but still a claim from the publisher. Thorsten Meyer AI says a text file on disk can outlive a vendor, API policy or pricing model. That does not prove Threlmark will replace established roadmap products, but it does identify a clear audience: users who care more about data ownership, simple automation and agent-readable workflows than hosted collaboration features.

Day Seven In The Build Series

Threlmark was presented as Day 7 of a 19-part Built in Public series from ThorstenMeyerAI.com. The entry describes the product as part of a local-first, provider-agnostic foundation across an 18-product portfolio. The source says the work is independent commentary produced with AI assistance under human editorial oversight.

The relevant product backdrop is the current growth of agent workflows that need shared operational state. Many project management and roadmap tools keep that state in hosted databases exposed through managed APIs. Threlmark takes the opposite position in this announcement: the operational record is the local file, and the board is only one interface over it.

The project is described as open source under the MIT license and provided ‘as is’ without warranty. The source also includes a safety caveat for agent workflows, warning that automated writes can introduce errors and should be reviewed rather than treated as verified facts.

Agent Edits Still Need Review

Several practical details are still unclear from the provided material. The source does not give the full schema, installation steps, repository path, versioning policy, sync model or merge-conflict handling for cases where multiple tools or agents edit the same roadmap file.

It is also not yet clear how Threlmark will handle permissions, audit history, validation errors or corrupted JSON in routine use. Those details matter because direct file access lowers integration friction but can also make mistakes easier to commit without guardrails.

Repository Details Face Scrutiny

The next stage for readers is to inspect the MIT-licensed source, the documented roadmap format and any examples published through threlmark.com. The main test will be whether the file contract is stable enough for real tools and agents to share, edit and validate without breaking the plan.

The Built in Public series is also expected to continue beyond Day 7, which may add more detail on how Threlmark connects with IdeaClyst and the rest of the decision-layer products. Until those details are public, the confirmed news remains the product announcement and its file-first design.

Key Questions

What is Threlmark?

Threlmark is a local-first roadmap and kanban tool announced by Thorsten Meyer AI. Its roadmap data is described as a plain JSON file on the user’s own disk.

What does ‘disk is the contract’ mean?

It means the shared contract between the board, outside tools and agents is the file format itself. The source says the UI reads the file, and other tools can read or write the same file if they follow its structure.

Is Threlmark open source?

Yes. The source material says Threlmark is open source under the MIT license and provided ‘as is’ without warranty.

What remains unknown about the tool?

The provided material does not specify the full schema, release cadence, repository path, sync behavior, permissions model or how it prevents bad agent writes from damaging the roadmap file.

Why would readers care about a JSON roadmap file?

A local JSON roadmap can be read by many tools without a vendor API. For teams using automation or AI agents, that could make roadmap data easier to inspect, rank, edit and preserve outside a single hosted service.

Source: Thorsten Meyer AI