Project Guardian
Make protected areas explicit.
Specify what must remain unchanged and inspect the protection actually available.
Make protected areas explicit.
Before allowing an agent to modify the project.
A broad request can unintentionally affect files you wanted to preserve. Guardian rules identify protected paths and the circumstances in which changes require attention.
Select files or areas, save the policy and inspect requests against it. Coverage depends on the execution route and its enforcement.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Select a file or folder and add a concrete preservation rule.
- 02
Review the protection supported by the selected engine and execution route.
- 03
Check warnings or blocked actions before sending a follow-up.
How it could work for you.
Protect an approved brand stylesheet while another part of the project is being developed.
How to assess the result
Structured file-tool checks are not automatically an operating-system sandbox for arbitrary terminal commands. Check the actual route before relying on protection.
Where to find it.
Conversation → Tools → Project Guardian
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Rules are saved for this project rather than automatically applied to all projects.
What you need to know
Instructions, warnings and technically enforced blocks are different. Terminal routes and external engines can have different restrictions; this is not a universal sandbox.