---
id: ADR-MBR-MEM-012
title: Record the Absence of Published Intake Operations
product_area: membership
module: memberships
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Current Membership operations carry an explicit non-publication reason and use
  the separate subject-and-decision delivery contract for Submissions
  integration.
constrains:
  - SVC-MBR-MEM-memberships
  - SVC-MBR-MEM-applications
  - SVC-MBR-MEM-billing
  - SVC-MBR-MEM-commerce-participant
  - SVC-MBR-MEM-snapshots
  - SVC-MBR-MEM-events
  - SVC-MBR-MEM-history
  - RESP-MBR
origin: >-
  R2-ARCH-002 v2.0 (Andrew, 2026-10-22) rule 1: publish an operation with a
  contract version, or say why not
alternatives:
  - option: Publish staff creation and term addition as intake operations
    why_not: >-
      Exposing staff term entry as applicant capture would need a review and
      authorization design rather than assuming staff operations are suitable.
  - option: Publish the affiliation change for members
    why_not: >-
      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.
supersedes: []
evidence:
  - >-
    services-membership at 5994c270: modules/*/aws/api/*.routes.ts (no
    Submissions binding); modules/applications/contracts/subject-kinds.ts
---

# 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.