Explicit authority
ERCC creates the reasoning contract; SFC compiles and qualifies; Govern binds authorization to the executable configuration; A4Layer executes; SAP decides runtime truth.
SAFETY / TRUST
CAPELLA’s trust position comes from explicit authority boundaries, safe stops and evidence-aware public claims.
ERCC creates the reasoning contract; SFC compiles and qualifies; Govern binds authorization to the executable configuration; A4Layer executes; SAP decides runtime truth.
Verified, demonstrated, experimental, roadmap and decision statements remain visibly distinct.
Hash-bound approval remains part of the supported SAP-write path.
Release qualification, historical outcomes and RAP-04 claim-specific runtime evidence remain separate; Observatory records evidence without granting authority.
CURRENT RELEASE TRUST RECORD
Release commit d9c02ef163c5ff0cfd2e7efcfdd20daa82dbfa57 and tag v0.7.4. Qualification recorded 0 new regressions against the qualified baseline, with historical and environment-dependent failures classified. No SAP/BTP activity is claimed for the release promotion.
TRUST INVARIANTS
CAPELLA reports operator truth in concrete engineering terms: APPROVALS are human/GOVERN decisions, OPERATIONS are machine lifecycle activity, DELIVERY is verified outcome, and EVIDENCE is observed proof.
What CAPELLA refused to do
PLAIN-LANGUAGE POSITION
PUBLIC CLAIM LANGUAGE
Every managed public record must carry one approved classification. The label states whether the record is evidence-backed, demonstrated in a bounded scope, experimental, planned, or an architectural decision.
Supported by current authoritative evidence.
Observed successfully in a stated, bounded scenario.
Observed in bounded experimentation, not general capability.
Planned direction, not present capability.
A recorded architectural or governance choice, not a capability claim.