Why deleting a document always requires your approval

Deleting a document in HIIE always passes through a Human Input Popup (HIP). Camelia will never quietly remove a file — she proposes the deletion and waits for you to approve it.

How the gate works

The delete_document tool is the one built-in tool Camelia does not execute directly. Instead of acting, she logs a pending deletion proposal and raises a HIP. The action runs only if you approve it. If you decline, the file stays exactly where it is.

Why deletion is treated differently

Most of Camelia's built-in tools — reading, writing, labelling, moving, queueing flows, spawning sub-agents — apply directly, because they act on your own project data. Deletion is different: it destroys data. That makes it a hard, blocking decision rather than a routine edit, so it is gated behind a true-gate approval.

Where you'll see it

This is most visible in Documents. Camelia's Organize tool can dedupe files, flag conflicts, smart-label, and move misfiled files automatically — but when organizing would require removing a file, that deletion still raises a HIP for your approval. The cleanup happens around the deletion; the deletion itself waits for you.

What this means for you

You can let Camelia tidy and restructure a project with confidence, knowing nothing gets erased without an explicit yes. Each proposed deletion is presented one at a time as a clear gate, so you always know exactly which document is about to be removed before it happens.