Current exclusion from Submissions

Context

The binding standard requires a publication decision for business intake. Absence of binding code establishes current availability but does not approve indefinite exclusion.

Decision

The pinned module publishes no Submissions binding; configuration and reads are excluded, and custom-record intake is deferred pending a designed binding.

Alternatives Considered

Publishing record intake immediately: Current portal pause, absent member routes and missing binding preparation leave intake unfinished. Omitting compatibility classification: The standard requires an explicit publication or a recorded reason for exclusion.

Consequences

Operation rows record why no binding is published. A future configurable record-intake milestone must design and publish its binding before forms can use it.