TL;DR
ThorstenMeyerAI.com’s Day 7 Built in Public dispatch describes Threlmark as an MIT-licensed roadmap tool whose working artifact is a JSON file on the user’s disk. The source confirms a scored kanban view, planned agent read-write workflows, and a link to threlmark.com, while warning that agent edits need review.
ThorstenMeyerAI.com’s Day 7 Built in Public dispatch presented Threlmark as an open-source, MIT-licensed roadmap tool built around a user-owned JSON file, a design choice meant to let humans, tools and automated agents work from the same local planning artifact.
The dispatch says Threlmark’s roadmap lives as a plain JSON file on a user-controlled disk. The kanban board is described as a view over that file, rather than the authoritative data store. Tools and automated agents can read and write the same file directly, according to the source, without depending on a SaaS API, authentication flow or rate limit.
The product is also described as a scored kanban board. Each work item carries a priority score, and the source frames scoring as a way to force ranking rather than allowing every card to sit at the same priority. The dispatch ties Threlmark to IdeaClyst, saying verdicts from IdeaClyst’s council become scored roadmap items in Threlmark.
ThorstenMeyerAI.com says Threlmark is open source under MIT and points readers to threlmark.com and a technical write-up. The source also includes a caution that automated agents can make mistakes and that agent-written changes should be reviewed before being treated as reliable project data.
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 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.
Local Roadmaps Cut Vendor Risk
The main consequence is ownership of planning data. Many roadmapping systems store plans behind vendor APIs; Threlmark’s stated bet is that the JSON file itself becomes the integration point. If the format remains stable, teams could move between editors, scripts, agents and version control without depending on one hosted service.
The agent angle gives the announcement added relevance. The dispatch treats the roadmap as a shared workspace for human operators and AI agents: an agent can take a scored decision, write a work item, and leave the file where the UI can render it. That lowers integration overhead, but it shifts responsibility to review habits, file validation and change control.
local JSON file project management tool
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Day Seven Links The Stack
Threlmark is described as the Day 7 entry in a 19-part Built in Public series under ThorstenMeyerAI.com’s operator portfolio. The dispatch positions it inside a Decision Layer and shows a chain from IdeaClyst to Threlmark, with decisions becoming an ordered plan.
The source lists the inherited thesis as local-first, provider-agnostic, non-developer build and edit by subtraction. In this story, those principles appear as a file-based contract, a readable JSON structure and scored cards that force comparison between competing items.
The portfolio described in the source includes 18 products, with Threlmark serving as the place where decision output becomes roadmap work. The dispatch says the views are the author’s own and notes that product and company names remain trademarks of their owners.
“disk is the contract”
— ThorstenMeyerAI.com Day 7 dispatch
scored kanban board software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Open Issues For Agent Edits
The supplied material does not give a repository URL, release number, install flow, schema definition, supported platforms or exact publication date. It also does not show whether the JSON contract is stable, versioned, validated or protected from conflicting writes when multiple tools edit the file at once.
It is also not clear how Threlmark handles permissions, backups, concurrent agent activity, malformed JSON or merge conflicts. The dispatch makes the architectural bet clear, but adoption, maintenance plans and real-world usage remain open.
open source roadmap tool
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Repository Details Become The Test
The next milestones are practical ones: readers will look for the public repository, license file, file schema, examples and setup instructions at threlmark.com or linked project pages. If agents are expected to write into the roadmap, validation rules and review workflows will be central to whether the model works safely.
The Built in Public series is scheduled as 19 entries, and Threlmark is marked as Day 7. Later posts may clarify how the roadmap file connects with the rest of the portfolio, including IdeaClyst and other operator tools mentioned in the source.
agent workflow project planner
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is Threlmark?
Threlmark is described by ThorstenMeyerAI.com as an open-source, MIT-licensed roadmap tool. Its roadmap data is stored as a JSON file on the user’s disk, with the kanban board acting as a view over that file.
What does the disk-based contract mean?
It means the file format, rather than a vendor API, is the shared agreement between the app, other tools and agents. Any compatible program could read or update the roadmap if it follows the JSON structure.
Is Threlmark a SaaS product?
The source presents Threlmark as local-first and says the roadmap is not dependent on a SaaS API. The supplied material does not provide full deployment or hosting details.
How do agents fit into Threlmark?
The dispatch says automated agents can read and write the same roadmap file used by the UI. It also warns that those edits can contain errors and should be reviewed.
What is still unknown?
The source does not specify the exact schema, repository link, release status, supported platforms, conflict handling or validation model. Those details will determine how usable the file-based approach is in practice.
Source: Thorsten Meyer AI
