Permissions

The core idea

SYLRA is designed around a permission and approval model, not free rein over your computer. It determines what actions a task might need, and sensitive actions are intended to require your explicit approval before they happen.

What counts as sensitive

Anything that meaningfully changes or removes something — deleting files, modifying important project structure, or taking actions outside the scope of what you asked for — is the kind of action meant to pause for your confirmation rather than proceeding silently.

Activity logs

A planned transparency feature is a record of what SYLRA actually did during a task — so actions taken on your computer are visible after the fact, not just trusted blindly.

Where this stands today

This is the intended architecture. The full production permissions and approval system is still being finalized ahead of launch, alongside the rest of the security architecture — see Security for more, and the site avoids making absolute promises before that work is done.