Change governed like any other action.
Verity Forge governs sovereign deployment and software lifecycle. Releases are signed, configuration and policy are data, and every rollout — to an enclave, an air-gapped network or an edge node — is authorized, staged, reversible and evidenced.
What it governs
- Signed releasesEvery artifact signed, so a customer can verify exactly what is installed.
- Configuration as dataEnvironment configuration versioned, reviewed and diffable.
- Policy as dataAuthority policy signed, tested and activated through the same controls.
- Deployment orchestrationOrdered rollout across services, domains and edge nodes.
- On-premises and enclave rolloutInstallation inside customer-controlled environments.
- Air-gapped update packagesSelf-contained, signed bundles verified before import.
- Edge lifecycleEnrollment, update, lease renewal and retirement of Verity Edge nodes.
- Canary deploymentChanges introduced to a subset first, with explicit promotion.
- RollbackA defined path back to the previous release for every change.
- Software bill of materialsComponent inventory delivered with each release.
- Release evidenceProvenance attestation and approval records for each deployment.
- Change controlCustomer approval of updates in sovereign postures, with quorum where policy requires.
Why lifecycle is authority
Whoever can change the software can change what the Authority Kernel decides. A platform that governs operational action but accepts unreviewed updates has moved its most powerful action outside the rules. Verity Forge closes that gap by treating a release, a configuration change and a policy change as authorized actions with their own evidence.
In sovereign postures the customer approves what is installed, and the vendor has no standing access to the environment. Reproducible builds and source inspection are available as options for customers that require them.
A release, end to end
- Build and attestSigned build, software bill of materials and provenance attestation.
- PackageOnline channel or a self-contained package for air-gapped import.
- Verify and approveSignature and provenance verified inside the customer domain; approval recorded.
- CanaryDeployed to a defined subset; promotion is an explicit, recorded decision.
- Roll out or roll backConsistent rollout across the estate, or a return to the previous release.
- EvidenceWhat is running where, installed by whose authority, reconstructable at any time.