Skip to content
All situations

A human was in the loop. They saw one green button.

The assistant says the release is ready. The reviewer sees Approve. The missing security review is nowhere to be seen.

Before they approved

Without the check

An approval that missed the point.

The reviewer trusts the recommendation. A new external connection proceeds without anyone resolving which data it can access.

Release requestFor your review

Ready to release?

The assistant recommends approval.

Approve release

One recommendation.
One very reassuring button.

Approved. Without the context.The missing review was never shown.

With ZAK checking the action

The missing information becomes the question.

Show the changed connection, completed checks, missing review and uncertainty before asking the authorised person what should happen next.

Approval matters when the person knows what they are approving.

Release requestFor your review

Ready to release?

Here is what you need to know.

What changed
A new external connection.
What we know
The functional checks passed.
What is missing
A security review of that connection.
What is uncertain
Which data the connection can access.
Why you are asked
Decide the next step before release.
A question worth asking.Request the missing review.

Here is where
the ending changes.

01

The assistant has a recommendation.

The functional checks passed, so the assistant recommends releasing the change.

02

Something still needs a person.

A new connection changes the data access question. Functional checks do not answer it.

03

Make the decision clear.

The reviewer sees why they are being asked and can request the missing security review. Their click cannot replace evidence required by the release rule.

Where could this happen
in your work?

Start with one action you would like to delegate. Work out the permission, the connection and the evidence it needs.

What would this require in practice?

The exact reviewer, authentication, decision and action binding depend on the connected workflow. This story describes the intended decision experience, not a universal approval interface.

The scenes show the decision being explained. They are not screenshots of a connected product or records of a customer incident.

Read the scope and limits