Intent
A bounded managed RAP create mission was frozen as the engineering objective.
CAPELLA AFEP / governed SAP engineering
CAPELLA connects engineering, qualification and evidence through explicit authorization and bounded SAP execution. Built for SAP architects, engineering teams and technical leaders adopting governed AI-assisted delivery.
CAPELLA AFEP — Agentic Full-Stack Engineering Platform for SAP. Constellation particles build the CAPELLA AFEP wordmark, then reveal the governed authority chain: SFC qualification, GOVERN human authorization, A4Layer execution, SAP and OBSERVATORY evidence.
VERIFIED product execution
A validated managed RAP mission moved through SFC 0.13.1 qualification, explicit human authorization, A4Layer 1.0.0 execution, SAP realization, SAP readback and ATC with 0 findings.
A bounded managed RAP create mission was frozen as the engineering objective.
Compilation and qualification completed before any SAP-write authorization.
Human approval remained explicit and bounded to the qualified execution request.
The authorized carrier executed without transferring SAP authority to CAPELLA or SFC.
SAP realized the exact expected 14-object set and remained final runtime truth.
SAP readback verified the realized state against the expected object set.
ATC completed with 0 findings and the bounded mission closed PASS.
Bounded evidence for the supported managed RAP create path. It does not claim unrestricted RAP delivery, a clean test environment, or SAP writes during the 0.6.1 release process.
See verified engineering caseWhy a control plane is needed
CAPELLA is the engineering control plane between AI-assisted engineering intent and governed SAP outcome. It does not replace SAP authority. The engineering contract keeps generation, qualification, authorization, execution and SAP authority as distinct concerns — you can experience each boundary in the verified mission replay.
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.
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.
Human approval authorizes a bounded execution intent. A4Layer 1.0.0 is the separate carrier that performs the approved execution.
A4Layer carries approved intent into SAP without inheriting SAP authority. SAP determines authorization, realized object state, activation and runtime truth.
Durable run activity and lifecycle telemetry exist, but measured effectiveness does not. The public experience separates verified, demonstrated, experimental and planned.
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.
AI contributes across the engineering lifecycle, but SFC still qualifies, Govern still authorizes, A4Layer still executes and SAP still decides.
Current product state
CAPELLA AFEP 0.6.1 is the current locally qualified operational baseline. It is not yet an external public software release.
Locally qualified current state
Identity match PASS
Non-editable qualified wheel
0.6.1 release delta
Fail-closed release posture
Current Capability
Capability states use the existing public claim vocabulary and preserve unsupported boundaries.
Governed path across planning, generation, qualification, approval, execution, SAP readback and ATC evidence.
Deployment-ready managed RAP generator output is qualified before execution.
Delivery candidates are checked before governed SAP execution.
Human approval remains explicit and bound to the executable intent.
Approved carriers execute without transferring authority to SFC or agentic surfaces.
The realized result is verified against SAP evidence.
Durable run activity and lifecycle telemetry exist; measured effectiveness does not.
Maintain and upgrade workflows remain outside the initial supported scope.
Architecture Teaser
Evidence, Not Marketing Claims
The public experience separates what is verified, demonstrated, experimental and planned so activity does not become an unsupported capability claim.
Persistent engineering state lets teams resume prior work, inspect visible gates and preserve delivery continuity without publishing transient mission counts.
OWNER UAT
Follow the product path, inspect the architecture and keep evidence boundaries visible while reviewing the public experience.
Independent project disclosure and evidence boundaries remain part of the product record.