Deterministic
Customer-defined scope, sensitive-group, critical-field, and SOD rules produce explicit results.
Approval is a boundary, not a button.
Customers define who can approve each system and risk class, what rules are deterministic, and which judgments must remain human.
Four-eyes / separation of duties
A decision can require different responsibilities.
An agent proposing an action does not approve it. Security, IAM, and system owners remain distinct roles, with authority defined by the customer.
SECURITYIAMSYSTEM OWNERREQUESTERV03
REVIEW
REVIEW
Do not blur check, explanation, and unknown.
Explanation
AI may organize and explain available context; it does not become the source of policy authority.
Unknown
Missing ticket, owner confirmation, or conflicting evidence remains a visible break—not invented certainty.
Version-bound
Any material content or evidence change retires the prior approval and starts review again.
Production writes remain locked.
Velqestra's initial concept produces a signed review outcome and machine-readable decision. It does not directly grant permissions or modify business records.
Approved decisions may later inform executors.
Execution, post-change verification, and compensating rollback are roadmap directions, not current capabilities claimed by this site.
Design your first review gate