Explicit
A person authorizes every SAP write. Qualified output cannot silently become an authorized write.
KNOWLEDGE / HUMAN AUTHORIZATION FOR SAP AI
Human authorization for AI-driven SAP engineering.
In CAPELLA AFEP, a human authorizes every SAP write through Govern’s hash-bound approval gate — applied before any SAP-write execution, with SAP as final runtime and authorization authority.
How it works
Approve exactly what will run.
CAPELLA keeps humans in decision-making positions at intent and at approval. The approval is bound by hash to the exact qualified execution request, so a person authorizes precisely what A4Layer will carry into SAP.
Hash-bound
The approval is bound by hash to the exact qualified execution request, so what is approved is exactly what runs.
Before execution
Approval sits between SFC qualification and A4Layer execution. Govern does not execute SAP itself.
SAP still decides
After the approved carrier executes, SAP makes the final authorization decision and records realized state.
Evidence
Verified in the 14-object realization.
In the verified mission, human approval remained explicit and bounded to the qualified execution request, and SAP writes during the 0.6.1 release process were zero. This is bounded evidence for the supported managed RAP create path and does not establish blanket or autonomous authorization.
CAPELLA is an independent engineering project and is not affiliated with, sponsored by, certified by or endorsed by SAP SE or its affiliates.
See it in the product
Experience the human authorization stage.
Keep exploring