Customization registry and configuration service
What the Service Owns
This service keeps customization declarations, reusable handlers and scoped bindings. Hosts resolve and invoke those bindings through the shared library; their invocation-writer role permits recording outcomes without transferring ownership of business records.
Operations
The operation rows define the callable boundary, its access class, exact permission declarations and planning coverage. Configuration and operational administration are not published as intake captures. Public health and provider callbacks retain their declared access boundaries.
Consistency and Failure
An application’s registry replacement and the resulting binding orphaning either commit together or leave the prior declaration intact. Refused registrations retain the earlier registry.
Handler and binding database mutations include their security audit writes; external secret calls cannot be rolled back with those writes. A successful secret mutation can outlive a failed database commit. Deletion requests allow seven days of recovery.
Hosts observe a configuration edit when they next resolve the point. No background correction is provided.
Events and Jobs
The declarations distinguish application events, incoming requests, queue work and direct host reads. These are different transport boundaries; registering a declaration does not by itself publish an application event.
Open Questions
Secret storage is outside database rollback. The console contracts describe mock previews, and actual handler testing remains less complete than production invocation. No scoped operation calls a language model.