📊 Full opportunity report: Disk Is the Contract: Inside Threlmark’s Local-First Architecture on ThorstenMeyerAI.com — validation score, market gap, and execution plan.
TL;DR
Threlmark employs a local-first architecture where project data resides entirely on disk as JSON files, eliminating the need for servers. This design enhances portability, safety, and interoperability, allowing external tools and AI agents to participate seamlessly.
Threlmark has revealed a pioneering local-first architecture that treats disk storage as the definitive contract for project data, removing reliance on servers or cloud databases. This approach enables tools and AI agents to interact directly with JSON files, ensuring portability, safety, and interoperability across systems.
The core design choice in Threlmark is that all project information, including cards, dependencies, and workflows, is stored as individual JSON files within a dedicated directory, defaulting to ~/.threlmark. This directory contains a manifest (threlmark.json), project metadata, lane configurations, and one file per roadmap item, facilitating a completely file-based, serverless system.
Data integrity is maintained through atomic write operations: updates are written to temporary files then renamed, preventing corruption during crashes. The system also employs read-merge-write patterns, allowing tolerant updates that preserve unknown fields and ensure forward compatibility. This setup makes the data portable, inspectable, and compatible with any tool that reads files, enabling easy backups, migrations, and integrations.
One notable feature is the self-healing lane ordering: the board file is reconciled at read time, automatically adding missing items or removing obsolete ones, ensuring consistency without locks or complex synchronization. External tools, including AI agents, can participate by reading and writing these files directly, closing the loop on project automation and management.
Disk is the contract: inside a local-first roadmap hub
A Next.js app on top of plain JSON files — no database, no cloud, no accounts. The key decision: the on-disk layout IS the API. Everything else cascades from taking that seriously.
There is no server-of-record — the files are the record
The UI and any external tool reach the same files through the same discipline. The data root defaults to ~/.threlmark — home-based, because it’s a shared hub every one of your apps points at.
Inspectable
Every artifact is a file you can cat, diff, grep, commit.
Portable · no lock-in
Back up with cp, sync with Dropbox / git, migrate trivially.
Interoperable
Any tool in any language joins by reading / writing files.
Restartable
No in-memory state to lose — stateless over the files.
TOPCJ Accordion File Organizer,Expanding File Folder Portable Filing Folders,13 Pockets File Box with Handle for Documents,Special Design for Carrying,A4/Letter Size,Colored Tabs
✔【HIGH CLASS】Advanced sealing all edges, Visable Window for quick classification, Perfect high class file folders organizer for Carrying…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Two disciplined patterns instead of a database
“Just use files” is easy to get wrong. These two patterns — ported from a battle-tested sibling app — are what make file-based state sound rather than reckless.
Atomic writes
Write to a temp file in the same dir, then rename() over the target. Rename is atomic on one filesystem — a crash mid-write leaves the complete old file or the complete new one, never a half.
The board heals itself
A single roadmap.json array races when two tools write at once. One file per card makes writes collision-free. Lane order lives in board.json and reconciles on read.
board.json. It writes an item file — the board fixes itself on Threlmark’s next read. Unknown keys are preserved, so the contract is forward-compatible.
TIME TIMER 10 Minute MOD Education Edition — Visual Timer with Desktop Software for Kids Classroom Learning, Productivity Timer, Study Tool and Office Meetings with Silent Operation (10min)
SHORT DURATION: This duration is ideal for quickly timed activities like fine motor skill development, sensory activities, and…
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The numbers can’t drift from the files
Anything computable from item state is computed — so the displayed numbers can never disagree with the underlying JSON. Priority is the clearest example: it’s calculated on read, never persisted.
priority — computed on read
Impact weighted heaviest; effort the only axis that subtracts. Reused verbatim from the original tool, so imported cards rank identically.
serverless data backup solutions
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A handoff is a first-class flow event
The genuinely 2026-shaped part: most building is done by AI agents, so Threlmark closes the loop. Watch a card go from ranked to Done without anyone dragging it.
Handoff → report → self-move
The brief carries a reporting protocol. The agent reports through REST or the filesystem — and a done report moves the card itself.
POST /api/projects/:id/
items/:itemId/reportDirect call. Applied immediately.
drop reports/.json
→ ingested on read Robust even if the server’s down at finish time.
![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.
A small formula, and an honest hosting caveat
Because items are globally addressable (
Portfolio ranking — status-weighted
In-flight work floats to the top; bottlenecks cost the most, so blockers get nudged up.
Static read-only demo
Seeded data, writes to localStorage. Try-before-you-clone.
Personal Node instance
Password-gated, persistent backed-up THRELMARK_DATA_DIR.
Multi-tenant SaaS
Add accounts + per-tenant isolation. A separate build.
src/lib/*/store.ts is the natural seam — the same boundary that keeps the local tool simple is the one you’d extend for multi-tenancy. The architecture doesn’t fight that future; it just doesn’t pay for it until you need it.
Why Local-First Architecture Transforms Project Management
This architecture shifts the paradigm from cloud-dependent systems to a portable, transparent model that empowers users with full control over their data. It enhances resilience, as no server downtime affects access; it simplifies backups and migrations; and it fosters interoperability, allowing diverse tools to participate without proprietary lock-in. For AI integration, this means seamless, autonomous management of project tasks with no intermediary database or API, paving the way for more autonomous, resilient workflows.
The Evolution of Threlmark’s Data Model and Design Choices
Traditional project management tools often rely on centralized databases or cloud services, which can introduce lock-in, reduce transparency, and create single points of failure. Threlmark’s approach, detailed by Thorsten Meyer, emphasizes a decentralized, file-based system inspired by battle-tested patterns from other applications. Its architecture is designed to be simple yet robust, ensuring that all data remains accessible and modifiable via standard file operations.
This design was motivated by the need for a unified, multi-project hub that can handle complex workflows, external suggestions, and AI-driven automation without the constraints of server-based systems. The approach also aligns with modern principles of openness and interoperability, making it easier to integrate with other tools and platforms.
“The on-disk layout is the API. That one choice cascades into everything else—how concurrency is handled, why there’s one file per card, and how external tools can participate without permission.”
— Thorsten Meyer
Remaining Questions About Threlmark’s Scalability and Adoption
While the architecture’s benefits are clear, it is not yet confirmed how well this approach scales with large or highly complex projects. Additionally, the extent of external tool and AI agent support in real-world scenarios remains to be demonstrated as adoption progresses.
Future Developments and Potential Ecosystem Growth
Threlmark plans to continue refining its file-based system, potentially expanding integrations with external tools and AI agents. Further user feedback and real-world testing will determine how scalable and adaptable this architecture proves over time. The project may also see the development of standardized file schemas to enhance interoperability further.
Key Questions
How does Threlmark ensure data safety without a database?
It uses atomic file writes via temporary files and renaming, preventing partial writes or corruption during crashes.
Can external tools modify Threlmark data?
Yes, since all data is stored as readable and writable JSON files, any tool that can read and write files can participate.
What are the advantages of this disk-based approach?
It offers portability, transparency, easy backups, and no lock-in, while enabling seamless integration with AI agents and other tools.
Are there limitations to this architecture?
Potential concerns include scalability with very large projects and the need for external tooling to manage complex workflows efficiently.
Source: ThorstenMeyerAI.com
