Platform
The stack stays yours.
The Causance operating model brings explicit authority and reasoned decision state to consequential software change. It does not replace the systems that own your facts or your effects.
Facts → governed state → customer effects
Repositories, CI/CD, ITSM, GRC, security, cloud, runtime, observability, and customer systems remain in place. Causance evaluates bounded facts and governed decision state across explicit interfaces. This does not imply that every source has a production connector.
Identity, authority, applicable evidence, freshness, and governed controls are evaluated as explicit bounded inputs. Within implemented scope, deterministic evaluation resolves a reasoned governed state. It is not a guarantee of external behavior or business outcomes.
A decision is not self-authorization.
Customer systems retain credentials, enforcement, product ownership, deployment responsibility, emergency authority, break-glass accountability, and operational authority. Causance does not acquire those powers because a decision state is complete.
The homepage illustrates this boundary with a change that passes through a governed environment, acquires fitted structures, and crosses into a customer-controlled system. It is an explanation of the operating model, not a live deployment.
Observation and history remain distinct.
Observed state can return as evidence and be compared with the governed or intended condition. Retained historical records support inspection and bounded reconstruction and recovery within implemented scope.
History does not preserve or revive execution authority. Later action requires fresh, separately governed authority. No automatic retry, universal recovery, provider failover, or recovery-performance commitment is implied.