0.6.1
Established the preserved 0.6.1 release baseline with SFC 0.13.1 and A4Layer 1.0.0.
- Tag
- v0.6.1
- Source
d880ba41266f85ed16069c7928670983105752d9
Release Record
Operational progress with provenance.
The current product identity is CAPELLA AFEP 0.7.4 / RELEASED. Release tags and exact source identities remain visible as provenance.
0.6.2
Converged the CAPELLA AFEP product identity and preserved the qualified component stack.
- Tag
- v0.6.2
- Source
d09eadfd6bf33c9cd8baac3b683c94cb68382253
0.7.0
Promoted the ERCC-capable product line while preserving the separate SFC, authorization, execution and SAP authority boundaries.
- Tag
- v0.7.0
- Source
a542d8b1a9b08cd2feba92f134f34276756743ec
0.7.1
Released structured pre-SFC diagnostics, Current Context, ERCC topology, mission continuity, actionable Needs Review, truthful release/run identity, current-versus-historical evidence, Agentic SAP Context run selection and stage drilldown.
- Tag
- v0.7.1
- Source
da0e7d35f135325ce030cdd7cf1446b1e7a6db5b
0.7.2
Advanced historical projection and operator continuity without changing the authority model.
- Tag
- v0.7.2
- Source
1b13b490aa777c57032e7732c5610651a0e6dc07
0.7.3
Closed historical archive/import and history UX work while preserving current-versus-historical evidence separation.
- Tag
- v0.7.3
- Source
77bc5c2477ca3cd7095c4bf953c3b19d437ba4a4
0.7.4 CURRENT
Released governed backend execution, publication/OData verification, Fiori lifecycle, runtime truth, platform-limited closure, canonical artifact authority and evidence hardening.
- Tag
- v0.7.4
- Source
d9c02ef163c5ff0cfd2e7efcfdd20daa82dbfa57
Release diff explorer
0.7.1 → 0.7.2 → 0.7.3 → 0.7.4 without inventing metrics.
- What changed
- Stabilized product truth and release qualification language after ERCC/current-context introduction.
- Why it matters
- Made release evidence easier to separate from historical SAP outcome proof.
- What did not change
- No authority-model promotion from qualification to SAP execution.
- SAP/BTP activity
- No public SAP/BTP activity claim for release promotion.
- Authority model change
- No SAP authority transfer.
- Evidence / source
- Release provenance and public website truth record.
- What changed
- Expanded FullStack delivery evidence vocabulary and delivery/runtime distinction.
- Why it matters
- Prepared backend, Fiori and runtime proof surfaces without collapsing them into one success badge.
- What did not change
- GOVERN authorization and SAP runtime authority remain separate.
- SAP/BTP activity
- No public SAP/BTP activity claim for release promotion.
- Authority model change
- No new authority layer.
- Evidence / source
- Source-proven delivery semantics and claim taxonomy.
- What changed
- RAP-04 current-generation evidence, Operator Truth, platform-limited runtime vocabulary and release/current-main distinction.
- Why it matters
- Lets visitors inspect BACKEND_VERIFIED, FIORI_DEPLOYMENT, CONTENT, SERVICE_ASSOCIATION, APPINDEX and PLATFORM_BLOCKED separately.
- What did not change
- Runtime verified remains false when runtime is PLATFORM_BLOCKED.
- SAP/BTP activity
- 0 during release promotion.
- Authority model change
- No. ERCC contract remains distinct from executable mutation/config hash.
- Evidence / source
- Release commit d9c02ef163c5ff0cfd2e7efcfdd20daa82dbfa57 and current engineering main ddafca2597285a4c39818f69cb949c0d5dfb54e2 reviewed separately.
POST-0.7.4 ENGINEERING HARDENING
Source-proven hardening after the release boundary.
This is current engineering main work, not a new public release and not part of the 0.7.4 release feature claim unless separately promoted.
Publish the CAPELLA CI/CD and release-engineering architecture accurately for the final architecture-series entry, then continue runtime qualification through governed evidence. This is post-release engineering hardening and release-management evidence. It is not a new public product release, not a SAP realization claim, and not proof that production promotion or a fresh live mission completed.
- Post-0.7.4 CI/CD and Release Train Controller evidence alignment
- PR44 8795 DOWN convergence classification repair
- 8791 launcher commit-pin refresh
- Ownership projection parity on the Step 18 fixture session
- E2E regression readiness with zero SAP-write claim
- Environment preflight self-heal
- FullStack status/readback
- Post-realization correction
- Fiori restart and wake recovery
- Fiori authorization UX
- Deployment reconciliation UX
- BAS-SSH deployment carrier
- Validation-failure recovery
- Runtime re-verification
- Platform-limited terminal-status clarity
- Canonical operator shell convergence