Registries are written only by deploy-time manifests

Context

The broader registry pattern is proposed; an approved workflow registry decision does not approve every other registration.

Decision

Receive registry declarations from deployment. Extension and workflow manifests retire omissions; adapter registration changes a named release and deployment; application consumer registration replaces that application’s consumer.

Alternatives Considered

Allow registry edits through administration screens. Configuration could diverge from the code implementing its contract.

Consequences

Declarations reflect the last accepted registration, with replacement scope determined by the service.

Extension registration trusts a supplied owner name rather than authenticating that owner, which remains a defect.

Registration changes leave row stamps and deployment logs but no audit event.