ID–204 · IDENTITY
Approval should bind to the fields, not a summary.
Related identity, ticket, and business-record writes stay attached to the exact version a reviewer saw. A material edit invalidates the old decision.
REVIEW SPINE · VQ–042 · VERSION 03
Before / current stateProposed / not executed
Illustrative change setSee the change
See the change
before it becomes
the record.
Velqestra turns proposed AI-agent writes across identity and business systems into one versioned approval object.
One review object. No hidden handoff.
Deterministic checks remain distinct from AI-written explanation and from evidence that is still unknown.
NOT APPROVED
One fold. Five moments of control.
01 Capture
Receive proposed writes without holding execution authority.
02 Compare
Show field-level before and proposed-after states.
03 Evaluate
Separate policy results, explanation, and unknowns.
04 Route + export
Bind a human decision to an exact version and export evidence.
Approvers see intent. Systems receive fields.
The gap between those views is where silent scope changes and stale approvals survive.
The decision travels with the exact change.
Evidence, affected records, policy results, approvers, reason, and version remain one review object.
Put one visible fold between agent intent and the system of record.
Start with one identity or business-record write pattern. This site does not request credentials or production data.
Design your first review gate See an illustrative change set