Guarded Docs · Included in every plan
Your documentation, under your control.
Every project stays current on your machine, readable by any AI, and changed only when you approve. If something breaks, it heals itself.
Clean Markdown · One folder you pick once · Every version kept
The problem
You pay for every search through your docs, and still get the wrong version.
Documentation piles up: plan-v2.md, plan-final.md, plan-final-2.md, a notes file from March you never deleted. Here is what one small request costs.
An illustrative session. Real numbers depend on how many files your docs hold.
-
01
You keep paying to find the same decision.
Files opened. Tokens spent. Nothing built yet. Next session, the same search again.
-
02
Your docs moved on. Your AI didn’t.
Your latest decision is buried among old drafts. Your AI follows the wrong one, and the work goes in the wrong direction.
-
03
Your AI rewrote the rules it was supposed to follow.
An agent rewrites your documentation mid-task. You’re left working out what changed and restoring what you meant.
The solution
One current version. A map to find it. Your approval to change it.
Same request, same docs. This time Guarded Docs keeps one approved version of every project on your machine, with a map any AI can read.
An illustrative session. Real numbers depend on how many files your docs hold.
-
01
Straight to the answer, for a fraction of the tokens.
The map in every folder sends your AI to the right section. One file instead of six, and the next session finds it just as fast.
-
02
Your AI reads the version you approved.
Only the latest approved version lives in the folder. There is no old draft left to follow by mistake.
-
03
Your rules change only when you say so.
Your AI proposes; you review each change and approve it. If anything in the folder is altered, the approved version comes back on the next update.
One source of truth
Every project lives in Grasppy, with every version kept.
Plans, documentation, rules, skills, prompts, memory, research and any project you create are kept in Grasppy as structured Markdown. Every change becomes a new version, and any earlier version can be restored in one click.
Project Folders
Always current on your machine.
Each project is mirrored, one way, to its own folder as clean Markdown, always the latest approved version. All of it lives in one folder you pick once, and Grasppy never touches anything outside it.
your-project/grasppy-exports/ ├── myplans/ every plan │ └── 03_Auth/3.2_Sessions.md updated to v6 ├── mydocs/ your documentation ├── myrules/ rules your agents follow ├── myskills/ reusable skills ├── myprompts/ prompt library ├── mymemory/ long-term memory ├── myresearch/ approved research └── your-own-project/ Every folder contains README.md how an AI should work here MANIFEST.md a one-line map of every section
Built for any local AI
One map, so your AI finds anything without wasting tokens.
The README tells an agent how to work with the folder. The MANIFEST maps every section in one line, with its size and where it lives. However large a project grows, the agent reads the map first and opens only the file it needs.
Works with Claude Code, Codex, Cursor or a model running on your own machine — anything that can read a folder.
# My Plans — Documentation Manifest > Auto-synced by Grasppy · Last synced: 2026-10-10 ## [id:41200] Auth: Login and Sessions - [id:41201] Decisions (3.6KB) - [id:41202] Sessions (2.1KB) - [id:41203] Password Reset (4.4KB) - [id:41204] Rollout (1.8KB)
AI proposes, you decide
Your AI never edits the record. It proposes.
The agent reads the folder
It starts from the manifest, opens only what it needs, and works from the latest approved version.
It writes a check-in file
Instead of changing your documents, it puts the proposed changes in a check-in file, ready to import.
You review, section by section
Grasppy shows every change side by side with what is there today. You approve or reject each section.
A new version, and the folder updates itself
Only what you approved becomes a new version. The project folder on your machine refreshes to match.
Self-healing
If something breaks, it heals itself.
Project Folders are a mirror, not the original. If an agent or a stray command changes, deletes or breaks a file, the next update puts the approved version back. Nothing in the record can be destroyed from the folder.
Guarded by design
Protection that comes from the architecture.
- One folder, nothing outside it. You pick a project folder once. Grasppy works only inside its
grasppy-exports/folder and never writes anywhere else on your disk. - One way, on purpose. The folder follows Grasppy, never the other way round, so a bad local edit can never overwrite the record.
- Every version kept. Each approved change is a new version with its history. Restore any earlier one in a click.
- Nothing changes without you. Documentation, rules and memory change only through check-ins you approve. Your agents work fast; you keep the say.
Part of the whole
How Guarded Docs fits with the rest of Grasppy.
Recall
Memory for your agents: every session remembered, and a briefing at the start of the next.
See Recall → Keeps every conversationContext Vault
Your analysed conversations, decisions and diagrams as a local folder for AI.
See Context Vault → Keeps every agent alignedRules Sync
One set of rules, written for Claude Code and Codex alike, so every agent follows the same ones.
See all features →Questions
Straight answers.
The five things people ask first about Guarded Docs.
Can my AI edit the files directly?
It can, but it would not stick: the folder is a mirror, and the next update restores the approved version. Real changes go through a check-in you approve.
What if I change a file by mistake?
The same thing: the approved version comes back on the next update. Your work in Grasppy is never touched by the folder.
Does it work with Cursor or a local model?
Yes. Anything that can read a folder can use it: point it at a project folder and ask it to read the manifest first.
Is it included in every plan?
Yes. Guarded Docs is part of Light, Pro and Max, with no extra charge. Keeping folders current uses no credits.
Where are the files on my disk?
Inside the project folder you chose, in grasppy-exports/, one subfolder per project, each with its README and MANIFEST.
Keep the project. Stay in control.
Guarded Docs is part of Grasppy, the workspace around your AI coding tools: capture, plans, memory and documentation, all under your approval.