Hidden instructions try to make an agent share information.
Kyber is designed to bound what an agent can reach, so a manipulated request cannot exceed its permitted access.
An agent requests another customer's records.
Access is defined per agent and per case; requests outside it are designed to be denied.
An agent sends a response or changes a record on its own.
Agents prepare the work; sending and record changes are designed to stay with a person.
Clear access.
Accountable requests.
Limit information
and actions.
information separated.
Stay within the right
account.
before access.
Validate against
permissions.
is asking.
Link requests to
an agent identity.
when needed.
Remove access when
authority changes.
and denied.
Inspect the request,
outcome and next owner.
Intended capability. Current product availability and enforcement remain unverified.
Useful work.
Limited access.
One customer case.
Two comparable requests, one allowed and one denied.
Review the permitted case, keep its draft and see what happens when another account is requested.
Prepare a response for
the assigned customer case.
and applies limits
Intended capability. Current product availability and enforcement remain unverified.
Useful work needs an access boundary and a person responsible for what happens next.