설계: 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>
2.2 KiB
2.2 KiB
Experimental Promotion Checklist
A reviewer evaluates this checklist. Every technical item, then the ADR. (The
ExperimentalPromotionGate class that encoded it in main code was removed on 2026-09-25; nothing
called it.)
Technical evidence
- Compatibility — the Stable contract suite passes on the experimental target, twice, on two supported patch releases. One passing run is a coincidence.
- Security — for tenancy features, cross-tenant read and write are both proven impossible,
including through native SQL, bulk DML,
getReference, and the second-level cache. A filter that covers only entity queries covers none of those. - Failure — connection reuse does not leak tenant context; a failover does not silently route a read-after-write to a stale replica; the commit-ambiguity scenarios still behave.
- Migration — per-tenant migration is resumable after a partial failure, and rate-limited. With one schema per tenant, a run is N independent migrations and "it failed" is not an answer.
- Performance — pool capacity, replica lag under load, and per-tenant memory are measured, not estimated. Database-per-tenant fails as a sum, not as an individual pool.
Decision
- Reviewed ADR — recording what is being promised, the operational burden it carries, and what would cause it to be withdrawn.
The ADR is not a formality. The technical suites establish that something works; the ADR records that the platform should promise it, which is a different question with a different cost.
What does not count as evidence
- The version being generally available.
- The feature working in one environment.
- A passing suite that skipped because Docker was unavailable.
- A green lane whose assertions were relaxed to make it pass.
Outcomes
| Decision | Meaning |
|---|---|
BLOCKED_TECHNICAL |
at least one suite has not passed |
BLOCKED_MISSING_ADR |
evidence is complete; no reviewed decision exists |
ELIGIBLE_FOR_STABLE_REVIEW |
both; Stable review may begin |
The two blocked states are distinct because they need different work: one needs evidence, the other needs a decision.