Imagine you’re working on a project. You want your tools to be fast, flexible, and never locked into a single app or cloud. That’s what Threlmark does. It treats your project data like a set of plain files sitting on your disk, making everything simple, transparent, and portable.

This isn’t just about saving space. It’s about shifting the whole idea of how project management software should behave. No server, no cloud dependency, just your files—easily backed up, shared, or edited by any tool you like. And the real genius? The on-disk structure is the API. That one simple choice unlocks a world of possibilities.

Key Takeaways

• Treat your project data as plain JSON files on disk — it’s simple, portable, and lock-free.
• Atomic file writes prevent data corruption even if your system crashes during save.
• One file per item makes concurrent editing safe and your boards self-heal automatically.
• The disk becomes your API, making your data accessible to any tool or AI without extra layers.
• This approach supports offline work and syncs smoothly once reconnected.

Why Your Project Data Should Live on Disk, Not in a Database

Most apps hide your data inside databases or cloud services. Threlmark flips that idea. It treats your project files like a contract—always on your disk, always accessible, and never locked behind proprietary formats.

Picture this: you have a folder with a file for each task, each project, each idea. You can open, edit, or share these files with any tool—no special permissions needed. That raw access means your data stays yours, portable and safe.

This approach makes collaboration and backups simple. Just copy a folder, and your entire project moves with it. No vendor lock-in, no complicated migration.

How Threlmark’s File Structure Turns Projects Into a Living Contract

At the heart of Threlmark is a disciplined file layout. The root folder contains a manifest (`threlmark.json`) and a dependency graph (`links.json`). Each project has its own folder with metadata, lane order, and one file per card.

Imagine a folder called `items/` filled with individual JSON files. Each file is a task or idea—unchanged whether you’re offline or online. External tools can read or write these files without asking for permission.

This structure isn’t just storage; it’s the contract. Everything is visible, diffable, and fully portable. Want to back up your project? Just copy the folder. Need to move to a new machine? Copy and go.

Why Atomic File Writes Make Your Data Safe and Reliable

When dealing with files, safety is everything. Threlmark uses atomic writes—write to a temp file, then rename. This simple trick prevents corruption if your system crashes mid-save.

For example, updating a task involves writing a new JSON file. If your computer crashes during that write, the old file remains untouched. That’s how data stays consistent, even in chaos.

This method is so reliable that it’s used in high-stakes systems like databases. It keeps your project data safe without complex locking or locking mechanisms.

How Single-Item Files and Self-Healing Boards Keep Everything Syncing

Instead of one big list, Threlmark uses one file per task or item. This means external tools can change individual cards without messing up the whole project.

Imagine a Kanban board where each card is a separate file. When you move a card, only that file updates. The board then self-heals—it checks itself against the actual files, fixing any inconsistencies.

This approach makes collaboration smooth. Multiple tools can update different cards simultaneously without conflicts, because each file is atomic and independent.

Making Projects Portable and Interoperable — No Lock-In Needed

Because all data lives in plain JSON files, any tool can join in. Need a custom script or an AI assistant? Just read or write the same files.

This openness means you aren’t tied to a single app or vendor. You can back up your entire project with a simple copy, migrate to other tools, or even write your own extensions.

It’s like having your project in a shared folder that any editor, script, or AI can access—no special API required.

How Threlmark Supports External Tools and AI Agents Seamlessly

Threlmark’s structure invites external tools. Want an AI to help move tasks or update statuses? Just point it at your files.

For example, an AI agent can scan the `items/` folder, decide what’s next, and update files directly. No API calls, no middleman. It’s all plain files, just like working on a shared folder.

This design not only speeds up automation but also makes your workflow transparent. You see exactly what the AI does, because changes are right there in the files.

Real-World Example: How Threlmark Keeps Projects Alive During Outages

Imagine working late at night, disconnected from the internet. Threlmark keeps your project alive because all data is on your disk. You continue working seamlessly, and when you reconnect, all changes sync up.

For instance, a team member updates a task on their laptop. When they go online again, their local files sync with others, updating the central state without any fuss or conflicts.

This resilience is a game-changer for teams in remote areas or with unreliable internet.

Frequently Asked Questions

What does ‘disk is the contract’ really mean?

It means your project data lives as plain files on your disk, and these files define everything. No database, no cloud dependencies—simply the files are the source of truth, accessible and editable by any tool.

How does this approach handle multiple tools editing at once?

Since each item is a separate file, external tools can update individual files without conflicts. The system self-heals by reconciling the files against the board or project view, avoiding race conditions.

What happens during offline work or internet outages?

All data resides locally, so you can keep working without interruption. When you reconnect, changes sync automatically, making collaboration seamless even with unreliable internet.

Is this safe for sensitive data?

Yes, because data stays on your disk unless you choose to sync or share. You control the files, and they can be encrypted or stored securely just like any other local data.

Can I extend or customize this system?

Absolutely. Because everything is plain JSON files, you can write your own scripts, tools, or AI integrations to read, modify, or automate your project data without vendor lock-in.

Conclusion

Choosing disk as the contract transforms project management into a transparent, resilient process. Your data isn’t locked behind proprietary systems—it’s a set of files you control and understand.

Imagine a future where your tools, AI agents, and backups all work from the same plain files—fast, safe, and flexible. That’s the power of the local-first, disk-as-contract approach. It’s not just a technical choice; it’s a mindset shift toward true control.