Record the Absence of Published Intake Operations

Context

The operation-publication standard requires explicit contract status. Receiving Submissions decisions does not itself publish a Membership intake operation.

Decision

Current Membership operations carry an explicit non-publication reason and use the separate subject-and-decision delivery contract for Submissions integration.

Alternatives Considered

Publish staff creation and term addition as intake operations: Exposing staff term entry as applicant capture would need a review and authorization design rather than assuming staff operations are suitable.

Publish the affiliation change for members: Member chapter capture cannot be claimed while its self-service path remains unbuilt.

Consequences

Each contract exposes its current publication status for review. Any future published capture needs its own versioned contract and intake wiring. Today application creation depends on imports because the engine intake is missing.