Veklom is built to constrain machine action, not to create a safer-looking path for unauthorized behavior. Operators remain responsible for having legitimate authority over the systems and consequences they connect.
You must have permission to connect, inspect and operate every repository, API, model, service, account or infrastructure target used through Veklom. A successful technical connection does not establish legal or organizational authority.
Do not intentionally falsify, delete, suppress or misrepresent execution evidence, recovery evidence, policy decisions or verification outputs where those records are required for the governed action or the applicable deployment policy.
Adversarial testing should use environments and targets you control or are expressly authorized to test. Production-shaped simulations must remain labeled as simulations until provider-side consequence and readback evidence exists.
Veklom's authority model narrows what software may do; it does not grant permission from the owner of an external system. Technical capability and legitimate authority are separate requirements.
