License changes are not software updates
E4S separates entitlement from application delivery. Changing a feature or plan at the License Authority does not require publishing a new software package.
Plan / Feature Change
→
License Refresh
→
New Entitlement
→
Platform Behavior
Software update path
Software releases use the Update Authority and release tooling. Fresh installation packages are published from Layer1.
Layer1 catalog
Read public release catalog
curl -fsS https://layer1.e4s.network/catalog.json | jq .The catalog identifies published versions, channels, manifests and available artifacts.
Public signing identity
Read Layer1 public key
curl -fsS https://layer1.e4s.network/public-key.json | jq .Release channels
| Channel | Purpose |
|---|---|
| Beta | Release candidates and pre-stable validation. |
| Stable | Production-approved releases. |