A real Microsoft Semantic Kernel v1.36.0 agent — a Kernel, plugin functions, auto function-calling — runs in-process with the Mission SDK. No mock, no sidecar approximation.
Semantic Kernel's strongest abstraction is function-calling, so we test the boundary immediately outside it. The agent invokes request_deploy(...) whenever it decides to — with no notion of whether the target is compliant or the identity authorized. ReDevOps admits the deploy only when every required compliance control for the environment is evidenced, and the Entra role permits it — then runs it as a Mission.
The real SK agent plans a deployment in every case. ReDevOps denies each one that is missing a required control or unauthorized for the environment — deny-by-default — while admitting 2 of 2 fully-evidenced, authorized deployments.
An admitted deploy still runs only through a Mission: approval held; exactly-once execution; replay reconstructs from the event ledger and fires zero extra deploys. A stateless re-run re-ships on every crash.
Effective authority is the intersection of the framework grant and the Entra role — never the union. A fully-compliant production deploy is still denied when the identity's Entra role does not permit production. The restrictive policy governs.
The gate is deterministic — the value is the enforced mechanism, not a model score. The real Semantic Kernel agent genuinely plans and invokes the deployment; what ReDevOps changes is whether that request is allowed to become a deployment.
// semantic-kernel 1.36.0 · Mission SDK 0.2.0 · Context Runtime 0.2.0 · local, no Azure cloud · github.com/redevops-io/redevops-integrations