Access and approvals

The product principles for work that touches your sources and tools.

Status: product direction. Veracto is being designed around a simple rule: you decide what it may touch.

A helpful agent can suggest work and prepare a result. When a task needs a source, permission, or external change, the intended experience is to make that boundary clear rather than hide it behind a chat response.

What you should see

Why access is needed

When work depends on a source or tool, the product should explain the purpose in the context of the task. Access is not a generic setup step detached from the work you asked for.

What may happen next

Before an external effect, the relevant action and scope should be visible. The point is to make a meaningful decision possible, not to turn every task into a maze of confirmations.

What was used

A final handoff should distinguish the result, its source basis where relevant, and any limit or uncertainty that remains.

How to change your mind

Access and saved context should be reviewable and reversible. The intended product model gives people a way to adjust or revoke them rather than treating earlier consent as permanent.

Honest limits

If Veracto cannot proceed safely or lacks the context it needs, it should say so plainly. A plausible-looking response is not a substitute for completed work.

These are product and release principles. They do not claim that every approval, access, or review surface is already available.