No Regional Operation Is Published to Submissions

Context

The cited submission architecture requires a published version or an explicit exclusion for every operation. The regional route declarations expose no submission binding.

Decision

The contract records each exclusion: configuration maintenance, existing-data reads, saved-policy preview, recalculation or bulk-job management. These reasons describe the scoped surface without approving a future intake capability.

Alternatives Considered

Expose regional definition creation to intake. The current operation maintains authorized workspace configuration; an intake use would require its own capture authority and binding.

Consequences

Future regional intake requires a separately specified submission contract and version.