Platform Admin Service — Sync Contract
Status: populated Owner: TBD Last updated: 2026-04-18 Companion: 16 Offline/Sync
1. Per-aggregate conflict policy
| Aggregate | Conflict policy | Rationale |
|---|---|---|
| PlatformConfig | server_authoritative | Config is platform-operator governed; no offline client mutations. |
| FeatureFlag | server_authoritative | Flag lifecycle is centrally controlled; flag decisions are evaluated on-demand. |
| HealthSource | server_authoritative | Service registration is a startup operation; no offline concept. |
2. Client caching of flag evaluations
Downstream services may cache flag evaluation results locally with the 60 s TTL established by the internal evaluate endpoint. This is a read-through cache, not a sync. On cache miss, the service calls /internal/admin/flags/:key/evaluate. On platform_admin.flag.updated.v1 event arrival (via NATS inbox), services should invalidate their local cache.
platform-admin-service does not push config or flags to offline clients. Offline clients must operate with the cached state from their last connectivity window. No conflict resolution is required because these are read-only reference data for offline clients.