Updates & propagation
Selective distribution, protected layers, rollback readiness, and queue intelligence — orchestration only.
Set NEXT_PUBLIC_DEFAULT_PROJECT_ID to run propagation actions.
Propagation planning
Choose how the shared-plane update reaches tenants. Selections are illustrative.
Targeting
Pick a distribution pattern, then refine tenant scope.
Only checked tenants receive the shared update. Best for surgical changes.
Tenant scope · 2 selected
Update preview
What moves on the shared plane vs what stays locked at the tenant edge.
Shared components
Workflow changes
Runtime impact
Protected areas
These surfaces are never overwritten by propagation — only merged at the tenant boundary.
- Branding
- Domains
- Runtime config
- Feature flags
- Tenant overrides
Tenant compatibility
Who feels this
Sidra — inherits shared UI · branding locked.
MD — receives logic bundle when job runs · domains untouched.
Sync intelligence
Operational language for drift, skips, and rollback readiness.
SidraSyncedPending update
Queued for v1.5.0 · currently synced on v1.4.2.
Protected snapshot v7 attached to next propagation job.
MDOutdatedDivergedRollback available
Diverged on shared workflow · rollback available.
Operator can restore v1.4.1 without touching tenant branding JSON.
EU pilotExperimental channelStaged
Experimental channel · staged wave 1.
Receives preview payloads before stable widen.
Archive (read-mostly)Skipped releaseInherited
Skipped v1.4.3 by policy · still inherited base.
No pending work · audit-only visibility.
Live observability requires NEXT_PUBLIC_DEFAULT_PROJECT_ID. Planning controls above stay available; timelines and metrics hydrate from the platform API once a project is bound.