설계: docs/superpowers/specs/2026-09-25-capability-module-packaging-design.md
계획/진행 기록: docs/superpowers/plans/2026-09-25-capability-module-packaging.md
- Wave 0: 규칙 고정(AGENTS.md capability 완료 기준·테스트 규칙) + 차단 결함 7건
(compose overlay 검사, redis-sdk CI job, 적용된 V9/V13 원복 + V16, @EnableScheduling,
messaging bridge 순서, prod 에러 상세 validator, sample loggers read-only)
- Wave 1: 데이터·보안 Critical 10건 (durable operation 25P02, operation 유스케이스 이동,
outbox 재인코딩, Kafka TLS/SASL, 알림 트랜잭션, SNS 서명, tus checksum, GraphQL fragment,
Redis lane, gRPC FAILED_TERMINAL)
- Wave 2: 리팩터링 잔재·실험용 자리 삭제, outbox v1 fencing(V17), 멱등성 V2 정본화
- Wave 3: 라이브러리형 코드 정리(동작하지 않는 설정·인터페이스·gate 제거, web-advanced 분리)
- Wave 4: capability 11개를 "있으면 켜짐" 모듈로 포장, 끄는 장치 제거, 기본 조립 web-only,
qualificationBootJar 분리
- Wave 5: 빌드 로직 축소(17.2k -> 10.8k줄), sample 테스트 컨벤션 적용
삭제한 코드는 docs/capability-status.md "제거된 코드" 표에 복구 커밋(208077fd)과 함께 기록.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
8.1 KiB
Notification Delivery Platform — module mapping
Source design:
docs/superpowers/specs/2026-08-10-notification-platform-design.mdSource plan:
docs/superpowers/plans/2026-08-10-notification-platform-implementation-plan.md
Why a mapping exists
The plan was written against a hypothetical repository (modules/notification/**, root package
io.backend.skeleton.notification, 31 Gradle projects). This repository is a fail-closed
19-leaf Clean Architecture template: src/settings.gradle rejects any registry that does not
contain exactly the 19 modules in src/config/architecture/modules.json, and
verifyCleanArchitectureDependencies rejects any project edge outside allowed_dependencies.
Creating 31 new Gradle projects would violate HARD-STOP #5 of AGENTS.md. The package README
anticipates this and instructs the implementer to map dependency catalog and package/file paths onto
the host repository's rules while preserving the public contracts and reliability semantics.
Every logical module of the plan is therefore implemented as a package inside the registered leaf that owns its responsibility. No public contract, evidence rule, or reliability semantic is dropped.
Logical module → registered leaf
| Plan module | Registered leaf | Package |
|---|---|---|
notification-core-api |
application-core |
dev.caskeleton.application.notification.platform.api |
notification-content-api |
application-core |
…platform.api.content |
notification-contact-api |
application-core |
…platform.contact |
notification-template-api |
application-core |
…platform.template |
notification-policy |
application-core |
…platform.policy |
notification-provider-spi |
application-core |
…platform.provider |
notification-callback-api |
application-core |
…platform.callback |
notification-inbox-api |
application-core |
…platform.inbox |
notification-admin-api |
application-core |
…platform.admin |
notification-security (ports) |
application-core |
…platform.security |
notification-observability (ports) |
application-core |
…platform.observation |
notification-dispatch-runtime |
adapter:outbound:notification |
dev.caskeleton.adapter.outbound.notification.platform.dispatch |
notification-security (AES-GCM/HMAC impl) |
adapter:outbound:notification |
…platform.security |
notification-template-thymeleaf (reference renderer) |
adapter:outbound:notification |
…platform.template |
notification-email-smtp |
adapter:outbound:notification |
…platform.provider.smtp |
notification-email-ses |
adapter:outbound:notification |
…platform.provider.ses |
notification-sms-twilio |
adapter:outbound:notification |
…platform.provider.twilio |
notification-push-fcm |
adapter:outbound:notification |
…platform.provider.fcm |
notification-push-apns |
adapter:outbound:notification |
…platform.provider.apns |
notification-webpush (transport + crypto) |
adapter:outbound:notification |
…platform.provider.webpush |
notification-webhook-extension |
adapter:outbound:notification |
…platform.provider.webhook |
notification-observability (Micrometer impl) |
adapter:outbound:notification |
…platform.observation |
notification-admin-runtime |
adapter:outbound:notification |
…platform.admin |
notification-spring-boot-starter |
adapter:outbound:notification |
…platform.autoconfigure |
notification-persistence-jpa |
adapter:outbound:persistence-jpa |
dev.caskeleton.adapter.outbound.persistence.notification.platform |
notification-inbox-jpa |
adapter:outbound:persistence-jpa |
…persistence.notification.platform.inbox |
notification-callback-mvc |
adapter:inbound:web-notification |
dev.caskeleton.adapter.inbound.web.notification.platform.callback |
notification-submission-mvc |
adapter:inbound:web-notification |
dev.caskeleton.adapter.inbound.web.notification.platform.submission |
application composition (use cases, callback bridge, config/module-defaults/notification.yml) |
composition:notification-platform |
dev.caskeleton.composition.notification |
notification-testkit |
test source sets of the owning leaves | …platform.testkit |
Dependency-direction consequences
The plan's module DAG (*-api → provider-spi/policy → runtime/adapters → starter) is preserved
by the leaf DAG that the registry already enforces:
application-core (all *-api, provider SPI, policy, callback contracts)
↑ ↑ ↑
adapter:outbound:notification adapter:outbound:persistence-jpa adapter:inbound:web-notification
↑ ↑ (→ adapter:inbound:web)
└──────────── composition:notification-platform ────┘
↑
app-bootstrap (one line)
Two plan edges cannot be expressed as project edges in this repository, and are replaced by ports:
notification-email-ses,notification-sms-twilio,notification-push-fcm,notification-push-apns,notification-webpush,notification-webhook-extension→httpclient platform.adapter-outbound-notificationis not allowed to depend onadapter-outbound-httpclient. The provider adapters therefore calldev.caskeleton.adapter.outbound.notification.platform.provider.http.NotificationHttpGateway, an adapter-local port with a JDKjava.net.http.HttpClientdefault implementation.app-bootstrapsees both leaves and is the supported place to substitute an implementation backed by the HTTP Client Platform (TLS/timeout/circuit-breaker/SSRF/dynamic-target policy reuse).notification-inbox-jpa→optional messaging outbox integration.adapter-outbound-persistence-jpamay not depend onadapter-outbound-messaging; the inbox publishes through the existing persistence outbox tables plus theNotificationInboxSignalPortapplication port, andapp-bootstrapbinds the relay.
Commit policy
AGENTS.md pins commit policy to human-only. Step 5 (git add / git commit) of every plan task
is therefore intentionally not executed by the agent; the working tree carries the change and the
human owner commits.
Runtime reachability after the R1 adapter cleanup
The application R1 contract covered by NOTIF-ADR-005 is a separate question from the abandoned
outbound implementation that had been built around it. The latter is gone: the notification leaf no
longer contains top-level catalog/, provider/, or template/ R1 adapter packages. They had no
production composition consumer and were proved only by their own fakes.
The useful rendering invariant from that experiment was not discarded. R2
platform.template.TemplateSlotPolicy now validates the final HTML against the reviewed tag and
attribute subset in addition to escaping substituted values. Active script markup, event-handler
attributes and non-HTTPS HTML links are refused.
R2 provider protocol packages remain because they implement the canonical platform SPI and have
contract tests. Their presence does not make them shipped dispatch runtimes. Current composition
reachability is SMTP and SES for dispatch, with SES also available for callback ingestion; the remaining
provider packages are extension assets until a composition contributes a ProviderRuntimeAssembler
with the settings and secret sources that family requires. See support-matrix.md for the explicit table.
R1 public types (NOTIF-ADR-005)
NOTIF-ADR-005 made ..notification.platform.. canonical. The R1 types directly under
dev.caskeleton.application.notification had no production consumer and were removed on
2026-09-25, together with the ArchUnit rule that kept the two namespaces apart. What remains there
is the simple notification port the adapter core implements — NotificationPort, Notification,
NotificationChannel. The removed types and their last commit are listed in
docs/capability-status.md under "제거된 코드".