Current Context and ERCC
ENGINEERING_PREPARATIONVERIFIEDAuthoritative context, assumptions, unknowns and ERCC Engineering Task Contract projection are inspectable before SFC.
CAPABILITY REGISTER
CAPELLA AFEP 0.7.4 groups released product behavior into an evidence-aware capability register—not generic marketing sections.
0.7.4 capability boundary
Current Context, ERCC, typed projection, SAP preflight, canonical artifact identity, governed backend execution, Fiori delivery and runtime classification are released product capabilities. Runtime remains claim-specific and may be PLATFORM_BLOCKED.
Authoritative context, assumptions, unknowns and ERCC Engineering Task Contract projection are inspectable before SFC.
Typed field fidelity and grounded projection checks prevent silent widening before qualification.
SFC 0.13.1 qualifies candidates while SAP preflight and canonical artifact identity remain separate gates.
The executable mutation manifest and physical artifact identity are frozen before governed execution.
Human approval remains explicit, single-use and bound to the exact execution configuration.
Fiori deployment authorization is distinct from SAP-write authorization and does not silently inherit it.
Governed carrier execution, SAP generation, activation, ATC, backend readback, service publication and OData validation are represented as separate proof points.
UI5 validation/build, BSP deployment, deployment reconciliation and deployed-content verification are exposed without equating deployment with runtime execution.
Runtime registration and execution verification are classified as VERIFIED, FAILED, PLATFORM_BLOCKED or UNVERIFIED.
Operator truth, backend truth, safe resume, evidence timeline and post-realization correction keep machine activity separate from verified delivery.
Generic modification of arbitrary existing RAP applications remains outside current source-proven support.
Broader target-environment qualification remains roadmap until evidence supports it.
From claim to proof