Engineering intent
Start with the SAP engineering outcome and the authority posture it requires.
CAPELLA AFEP / governed SAP engineering
CAPELLA connects engineering, qualification and evidence through explicit authorization and bounded SAP execution.
CAPELLA software logo resolving into the authority system for SFC, governance, A4Layer, SAP and evidence.
Product in action
One engineering journey. Explicit authority at every handoff.
Start with the SAP engineering outcome and the authority posture it requires.
Keep the mission state, gates and handoffs visible as work resumes.
Compile and qualify managed RAP candidates before any write path.
Preserve hash-bound human approval as a deliberate step.
Carry approved intent through the non-editable qualified carrier.
Treat SAP authorization and realized state as final authority.
Keep proof attached to engineering work and outcome claims.
Governed Engineering Journey
Intent, engineering, qualification, approval, execution, SAP truth and evidence move as one continuous product experience.
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.