Explicit Submissions exclusions for configuration and maintenance

Context

The service operations maintain setup, return information or perform internal lifecycle work. The publication standard requires a disposition for each operation.

Decision

Every examined Books and maintenance operation is excluded from Submissions with its own reason. None has an implemented intake binding for an external business request.

Alternatives Considered

Publish unit or term creation as intake. An intake process and capture contract would have to be designed first.

Omit publication declarations. The cited architecture standard requires either publication or an explanation.

Consequences

Each service operation records why it is unpublished.

A future form-driven setup process needs a separate capture and permission design.