Register an adapter release
What It Does
Adapter registration supplies the offer, supported contracts and running location that make provider work possible. The deployment presents a validated declaration, and one database transaction records it. Staff still control who can see a newly internal offer.
The Flow
When Something Fails
A refusal fails the deployment and returns its reason. No catalogue update occurs. Reject an unauthorized registration. All records remain unchanged. Reject invalid declarations before committing. No partial declaration is retained. A write error rolls back the registration; published fingerprints cannot change. Either the previous declaration remains or the complete new registration commits. Failure aborts the same transaction. The pointer cannot commit separately from the release.
Open Design Questions
Principal admission still uses a local adapter pattern. Registration lacks a product audit entry, and release administration remains ahead of its staff-screen milestone.