CAPELLA AFEPCapella Agentic Full-Stack Engineering Platform for SAPAsk CAPELLA

CI/CD / RELEASE ENGINEERING

Agents can prepare change. CAPELLA release controls decide what can move.

CAPELLA’s delivery lifecycle separates agent-generated engineering work, deterministic CI, trusted script verification, qualification, release-candidate control, human authorization, environment promotion, runtime verification and Observatory evidence.

See authority architecture Inspect release truth
Product releaseCAPELLA AFEP 0.7.4
Release stateRELEASED
Reviewed engineering mainddafca259728…
ClassificationPOST 0 7 4 ENGINEERING EVIDENCE

Release principle

CI success is not release authority.

CAPELLA treats CI/CD as a governed release-management system: agents may prepare engineering changes, but qualification, signed-script trust, human release authorization, environment promotion, runtime verification and Observatory evidence remain separate controls.

Website boundary

The capellaafep.com deployment lifecycle is independent from CAPELLA runtime CI/CD. Publishing this page does not deploy SAP content, activate SAP objects, promote CAPELLA runtime changes or create a new CAPELLA product release.

Engineering delivery lifecycle

From pull request to evidence, with authority checkpoints visible.

This is the public release-management model. It intentionally avoids private hostnames, secrets and internal runner details while preserving the real authority sequence.

  1. 01

    Engineering Change

    Agentic engineering / human owner

    Source changes or release-management proposal. A generated change is not approval.

  2. 02

    GitHub Pull Request

    Repository governance

    Reviewable diff, discussion, branch identity and merge lineage.

  3. 03

    Repository CI

    GitHub Actions

    Deterministic lint, test and build evidence. CI success is not production promotion.

  4. 04

    Script Signature Verification

    Trusted signer policy

    PowerShell execution trust remains Authenticode-bound before trusted-runner execution.

  5. 05

    Qualification

    SFC / release qualification

    Candidate identity, baseline comparison and evidence classification.

  6. 06

    Release Train Controller

    RTC

    Release candidate identity, lineage, supersession and environment reconciliation.

  7. 07

    Development / UT

    Runtime 8795

    Development convergence and unit-test posture; observed DOWN can be actionable when source identity is qualified.

  8. 08

    Quality / Regression / UAT

    Runtime 8793

    Regression and acceptance qualification before production promotion.

  9. 09

    Production Promotion

    Owner authorization + protected release controls

    Eligible candidate moves only under governed approval; agents do not self-promote.

  10. 10

    Runtime Verification

    Target runtime / SAP

    Deployment identity, service state and runtime truth remain separate from deployment activity.

  11. 11

    Observatory Evidence

    Observatory

    Evidence, rollback posture and post-deployment truth are recorded without overclaiming success.

Three-environment architecture

Development, Quality and Production are not the same proof state.

CAPELLA moves from Development to Quality to Production through qualified evidence and authorization. Qualification, deployment, verification and formal acceptance remain separate terms.

Development / Unit Test

Runtime 8795

development convergence and unit-test verification

RTC convergence evidence; production readiness is not implied.
Quality / Regression / UAT

Runtime 8793

regression, reconciliation and acceptance evidence

Quality evidence remains distinct from production acceptance.
Production

Runtime 8791

production runtime and final promotion target

Promotion requires protected authorization and runtime readback.

Release Train Controller

Candidate lineage, environment reconciliation and fail-closed recovery.

The Release Train Controller is described as release-management evidence. Open or unverified work is not promoted to a production capability claim.

RTC alignment

What is supported by current engineering evidence

  • Release candidate identity and lineage are explicit.
  • Supersession is treated as state, not silent replacement.
  • Environment reconciliation separates development convergence, quality readiness and production promotion.
  • PR #44 preserves fail-closed runtime identity handling: observed DOWN can be actionable; unobserved runtime or unknown identity remains UNKNOWN.
  • Runtime recovery evidence is not presented as a completed production promotion unless production verification exists.
Signed-script governance

Trusted execution is stricter than ordinary CI

  • Repository CI and trusted Windows-runner execution are different gates.
  • Executable PowerShell scripts must carry a valid Authenticode signature from the trusted signer before entering trusted execution.
  • Unsigned or invalidly signed scripts must not pass the trusted execution boundary.
  • No website deployment step grants SAP write authority or bypasses GOVERN, branch protection or owner approval.
“Generate ≠ qualify ≠ authorize ≠ execute ≠ release ≠ runtime truth.”

CAPELLA release-engineering boundary