TL;DR
Threlmark’s latest architecture write-up says the app treats local disk storage as the record, using plain JSON files rather than a database, cloud account, or server of record. The report says this design is meant to make project data inspectable, portable, offline-friendly, and accessible to external tools, though release status and independent performance data are not stated.
Threlmark’s new architecture report says the project management app uses plain JSON files on local disk as its source of truth, rather than a traditional database, cloud backend, or account system, a design choice that affects how the app handles sync, offline use, automation, and third-party tooling.
The report describes Threlmark as a Next.js and TypeScript app built around a default data root at ~/.threlmark. Its file tree includes a manifest, dependency graph, project folders, one JSON file per card, agent handoff records, reports, an archive, and a human-readable roadmap mirror.
According to the source material, the central design rule is that the disk layout is the API. The UI and external tools are expected to read and write the same files under the same discipline, making every artifact available to command-line tools, sync tools, backups, version control, and other applications.
The report says Threlmark uses two main safety patterns: atomic writes and one file per item. Writes go to a temporary file in the same directory before being renamed over the target, while individual cards are stored separately to reduce collisions when more than one tool writes data.
Why It Matters
The design matters because it challenges a common app architecture choice: making a hosted service or database the primary record. If the model works as described, users could inspect, copy, diff, back up, commit, and migrate their project data with ordinary file tools.
It also matters for teams and developers using AI agents or automation. The report says external tools can create or update work items by writing files, while Threlmark reconciles board state when it reads the project. That could make agent-driven workflows less dependent on a running web server.
JSON file editor for project management
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
The source frames the report as part 2 of a Threlmark series and calls the system local-first. The app is described as using JSON-on-disk, MIT licensing, and no database, cloud service, or accounts.
The report also says several values shown in the app are derived rather than stored. Priority is calculated on read from impact, evidence, fit, and effort. Other computed values include stale-work age, cycle time, weekly throughput, and work-in-progress counts.
A later section describes an agent loop in which a handoff produces a report. The preferred path is a REST call to a project-item report endpoint, while the fallback is a JSON report dropped into a reports folder and ingested on read.
“The on-disk layout IS the API.”
— Thorsten Meyer AI source material
“There is no server-of-record – the files are the record.”
— Thorsten Meyer AI source material
“Every artifact is a file you can cat, diff, grep, commit.”
— Thorsten Meyer AI source material
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL500_.jpg)
Free Fling File Transfer Software for Windows [PC Download]
Intuitive interface of a conventional FTP client
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
The source material does not state whether all described features are already released, in testing, or planned. It also does not provide independent benchmarks, user adoption figures, security details, or a full conflict-resolution model for multi-device sync through services such as Git or Dropbox.
version control tools for JSON project data
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
The next thing to watch is whether Threlmark publishes implementation details, release notes, repository updates, or usage examples that show the architecture working across real projects, external tools, and agent handoffs.
Information Technology Project Management (MindTap Course List)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the actual news development?
Thorsten Meyer AI published a report explaining Threlmark’s local-first architecture, centered on the claim that local disk files are the application’s source of truth.
What is confirmed by the source material?
The source says Threlmark is a Next.js and TypeScript app using plain JSON files, a default ~/.threlmark data root, one file per card, atomic writes, derived metrics, and REST or filesystem-based agent reports.
What claims still need proof outside the report?
The report claims the design improves portability, offline use, restartability, and tool interoperability. The material provided does not include independent testing, production usage data, or benchmark results.
Why would readers care?
Readers interested in local-first software, AI-assisted project workflows, or data ownership may care because Threlmark’s approach keeps project state in ordinary files rather than behind a hosted service.
What remains unclear?
The source does not give an exact release date, public availability status, security model, or detailed behavior when multiple devices edit the same files through outside sync tools.
Source: Thorsten Meyer AI
