Files
clean-architecture-backend-…/docs/notification/support-matrix.md
T
DongHyeonka bbe944bd3c fix!: 재리뷰가 찾은 결함과 색인에서 빠졌던 발견 5건을 고친다
문제: 성숙도 리뷰 수정을 다시 읽은 재리뷰(Critical 0, 회귀 0)가
Important 27건·Minor 41건을 찾았다. 수정이 새로 만든 결함이 많았다.
@SystemInvoked가 권한 규칙의 탈출구가 됐고, 데모 계정 거부가 정확히
prod일 때만 걸렸고, outbox 순서 번호가 업그레이드 때 뒤로 갔고,
GraphQL union 아래 복잡도가 0이었고, 서블릿 오류 응답이 success:true로
나갔고, 호출자 deadline이 breaker를 열었다. 원래 리뷰 색인이 06 영역
발견 5건(06-10~14)을 빠뜨려 그동안 처리되지 않았다.

방법: 영역별 7묶음이 test-driven-development 절차로 실패 테스트를
먼저 쓰고 고쳤다. 결정은 재리뷰 README 4절에 적었다: 순서 번호는 V21이
기록한 전역 floor부터, 데모 계정은 local·test·demo 허용 목록,
@SystemInvoked bean은 기동 실패, complete 단계 실패는
IDEMPOTENCY_COMPLETION_UNKNOWN(결과 불명), 캐시 조건부 쓰기는 별도
SCRIPT lane, strict lane 정책은 build cache 입력, 끝나지 않는 재시도
행은 원인 코드·지표·PARKED 절차. 레지스트리가 선언만 하고 아무 코드도
내보내지 않던 redis.capability.* 지표 6개는 빼고 runbook을 실제
지표(redis.lane.*) 기준으로 고쳤다.

위험·한계: V21을 V22 없이 직접 고쳤다(어느 배포에도 아직 없음). 이
브랜치의 V21을 적용한 개발 DB는 다시 만들어야 한다. 서블릿 오류
디스패치를 보안 체인이 허용한다. 발행·저장소 포트 시그니처가 바뀌어
파생 서비스 코드가 깨진다. prod에서 fixture-로 시작하는 설정값은
기동을 막는다. httpclient failure-injection lane의 main 단계 중복
실행은 이전 결정대로 남겼다. 실제 CI runner 실행은 확인하지 못했다.

검증: ci, mainCheck, :integrationCheck, -p optional-platforms ci
integrationCheck performanceCheck, :performanceCheck, :releaseCheck
(-PgitRevision), verify-compose-profile-contracts(18 lane) 통과.
첫 실행의 실패 2건(FindSecBugs 1, sample 동시 생성 테스트의 v4 event
id)은 고친 뒤 ci·integrationCheck·mainCheck를 다시 돌려 통과했다.

Refs: docs/reviews/2026-11-03-rereview/README.md 3·4·6·7절
BREAKING CHANGE: outbox 발행 포트와 저장소 포트 시그니처, 순서 번호
첫 값(V21 floor 다음), 샘플 데모 계정 프로필 허용 목록, 새 오류 코드
IDEMPOTENCY_COMPLETION_UNKNOWN, prod의 fixture- 값 거부, 기동 rule은
static·의존 없음이어야 한다.
2026-11-03 23:29:35 +09:00

6.1 KiB

Notification support matrix

What each channel can actually prove, and what the platform refuses to claim.

The grade column is not an opinion. docs/notification/evidence-manifest.json declares which claims each grade requires and which executable artifact proves each claim, and NotificationEvidenceVerifierTest (in :adapter:outbound:notification:test) refuses a grade whose claims are not all backed by a file that exists. Raising a grade means adding the artifact first.

Five channels read Stable until 2026-08-15. Nothing in the pipeline had ever sent a request to a provider — the sandbox job's whole body was two echo statements behind continue-on-error — and no test killed a worker mid-dispatch. The protocols are implemented and their contracts are proven against real PostgreSQL; the wire and the crash are not. That is what the grade now says.

Channels

