CAPELLA / VERIFIED MISSION REPLAY
Experience CAPELLA
An interactive reconstruction of an actual verified CAPELLA engineering case — from SAP engineering intent through SFC qualification, human authorization, A4Layer execution, SAP realization and verified evidence. This is a verified mission replay, not a live SAP demo, sandbox or execution surface.
Stage 01 / 8 · Guided · Verified mission replay
Engineering intent
A person expresses the engineering goal: create a governed SAP RAP application. CAPELLA freezes this as a bounded managed RAP create mission. Nothing is generated, qualified or executed yet — this stage only fixes the objective. CAPELLA holds coordination authority; SFC owns the next step.
- What entered
- Human engineering goal
- What left
- Frozen managed RAP create mission
- What was not proven
- This stage does not prove any code was generated, qualified or executed. It only proves the mission objective was bounded.
- Next authority
- CAPELLA orchestration, then SFC qualification
Engineering lineage
Eight stages, one verified mission.
Each stage shows what happened, which authority owned it, what evidence exists and what was not proven. The interactive replay above walks these same stages; this list stays readable without it.
- 01 · CAPELLA AFEP
Engineering intent
A person expresses the engineering goal: create a governed SAP RAP application. CAPELLA freezes this as a bounded managed RAP create mission. Nothing is generated, qualified or executed yet — this stage only fixes the objective. CAPELLA holds coordination authority; SFC owns the next step.
- 02 · CAPELLA AFEP
CAPELLA orchestration
CAPELLA coordinates operator workflows, status, approvals, delivery surfaces and evidence continuity so the mission stays visible end to end. It keeps the work moving between authorities without becoming any of them. The next authority is SFC, which compiles and qualifies the delivery candidate.
- 03 · SFC 0.13.1
SFC qualification
SFC 0.13.1 compiles the managed RAP candidate and qualifies it against the current banked release. Compilation and qualification completed before any SAP-write authorization existed. A qualified candidate is still not an approved write — Govern owns the next gate.
- 04 · Govern
Govern / human approval
Govern applies the hash-bound human approval gate before any SAP-write execution. A person authorizes the exact qualified execution request; the approval is bound by hash so what is approved is exactly what runs. Govern does not execute against SAP — it authorizes a bounded execution intent.
- 05 · A4Layer 1.0.0
A4Layer execution
A4Layer 1.0.0 carries the authorized delivery intent into bounded SAP execution. The authorized carrier executed without transferring SAP authority to CAPELLA or SFC. A4Layer performs the approved work; it does not decide whether SAP accepts it.
- 06 · SAP
SAP realization
SAP determines authorization, realized object state, activation and runtime truth. In the verified mission, SAP realized the exact expected 14-object set and remained final runtime truth. If SAP had rejected the change, SAP's decision would stand and be recorded as evidence.
- 07 · SAP / Observatory
Readback + ATC
SAP readback verified the realized state against the expected object set, and ATC completed with 0 findings. Readback and ATC turn an outcome into evidence: until the realized state is verified, an outcome is not yet proof.
- 08 · Observatory
Observatory / evidence
Observatory records the authoritative engineering execution and evidence, and the bounded mission closed PASS with ATC 0 findings. The evidence is classified VERIFIED — supported by current authoritative CAPELLA evidence — with its boundary stated explicitly.
Mission completion
This is what CAPELLA means by a governed engineering outcome.
- Engineering intentqualified
- SFC 0.13.1qualification passed
- Governhuman authorization preserved
- A4Layer 1.0.0bounded execution carried
- SAPrealization + runtime truth
- ATC0 findings
- Observatoryevidence preserved
- Outcome
- 14-object bounded SAP realization
- Qualification
- SFC 0.13.1
- Authorization
- explicit human approval
- Execution
- A4Layer 1.0.0
- SAP
- realized + readback
- ATC
- 0 findings
- Claim
- bounded verified outcome
Boundary This verified case does not establish unrestricted autonomous SAP engineering. It does not claim unrestricted RAP delivery, a clean test environment, or SAP writes during the 0.6.1 release process.
The CAPELLA engineering contract
One layer never inherits another’s authority.
These invariants are CAPELLA product behaviour, consistent with the published authority model and claim taxonomy — not marketing slogans.
- Generation is not qualification
Generated managed RAP content is a candidate, not a qualified result. SFC 0.13.1 compiles and qualifies it before it can move toward a SAP-write authorization.
Verify - Qualification is not authorization
A qualified execution request still cannot become a SAP write on its own. Govern applies a hash-bound human approval bound to that exact request.
Verify - Authorization is not execution
Human approval authorizes a bounded execution intent. A4Layer 1.0.0 is the separate carrier that performs the approved execution.
Verify - Execution is not SAP authority
A4Layer carries approved intent into SAP without inheriting SAP authority. SAP determines authorization, realized object state, activation and runtime truth.
Verify - Activity is not a verified outcome
Durable run activity and lifecycle telemetry exist, but measured effectiveness does not. The public experience separates verified, demonstrated, experimental and planned.
Verify - An outcome is not evidence until it is verified
SAP readback and ATC verify the realized state against the expected object set. The verified mission recorded a 14-object realization with ATC 0 findings.
Verify - AI intelligence is not engineering authority
AI contributes across the engineering lifecycle, but SFC still qualifies, Govern still authorizes, A4Layer still executes and SAP still decides.
Verify
Product category
CAPELLA AFEP — Agentic Full-Stack Engineering Platform for SAP.
CAPELLA is the engineering control plane between AI-assisted engineering intent and governed SAP outcome. It does not replace SAP authority. Supporting category: Governed Engineering Control Plane for SAP.
- AI can generate.
- Agents can reason.
- MCP can expose tools.
- Workflow engines can orchestrate.
- SAP can authorize and execute.
CAPELLA's product role is to connect these concerns into a governed engineering lifecycle without allowing one layer to silently inherit the authority of another.
| Dimension | AI copilot | LLM / agent | Workflow automation | Low-code / app builder | CAPELLA AFEP |
|---|---|---|---|---|---|
| Generates engineering suggestions | Yes | Yes | Not inherent to the category | Product-dependent | Yes — as one stage, not the outcome |
| Deterministic qualification boundary | Not inherent to the category | Not inherent to the category | Requires external controls | Product-dependent | SFC 0.13.1 compiles and qualifies before authorization |
| Explicit human authorization boundary | Product-dependent | Requires external controls | Requires external controls | Product-dependent | Govern hash-bound approval before any SAP write |
| Separate execution authority | Not inherent to the category | Not inherent to the category | Product-dependent | Product-dependent | A4Layer 1.0.0 carrier, separate from generation and compilation |
| SAP remains final runtime authority | Not addressed by the category | Not addressed by the category | Not addressed by the category | Product-dependent | SAP determines authorization, realized state and runtime truth |
| Evidence lineage and claim classification | Not inherent to the category | Not inherent to the category | Product-dependent | Product-dependent | Observatory records evidence; every public claim carries a class |
After the replay