Reconcile export coverage at each release
What It Does
Platform activation commits its security catalog and then reconciles participant export declarations. An absent datasets property leaves a service’s registry rows alone; an explicit empty list can retire them.
The Flow
After catalog activation, collect local and remote participant declarations and invoke coverage reconciliation. Plan additions, schema-version changes, retirement and restoration while rejecting duplicate owners and conflicting recorded hashes. Apply accepted declaration and version writes with the registry-version update in one transaction.
When Something Fails
Log and count failure without failing activation. Coverage can continue to describe an earlier release. Log declaration conflicts and omit their writes. Conflicting datasets retain their previously accepted declaration. Rollback a failed coverage write and report reconciliation failure. The registry retains its preceding committed contents.
Idempotency and Concurrency
Unchanged declaration content creates no coverage write or registry-version increment. The computed plan is applied transactionally; activation sequencing supplies the expected single-release execution boundary.