Channel Reference implementation Grade Strongest evidence the platform records by default
Email SMTP, Amazon SES API Contract implemented / runtime unqualified Provider acceptance; recipient mail-server delivery, bounce and complaint when the provider publishes events
SMS none shipped — adapter removed; the channel type stays in the application API (see docs/capability-status.md 제거된 코드) Extension Whatever the added provider adapter can prove
Mobile push (FCM, APNs) none shipped — adapter removed; the channel type stays in the application API (see docs/capability-status.md 제거된 코드) Extension Whatever the added provider adapter can prove
Web Push none shipped — adapter removed; the channel type stays in the application API (see docs/capability-status.md 제거된 코드) Extension Whatever the added provider adapter can prove
In-app inbox Own database Optional stable PERSISTED, SEEN, READ
Webhook none shipped — adapter removed; the channel type stays in the application API (see docs/capability-status.md 제거된 코드) Extension Whatever the receiving HTTP contract states

Shipped provider assembly reachability

The grade above describes protocol/reliability evidence. It does not mean every reference implementation is selectable in the default composition. Dispatch reachability is a separate axis:

Provider family Dispatch assembler in shipped composition Callback assembler Current use
SMTP yes no EMAIL dispatch reference family
SES yes yes EMAIL dispatch + SNS callback ingestion; disabled reference profile ships in config/module-defaults/notification.yml (composition:notification-platform)

APNs, FCM, Twilio, Web Push and Webhook adapters shipped as protocol code with no assembler and were removed; ProviderType now lists only SES and SMTP, so such a profile fails binding as an unknown type. An enabled dispatch profile with no assembler fails startup by profile/family; it never silently assembles into an empty runtime. SMTP additionally names spring.mail.host when its shipped assembler is absent because the relay was not configured.

What each grade requires

Grade Requires
Stable durable, multi-worker-safe, callback-supported, recoverable, provider-wire-qualified
Contract implemented / runtime unqualified durable, multi-worker-safe, callback-supported
Optional stable durable
Extension nothing; the receiving contract owns its own guarantees
Experimental nothing; the grade is the warning

recoverable is backed by two tests. WorkerCrashRecoveryContractTest walks the four phases a dispatch passes through — claimed, attempt written, request started, body committed — and pins the rows a dead worker leaves at each: a passed lease, and from the attempt insert on an unfinished attempt carrying that phase's evidence. It writes those rows itself, so it checks recovery's input, not recovery. PostgreSqlNotificationBackgroundPassIntegrationTest runs lease recovery and reconciliation over rows the dispatcher's own factory wrote and asserts the outcome: requeued before any attempt, reconciled after one (review 05-01, RR-03-07).

The remaining unmet claim, and what would meet it:

  • provider-wire-qualified — a real provider sandbox call producing an immutable, uploaded artifact with a correlation id. No request has ever left the process in CI.

Evidence levels

NONE → PLATFORM_QUEUED → PROVIDER_ACCEPTED → NETWORK_OR_CARRIER_ACCEPTED → DEVICE_DELIVERED → USER_AGENT_DISPLAYED → USER_READ

Provider signal Highest evidence it may produce
Internal queue commit PLATFORM_QUEUED
SES MessageId PROVIDER_ACCEPTED
SES Delivery NETWORK_OR_CARRIER_ACCEPTED
In-app row commit PROVIDER_ACCEPTED
In-app seen endpoint USER_AGENT_DISPLAYED
In-app read endpoint, authenticated app receipt USER_READ

Promotions the platform will not make, in code or in configuration:

  • A push or SMS acceptance, from any provider adapter a deployment adds, is not DEVICE_DELIVERED.
  • A provider 2xx is not DELIVERED.
  • An SES MessageId is not DELIVERED.
  • An SMTP 250 is not inbox delivery.

Submission outcomes

NOT_SUBMITTED, CONFIRMED_ACCEPTED, CONFIRMED_REJECTED, AMBIGUOUS.

AMBIGUOUS is a first-class stored state, not an error path. It means the request body was committed to the provider and the outcome could not be read. While an ambiguous attempt exists on a recipient delivery, automatic retry and automatic cross-channel fallback are both blocked.

Not supported

The platform will not claim any of the following, because no channel above can support them:

  • guaranteed delivery
  • guaranteed read
  • exactly-once human notification
  • unconditional multi-provider failover after an unread response
  • provider SDK types in the public API
  • audience selection, campaign segmentation or jurisdiction rulings

Target model

FCM_FID is the primary mobile push target. FCM_REGISTRATION_TOKEN_LEGACY and APNS_DEVICE_TOKEN are separate types with separate lifecycles; they are never flattened into one string field.