diff --git a/docs/registries/capabilities.yaml b/docs/registries/capabilities.yaml index 2fc161d4..157c27b8 100644 --- a/docs/registries/capabilities.yaml +++ b/docs/registries/capabilities.yaml @@ -3,24 +3,24 @@ # Owner branch: feature-repository-access-permission-contract # Last updated: 2026-06-05 # -# Notes -# - capability는 사용자 권한이 아니라 application use case가 infrastructure capability를 -# 사용할 수 있는지에 대한 계약 (feature-repository-access-permission-contract). -# - enforcement default = ArchUnit annotation-based rule. compile-time annotation processor는 -# alternative. runtime AOP는 forbidden. -# - capability 제거는 항상 breaking change. 추가는 additive (registry row 동반 시). -# - annotation 표기 (as-built, F1/F2 reconciled 2026-06-05): 코드 SSOT는 단일 -# `@UseCaseCapability` (TYPE target, typed attribute). 노트 D2/D11의 flat -# `@UseCaseRepositoryAccess(Capability[])` 모델은 superseded. 7 capability ↔ as-built 매핑: +# 읽는 법 +# - capability는 사용자 권한이 아니라, application use case가 인프라 기능을 쓸 수 있는지에 대한 +# 계약이다 (feature-repository-access-permission-contract). +# - 강제(enforcement) 기본값 = annotation을 보는 ArchUnit 규칙. compile-time annotation processor는 +# 대안이다. runtime AOP는 쓰지 않는다. +# - capability를 지우면 언제나 breaking change다. 더하는 것은 additive다(registry 행을 같이 더할 때). +# - annotation 표기 (구현된 모양, F1/F2를 2026-06-05에 맞춤): 코드의 정본은 `@UseCaseCapability` 하나다 +# (TYPE target, 타입이 있는 속성). 노트 D2/D11의 평평한 `@UseCaseRepositoryAccess(Capability[])` +# 모델은 대체됐다. capability와 구현된 속성의 대응: # READ_REPOSITORY/WRITE_REPOSITORY → repositoryAccess, TRANSACTION_REQUIRED → transactionMode, # EXTERNAL_OUTBOUND_ALLOWED → externalOutboundAllowed, SENSITIVE_READ → sensitiveRead, # BULK_WRITE → bulkWrite, CROSS_TENANT_ADMIN → crossTenantAdmin. -# 각 row의 annotation: 필드는 아래에서 as-built 표기로 정합됨. +# 각 행의 annotation: 칸은 아래에서 구현된 표기로 맞췄다. capabilities: - # source: feature-repository-access-permission-contract — 판정 기준 "Required capability: READ_REPOSITORY" - # source: feature-application-port-usecase-contract — "read-only query use case는 readOnly 와 READ_REPOSITORY capability만 선언 가능" + # 출처: feature-repository-access-permission-contract — 판정 기준 "Required capability: READ_REPOSITORY" + # 출처: feature-application-port-usecase-contract — "read-only query use case는 readOnly 와 READ_REPOSITORY capability만 선언 가능" - name: READ_REPOSITORY scope: use_case_method enforcement: archunit @@ -32,8 +32,8 @@ capabilities: compatibility_impact: breaking required_test: architecture-enforcement:read-repository-capability - # source: feature-repository-access-permission-contract — 판정 기준 "Required capability: WRITE_REPOSITORY" - # source: feature-application-port-usecase-contract — "write use case는 transactionMode, idempotency, repositoryAccess를 명시해야 함" + # 출처: feature-repository-access-permission-contract — 판정 기준 "Required capability: WRITE_REPOSITORY" + # 출처: feature-application-port-usecase-contract — "write use case는 transactionMode, idempotency, repositoryAccess를 명시해야 함" - name: WRITE_REPOSITORY scope: use_case_method enforcement: archunit @@ -45,8 +45,8 @@ capabilities: compatibility_impact: breaking required_test: architecture-enforcement:write-repository-capability - # source: feature-repository-access-permission-contract — decisions 2026-05-22 - # "SENSITIVE_READ marker = registry-managed metadata table (entity FQN + field name 단위)" + # 출처: feature-repository-access-permission-contract — decisions 2026-05-22 + # "SENSITIVE_READ marker = registry-managed metadata table (entity FQN + field name 단위)" - name: SENSITIVE_READ scope: use_case_method enforcement: archunit @@ -58,8 +58,8 @@ capabilities: compatibility_impact: breaking required_test: architecture-enforcement:sensitive-read-capability - # source: feature-repository-access-permission-contract — decisions 2026-05-22 - # "BULK_WRITE threshold = N > 100 또는 batch size > 100. 미만은 일반 WRITE_REPOSITORY로 충분" + # 출처: feature-repository-access-permission-contract — decisions 2026-05-22 + # "BULK_WRITE threshold = N > 100 또는 batch size > 100. 미만은 일반 WRITE_REPOSITORY로 충분" - name: BULK_WRITE scope: use_case_method enforcement: archunit @@ -71,9 +71,9 @@ capabilities: compatibility_impact: breaking required_test: architecture-enforcement:bulk-write-capability - # source: feature-repository-access-permission-contract — decisions 2026-05-22 - # "TRANSACTION_REQUIRED는 application-port branch의 TransactionPort contract와 연결되어야 하며 Spring @Transactional 직접 import로 충족하지 않음" - # source: feature-application-port-usecase-contract — TransactionPort Contract + # 출처: feature-repository-access-permission-contract — decisions 2026-05-22 + # "TRANSACTION_REQUIRED는 application-port branch의 TransactionPort contract와 연결되어야 하며 Spring @Transactional 직접 import로 충족하지 않음" + # 출처: feature-application-port-usecase-contract — TransactionPort Contract - name: TRANSACTION_REQUIRED scope: use_case_method enforcement: archunit @@ -85,9 +85,9 @@ capabilities: compatibility_impact: breaking required_test: architecture-enforcement:transaction-required-capability - # source: feature-repository-access-permission-contract — decisions 2026-05-22 - # "EXTERNAL_OUTBOUND_ALLOWED 분류 = outbox row INSERT는 in-process(불요), polling publisher의 broker publish는 outbound(필요)" - # source: feature-application-port-usecase-contract — "outbound adapter 호출 use case에 EXTERNAL_OUTBOUND_ALLOWED가 없으면 실패" + # 출처: feature-repository-access-permission-contract — decisions 2026-05-22 + # "EXTERNAL_OUTBOUND_ALLOWED 분류 = outbox row INSERT는 in-process(불요), polling publisher의 broker publish는 outbound(필요)" + # 출처: feature-application-port-usecase-contract — "outbound adapter 호출 use case에 EXTERNAL_OUTBOUND_ALLOWED가 없으면 실패" - name: EXTERNAL_OUTBOUND_ALLOWED scope: use_case_method enforcement: archunit @@ -99,8 +99,8 @@ capabilities: compatibility_impact: breaking required_test: architecture-enforcement:external-outbound-capability - # source: feature-repository-access-permission-contract — decisions 2026-05-22 - # "CROSS_TENANT_ADMIN capability를 capability vocabulary에 추가 (tenant branch feature-tenant-context-policy와 cross-link)" + # 출처: feature-repository-access-permission-contract — decisions 2026-05-22 + # "CROSS_TENANT_ADMIN capability를 capability vocabulary에 추가 (tenant branch feature-tenant-context-policy와 cross-link)" - name: CROSS_TENANT_ADMIN scope: use_case_method enforcement: archunit diff --git a/docs/registries/env-keys.yaml b/docs/registries/env-keys.yaml index 6536d1ae..9fc9fb82 100644 --- a/docs/registries/env-keys.yaml +++ b/docs/registries/env-keys.yaml @@ -3,30 +3,30 @@ # Owner branch: feature-env-driven-runtime-configuration # Last updated: 2026-09-25 # -# Conventions: -# - Application-owned env uses `APP_` prefix, fully unified (D2, 2026-06-05): -# datasource/server/etc. keys that map onto Spring properties are renamed APP_* -# as well (e.g. SERVER_PORT -> APP_SERVER_PORT). -# - Only env the Spring runtime reads natively stays native: SPRING_* and -# SPRING_PROFILES_ACTIVE (D6 — profile selector is Spring-native, not APP_). -# - `classification: secret` rows only reference secrets-classification.yaml; full row owned there. -# - reload_policy default = `restart-only` (env-driven branch "config reload: no runtime reload"). -# - boolean encoding = true/false only (env-driven branch 2026-05-22). -# - Duration encoding = Spring shorthand (`30s`); ISO-8601 (`PT30S`) forbidden (env-driven branch 2026-05-22). -# - DataSize encoding = `10MB` (env-driven branch 2026-05-22). +# 표기 규칙 +# - 애플리케이션이 가진 env는 모두 `APP_` 접두어를 쓴다(D2, 2026-06-05). Spring 속성으로 이어지는 +# datasource·server 등의 키도 APP_*로 바꿨다(예: SERVER_PORT -> APP_SERVER_PORT). +# - Spring 런타임이 직접 읽는 env만 원래 이름으로 둔다: SPRING_*와 SPRING_PROFILES_ACTIVE +# (D6 — profile 선택자는 APP_가 아니라 Spring 자체 이름이다). +# - `classification: secret` 행은 secrets-classification.yaml을 가리키기만 한다. 행 전체는 그 파일이 가진다. +# - reload_policy 기본값 = `restart-only` (env-driven branch "config reload: no runtime reload" — 실행 중 +# 다시 읽지 않는다). +# - boolean 값은 true/false만 쓴다 (env-driven branch 2026-05-22). +# - Duration 값은 Spring 줄임 표기(`30s`)다. ISO-8601(`PT30S`)은 쓰지 않는다 (env-driven branch 2026-05-22). +# - DataSize 값은 `10MB` 꼴이다 (env-driven branch 2026-05-22). +# - required_when은 둘 중 하나다. `<속성>=<값>` 꼴(공백 없음)은 테스트가 그 조건에서 기동 실패를 확인하고, +# 공백이 든 설명 꼴은 사람이 읽는 조건이다(RequiredWhenIsEnforcedTest). env_keys: - # === Profile / Identity (feature-env-driven-runtime-configuration) === + # === Profile / 정체성 (feature-env-driven-runtime-configuration) === - name: SPRING_PROFILES_ACTIVE - # source: feature-env-driven-runtime-configuration D6 (2026-06-06), amended by - # five-adapter-runtime-remediation §7.1. Profile selector is Spring-native and sole - # (APP_PROFILE was dropped). Exactly one value, not a CSV list: two environments cannot both - # have their safety rules apply, and whichever lost did so silently. + # 출처: feature-env-driven-runtime-configuration D6 (2026-06-06), five-adapter-runtime-remediation §7.1에서 + # 고침. profile 선택자는 Spring 자체 키 하나뿐이다(APP_PROFILE은 지웠다). CSV 목록이 아니라 값 정확히 + # 하나다: 두 환경의 안전 규칙이 함께 적용될 수 없고, 진 쪽은 소리 없이 빠졌다. type: enum - # No default. A profile that is guessed is a deployment nobody chose: a jar started - # with none used to become local, which before persistence was gated also meant an - # in-memory database that loses every write on restart. + # 기본값이 없다. 짐작한 profile은 아무도 고르지 않은 배포다: 예전에는 profile 없이 띄운 jar가 local이 + # 됐고, 영속성을 조건으로 묶기 전에는 재기동 때 쓴 것을 모두 잃는 in-memory DB이기도 했다. allowed_values: [local, dev, prod] classification: public-config required: true @@ -36,12 +36,12 @@ env_keys: compatibility_impact: behavior-change required_test: env-contract:profile-active - # APP_PROFILE intentionally removed (D6, 2026-06-06): profile = SPRING_PROFILES_ACTIVE - # alone. A duplicate APP_PROFILE would only add information doubling + mismatch-fail - # cost. See design record feature-env-driven-runtime-configuration Claims (wont-fix). + # APP_PROFILE은 일부러 지웠다 (D6, 2026-06-06): profile = SPRING_PROFILES_ACTIVE 하나. APP_PROFILE을 + # 따로 두면 같은 정보를 두 번 두고, 어긋날 때 실패하는 비용만 늘어난다. 설계 기록 + # feature-env-driven-runtime-configuration Claims (wont-fix) 참고. - name: APP_NAME - # source: feature-env-driven-runtime-configuration 2026-05-22 + # 출처: feature-env-driven-runtime-configuration 2026-05-22 # "Required config: APP_NAME, APP_PROFILE..." type: string default: null @@ -54,12 +54,13 @@ env_keys: compatibility_impact: behavior-change required_test: env-contract:app-name-present - # === HTTP server (APP_ unified per D2) === + # === HTTP 서버 (D2에 따라 APP_로 통일) === - name: APP_SERVER_PORT - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — full APP_ - # unification; server.port maps from APP_SERVER_PORT. - # + feature-management-actuator-security-contract 2026-05-22 "management port default = 9001 (separate from app 8080)" + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_로 전부 통일. server.port는 + # APP_SERVER_PORT에서 온다. + # + feature-management-actuator-security-contract 2026-05-22 "management port default = 9001 (separate from app 8080)" + # (관리 포트 기본값 9001, 앱 8080과 분리) type: int default: 8080 allowed_values: null @@ -72,7 +73,7 @@ env_keys: required_test: env-contract:server-port-bound - name: MANAGEMENT_SERVER_PORT - # source: feature-management-actuator-security-contract 2026-05-22 + # 출처: feature-management-actuator-security-contract 2026-05-22 # "management port default = 9001 (separate from app 8080). single-port는 platform ingress 보호 + 문서화 시만 허용." type: int default: 9001 @@ -86,8 +87,8 @@ env_keys: required_test: actuator-contract:management-port-separated - name: APP_SERVER_SHUTDOWN - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (server.shutdown mode; graceful drains in-flight requests) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (server.shutdown 방식. graceful은 처리 중인 요청을 끝내고 내린다) type: enum default: graceful allowed_values: [graceful, immediate] @@ -100,9 +101,9 @@ env_keys: required_test: env-contract:server-shutdown-mode - name: APP_SERVER_SHUTDOWN_TIMEOUT - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification. - # Supersedes the old APP_SHUTDOWN_TIMEOUT row. Must stay <= k8s - # terminationGracePeriod (cross-ref feature-container-runtime-contract). + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일. + # 옛 APP_SHUTDOWN_TIMEOUT 행을 대신한다. k8s terminationGracePeriod 이하여야 한다 + # (feature-container-runtime-contract 참고). type: duration default: 30s allowed_values: null @@ -115,11 +116,11 @@ env_keys: required_test: env-contract:server-shutdown-timeout-aligned - name: APP_SERVER_FORWARD_HEADERS_STRATEGY - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification. - # Fail closed: forwarded headers are trusted only when a deployment opts in behind a - # sanitizing/trusted proxy. native = Tomcat RemoteIpValve, which honours them only from - # peers matching server.tomcat.remoteip.internal-proxies. framework is not allowed: its - # ForwardedHeaderFilter believes every peer, and the rate limiter refuses to start on it. + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일. + # 기본은 닫힘(fail closed): forwarded 헤더는 배포가 정리·신뢰 proxy 뒤에서 직접 켤 때만 믿는다. + # native = Tomcat RemoteIpValve. server.tomcat.remoteip.internal-proxies에 맞는 상대에게서 온 헤더만 + # 따른다. framework는 허용하지 않는다: 그 ForwardedHeaderFilter는 모든 상대를 믿고, rate limiter가 + # 그 값으로는 기동을 거부한다. type: enum default: none allowed_values: [none, native] @@ -132,8 +133,8 @@ env_keys: required_test: env-contract:server-forward-headers-strategy - name: APP_SERVER_TOMCAT_MAX_THREADS - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (ceiling on concurrent request workers) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (동시 요청 worker 상한) type: int default: 200 allowed_values: null @@ -146,8 +147,8 @@ env_keys: required_test: env-contract:tomcat-max-threads-bounded - name: APP_SERVER_TOMCAT_MIN_SPARE_THREADS - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (idle worker pool floor) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (쉬는 worker pool의 하한) type: int default: 10 allowed_values: null @@ -160,8 +161,8 @@ env_keys: required_test: env-contract:tomcat-min-spare-threads-valid - name: APP_SERVER_TOMCAT_ACCEPT_COUNT - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (OS-level backlog queue depth for incoming TCP connections) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (들어오는 TCP 연결의 OS backlog queue 깊이) type: int default: 100 allowed_values: null @@ -174,8 +175,8 @@ env_keys: required_test: env-contract:tomcat-accept-count-valid - name: APP_SERVER_TOMCAT_MAX_CONNECTIONS - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (hard cap on simultaneously open connections) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (동시에 열린 연결 수의 상한) type: int default: 8192 allowed_values: null @@ -188,8 +189,8 @@ env_keys: required_test: env-contract:tomcat-max-connections-bounded - name: APP_SERVER_TOMCAT_CONNECTION_TIMEOUT - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (connection timeout for the Tomcat connector) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (Tomcat connector 연결 timeout) type: duration default: 20s allowed_values: null @@ -202,8 +203,8 @@ env_keys: required_test: env-contract:tomcat-connection-timeout-set - name: APP_SERVER_COMPRESSION_ENABLED - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (server.compression toggle) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (server.compression 켜고 끄기) type: boolean default: true allowed_values: [true, false] @@ -216,8 +217,8 @@ env_keys: required_test: env-contract:server-compression-toggle - name: APP_SERVER_COMPRESSION_MIN_RESPONSE_SIZE - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (payloads below this threshold are not compressed) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (이 크기보다 작은 응답은 압축하지 않는다) type: data_size default: 1KB allowed_values: null @@ -230,8 +231,8 @@ env_keys: required_test: env-contract:server-compression-min-size - name: APP_SERVER_ERROR_INCLUDE_STACKTRACE - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (spring.web.error.include-stacktrace policy) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (spring.web.error.include-stacktrace 정책) type: enum default: never allowed_values: [always, never, on_param] @@ -244,8 +245,8 @@ env_keys: required_test: env-contract:server-error-stacktrace-policy - name: APP_SERVER_ERROR_INCLUDE_MESSAGE - # source: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ unification - # (spring.web.error.include-message policy) + # 출처: feature-env-driven-runtime-configuration D2 (2026-06-05) — APP_ 통일 + # (spring.web.error.include-message 정책) type: enum default: never allowed_values: [always, never, on_param] @@ -258,13 +259,13 @@ env_keys: required_test: env-contract:server-error-message-policy - name: APP_MULTI_INSTANCE_ENABLED - # source: feature-env-driven-runtime-configuration D8 (2026-06-06) - # When true, StartupSafetyValidator (a StartupRule, run before any other singleton) - # requires a cross-instance DistributedLockPort bean named distributedLockProvider, - # else startup fails (exit 72). Consumed - # by feature-runtime-health-lifecycle-contract, feature-background-job-async-contract, - # feature-cache-consistency-contract, feature-domain-event-outbox-contract, - # feature-rate-limit-idempotency-contract, feature-migration-startup-contract. + # 출처: feature-env-driven-runtime-configuration D8 (2026-06-06) + # true면 StartupSafetyValidator(다른 singleton보다 먼저 도는 StartupRule)가 이름이 + # distributedLockProvider인 인스턴스 간 DistributedLockPort bean을 요구한다. 없으면 기동이 실패한다 + # (exit 72). 이 값을 쓰는 곳: feature-runtime-health-lifecycle-contract, + # feature-background-job-async-contract, feature-cache-consistency-contract, + # feature-domain-event-outbox-contract, feature-rate-limit-idempotency-contract, + # feature-migration-startup-contract. type: boolean default: false allowed_values: [true, false] @@ -277,9 +278,9 @@ env_keys: required_test: env-contract:multi-instance-beans-present - name: APP_MIGRATION_ON_STARTUP - # source: feature-migration-startup-contract - # When true, Flyway migrations are executed automatically during application startup. - # When false, migrations are bypassed (delegated to out-of-app container/pipeline jobs). + # 출처: feature-migration-startup-contract + # true면 애플리케이션이 기동하면서 Flyway migration을 자동으로 돌린다. + # false면 migration을 건너뛴다(앱 밖의 container·pipeline job에 맡긴다). type: boolean default: true allowed_values: [true, false] @@ -294,8 +295,9 @@ env_keys: # === Datasource / pool (env-driven branch "Required config: datasource") === - name: APP_DATASOURCE_URL - # source: feature-env-driven-runtime-configuration "Required config: datasource" - # + feature-persistence-failure-baseline "datasource/pool/timeout/connection exhaustion log field" + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" + # + feature-persistence-failure-baseline "datasource/pool/timeout/connection exhaustion log field" + # (datasource·pool·timeout·연결 고갈 로그 필드) type: url default: null allowed_values: null @@ -308,7 +310,7 @@ env_keys: required_test: env-contract:datasource-url-resolvable - name: APP_DATASOURCE_USERNAME - # source: feature-env-driven-runtime-configuration "Required config: datasource" + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" type: string default: null allowed_values: null @@ -321,8 +323,8 @@ env_keys: required_test: env-contract:datasource-credential-present - name: APP_DATASOURCE_PASSWORD - # source: feature-env-driven-runtime-configuration "Required config: datasource" - # + feature-secrets-config-source-contract — secret 분류로 secrets-classification.yaml에서 owns + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" + # + feature-secrets-config-source-contract — secret 분류라 secrets-classification.yaml이 행을 가진다 type: string default: null allowed_values: null @@ -335,8 +337,8 @@ env_keys: required_test: secrets-contract:db-password-not-leaked - name: APP_PERSISTENCE_VENDOR - # source: persistence vendor selector used by application-local.yml and bootRunH2. - # PostgreSQL is the shipped default; H2 is an explicit developer-only selection. + # 출처: application-local.yml과 bootRunH2가 쓰는 영속성 vendor 선택자. + # PostgreSQL이 기본으로 들어 있고, H2는 개발자가 명시적으로 고를 때만 쓴다. property: app.persistence.vendor type: enum default: postgresql @@ -379,10 +381,10 @@ env_keys: required_test: jpa-contract:realtime-replay-env - name: APP_FLYWAY_ENABLED - # source: local PostgreSQL parity / explicit H2 developer lane. - # Every profile runs migrations by default — the persistence-jpa module default reads this key - # (07-08; dev/prod no longer pin a literal over it); bootRunH2 disables them because the - # migration tree is PostgreSQL-specific. + # 출처: 로컬 PostgreSQL을 운영과 맞춤 / 명시적 H2 개발 lane. + # 모든 profile이 기본으로 migration을 돌린다 — persistence-jpa 모듈 기본값이 이 키를 읽는다 + # (07-08; dev/prod가 그 위에 값을 박지 않는다). bootRunH2는 migration tree가 PostgreSQL 전용이라 + # 끈다. property: spring.flyway.enabled type: boolean default: true @@ -396,8 +398,8 @@ env_keys: required_test: jpa-contract:local-flyway-parity - name: APP_DATASOURCE_POOL_MAX_SIZE - # source: feature-env-driven-runtime-configuration "datasource/pool env" - # + feature-persistence-failure-baseline "Hikari metric 노출 기준" + # 출처: feature-env-driven-runtime-configuration "datasource/pool env" + # + feature-persistence-failure-baseline "Hikari metric 노출 기준" type: int default: 10 allowed_values: null @@ -410,7 +412,7 @@ env_keys: required_test: env-contract:pool-bounded - name: APP_DATASOURCE_POOL_MIN_IDLE - # source: feature-env-driven-runtime-configuration "datasource/pool env" + # 출처: feature-env-driven-runtime-configuration "datasource/pool env" type: int default: 2 allowed_values: null @@ -423,13 +425,13 @@ env_keys: required_test: env-contract:pool-min-idle-valid - name: APP_DATASOURCE_CONNECTION_TIMEOUT - # source: feature-env-driven-runtime-configuration "datasource/pool env" - # + feature-persistence-failure-baseline "Hikari Alert Threshold: pool wait p99 > 100ms" - # unit: milliseconds. It feeds spring.datasource.hikari.connection-timeout, which binds onto - # HikariConfig#setConnectionTimeout(long) — a duration shorthand such as "5s" does not bind and - # fails the boot. This row said `duration` / `5s`, application.yml copied that default, and - # every prod and dev deployment refused to start; five-adapter-runtime-remediation Wave 2 found - # it in the prod-smoke lane. Corrected to what the property actually accepts. + # 출처: feature-env-driven-runtime-configuration "datasource/pool env" + # + feature-persistence-failure-baseline "Hikari Alert Threshold: pool wait p99 > 100ms" + # 단위: 밀리초. 이 값은 spring.datasource.hikari.connection-timeout으로 가고, 그 키는 + # HikariConfig#setConnectionTimeout(long)에 바인딩된다 — "5s" 같은 duration 줄임 표기는 바인딩되지 않아 + # 기동이 실패한다. 이 행이 `duration` / `5s`라 했고, application.yml이 그 기본값을 복사했고, 모든 prod·dev + # 배포가 기동을 거부했다. five-adapter-runtime-remediation Wave 2가 prod-smoke lane에서 찾았다. 실제로 + # 받는 값으로 고쳤다. type: integer default: 5000 allowed_values: null @@ -442,8 +444,8 @@ env_keys: required_test: env-contract:connection-timeout-set - name: APP_DATASOURCE_DRIVER - # source: feature-env-driven-runtime-configuration "Required config: datasource" - # (JDBC driver class for the configured datasource URL) + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" + # (설정한 datasource URL의 JDBC driver class) type: string default: org.postgresql.Driver allowed_values: null @@ -456,8 +458,8 @@ env_keys: required_test: env-contract:datasource-driver-set - name: APP_DATASOURCE_DDL_AUTO - # source: feature-env-driven-runtime-configuration "Required config: datasource" - # (Hibernate ddl-auto; prod must be validate|none, local update convenient) + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" + # (Hibernate ddl-auto. prod는 validate|none이어야 하고, local은 update가 편하다) type: enum default: validate allowed_values: [none, validate, update, create, create-drop] @@ -470,8 +472,8 @@ env_keys: required_test: env-contract:datasource-ddl-auto-safe - name: APP_DATASOURCE_SHOW_SQL - # source: feature-env-driven-runtime-configuration "Required config: datasource" - # (echo SQL to logs) + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" + # (SQL을 로그에 찍는다) type: boolean default: false allowed_values: [true, false] @@ -484,8 +486,8 @@ env_keys: required_test: env-contract:datasource-show-sql-toggle - name: APP_DATASOURCE_FORMAT_SQL - # source: feature-env-driven-runtime-configuration "Required config: datasource" - # (pretty-print SQL — only useful when SHOW_SQL=true) + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" + # (SQL을 보기 좋게 찍는다 — SHOW_SQL=true일 때만 쓸모 있다) type: boolean default: false allowed_values: [true, false] @@ -498,8 +500,8 @@ env_keys: required_test: env-contract:datasource-format-sql-toggle - name: APP_DATASOURCE_OPEN_IN_VIEW - # source: feature-env-driven-runtime-configuration "Required config: datasource" - # (Hibernate OSIV — don't enable in prod) + # 출처: feature-env-driven-runtime-configuration "Required config: datasource" + # (Hibernate OSIV — prod에서 켜지 않는다) type: boolean default: false allowed_values: [true, false] @@ -512,8 +514,8 @@ env_keys: required_test: env-contract:datasource-open-in-view-toggle - name: APP_DATASOURCE_POOL_IDLE_TIMEOUT - # source: feature-env-driven-runtime-configuration "datasource/pool env" - # (Hikari milliseconds; idle connection eviction threshold) + # 출처: feature-env-driven-runtime-configuration "datasource/pool env" + # (Hikari 밀리초. 쉬는 연결을 내보내는 기준) type: int default: 600000 allowed_values: null @@ -526,8 +528,8 @@ env_keys: required_test: env-contract:pool-idle-timeout-valid - name: APP_DATASOURCE_POOL_MAX_LIFETIME - # source: feature-env-driven-runtime-configuration "datasource/pool env" - # (Hikari milliseconds; max lifetime — rotate before broker timeout) + # 출처: feature-env-driven-runtime-configuration "datasource/pool env" + # (Hikari 밀리초. 연결 최대 수명 — broker timeout 전에 교체한다) type: int default: 1800000 allowed_values: null @@ -539,14 +541,14 @@ env_keys: compatibility_impact: behavior-change required_test: env-contract:pool-max-lifetime-valid - # === Tracing / Observability (feature-distributed-tracing-contract) === + # === 추적 / 관측 (feature-distributed-tracing-contract) === - name: OTEL_EXPORTER_OTLP_ENDPOINT - # source: feature-distributed-tracing-contract 2026-05-22 + # 출처: feature-distributed-tracing-contract 2026-05-22 # "Micrometer Tracing + OpenTelemetry exporter를 기본 기준으로 둠" - # OTLP base address (OpenTelemetry spec). TracingEnvironmentPostProcessor bridges it to - # management.opentelemetry.tracing.export.otlp.endpoint as /v1/traces (OTLP/HTTP); - # blank = no span exporter bean (review 07-01, 2026-11-01). + # OTLP 기본 주소(OpenTelemetry 규격). TracingEnvironmentPostProcessor가 이 값을 + # management.opentelemetry.tracing.export.otlp.endpoint의 /v1/traces(OTLP/HTTP)로 잇는다. + # 빈 값 = span exporter bean 없음 (review 07-01, 2026-11-01). type: url default: null allowed_values: null @@ -559,7 +561,7 @@ env_keys: required_test: tracing-contract:exporter-endpoint-resolvable - name: APP_TRACING_ENABLED - # source: feature-distributed-tracing-contract 2026-05-22 + # 출처: feature-distributed-tracing-contract 2026-05-22 # "tracing disabled profile에서도 envelope meta.traceId와 log traceId는 유지" type: boolean default: true @@ -573,12 +575,11 @@ env_keys: required_test: tracing-contract:meta-traceid-when-disabled - name: APP_TRACING_SAMPLE_RATE - # source: feature-distributed-tracing-contract 2026-05-22 + # 출처: feature-distributed-tracing-contract 2026-05-22 # "trace sampling rate default = prod 1%, dev/local 100%" - # D-1 ISSUE-1 fix (2026-06-16): blank = per-profile resolver 기본값 사용. - # RuntimeEnvironment is the profile SSOT; resolver policy is prod=0.01, dev/local=1.0. - # TracingEnvironmentPostProcessor bridges resolved rate to - # management.tracing.sampling.probability. + # D-1 ISSUE-1 fix (2026-06-16): 빈 값 = profile별 resolver 기본값을 쓴다. + # RuntimeEnvironment가 profile의 정본이다. resolver 정책은 prod=0.01, dev/local=1.0. + # TracingEnvironmentPostProcessor가 정한 비율을 management.tracing.sampling.probability로 잇는다. type: string default: "" allowed_values: null @@ -590,13 +591,13 @@ env_keys: compatibility_impact: behavior-change required_test: tracing-contract:sample-rate-per-profile - # === Log management (feature-log-management-contract) === + # === 로그 관리 (feature-log-management-contract) === - # APP_LOG_LEVEL (single key) replaced by the 5 granular APP_LOG_LEVEL_* rows below - # (root / app / spring / web / sql) — as built by feature-log-management-contract. + # APP_LOG_LEVEL 키 하나를 아래 APP_LOG_LEVEL_* 행 다섯(root / app / spring / web / sql)으로 나눴다 + # — feature-log-management-contract가 만든 대로. - name: APP_LOG_LEVEL_ROOT - # source: feature-log-management-contract — root logger level + # 출처: feature-log-management-contract — root logger 레벨 type: enum default: INFO allowed_values: [TRACE, DEBUG, INFO, WARN, ERROR, OFF] @@ -609,7 +610,7 @@ env_keys: required_test: log-contract:root-level - name: APP_LOG_LEVEL_APP - # source: feature-log-management-contract — application package level + # 출처: feature-log-management-contract — 애플리케이션 패키지 레벨 type: enum default: INFO allowed_values: [TRACE, DEBUG, INFO, WARN, ERROR, OFF] @@ -622,7 +623,7 @@ env_keys: required_test: log-contract:app-level - name: APP_LOG_LEVEL_SPRING - # source: feature-log-management-contract — Spring framework package level + # 출처: feature-log-management-contract — Spring framework 패키지 레벨 type: enum default: INFO allowed_values: [TRACE, DEBUG, INFO, WARN, ERROR, OFF] @@ -635,7 +636,7 @@ env_keys: required_test: log-contract:spring-level - name: APP_LOG_LEVEL_WEB - # source: feature-log-management-contract — web/MVC package level + # 출처: feature-log-management-contract — web/MVC 패키지 레벨 type: enum default: INFO allowed_values: [TRACE, DEBUG, INFO, WARN, ERROR, OFF] @@ -648,7 +649,7 @@ env_keys: required_test: log-contract:web-level - name: APP_LOG_LEVEL_SQL - # source: feature-log-management-contract — JPA/JDBC SQL package level (DEBUG prints SQL) + # 출처: feature-log-management-contract — JPA/JDBC SQL 패키지 레벨 (DEBUG면 SQL을 찍는다) type: enum default: WARN allowed_values: [TRACE, DEBUG, INFO, WARN, ERROR, OFF] @@ -661,7 +662,7 @@ env_keys: required_test: log-contract:sql-level - name: APP_LOG_FILE_ENABLED - # source: feature-log-management-contract — rolling JSON file appender toggle + # 출처: feature-log-management-contract — 순환(rolling) JSON 파일 appender 켜고 끄기 type: boolean default: false allowed_values: [true, false] @@ -674,7 +675,7 @@ env_keys: required_test: log-contract:file-appender-toggle - name: APP_LOG_FILE_PATH - # source: feature-log-management-contract — file path (relative to bootRun cwd or absolute) + # 출처: feature-log-management-contract — 파일 경로 (bootRun 실행 위치 기준 상대 경로 또는 절대 경로) type: string default: logs/ca-skeleton.json allowed_values: null @@ -687,7 +688,7 @@ env_keys: required_test: log-contract:file-path-set - name: APP_LOG_FILE_MAX_SIZE - # source: feature-log-management-contract — per-file rolling size cap + # 출처: feature-log-management-contract — 파일 하나의 순환 크기 상한 type: data_size default: 100MB allowed_values: null @@ -700,7 +701,7 @@ env_keys: required_test: log-contract:file-max-size - name: APP_LOG_FILE_MAX_HISTORY - # source: feature-log-management-contract — number of rolled archives to retain + # 출처: feature-log-management-contract — 남길 순환 보관 파일 수 type: int default: 14 allowed_values: null @@ -713,7 +714,7 @@ env_keys: required_test: log-contract:file-max-history - name: APP_LOG_FILE_TOTAL_SIZE_CAP - # source: feature-log-management-contract — total size cap across rolled files + # 출처: feature-log-management-contract — 순환 파일 전체의 크기 상한 type: data_size default: 3GB allowed_values: null @@ -726,7 +727,7 @@ env_keys: required_test: log-contract:file-total-size-cap - name: APP_LOG_ASYNC_ENABLED - # source: feature-log-management-contract — AsyncAppender wrap for non-blocking I/O + # 출처: feature-log-management-contract — 막히지 않는 I/O를 위한 AsyncAppender 감싸기 type: boolean default: true allowed_values: [true, false] @@ -739,7 +740,7 @@ env_keys: required_test: log-contract:async-appender-toggle - name: APP_LOG_ASYNC_QUEUE_SIZE - # source: feature-log-management-contract — in-memory queue depth before back-pressure + # 출처: feature-log-management-contract — 역압(back-pressure) 전 메모리 queue 깊이 type: int default: 512 allowed_values: null @@ -752,8 +753,8 @@ env_keys: required_test: log-contract:async-queue-size - name: APP_LOG_ASYNC_DISCARDING_THRESHOLD - # source: feature-log-management-contract — remaining-capacity floor below which - # TRACE/DEBUG/INFO events drop (WARN/ERROR always kept). 0 = never drop. + # 출처: feature-log-management-contract — 남은 용량이 이 값 아래로 내려가면 + # TRACE/DEBUG/INFO 이벤트를 버린다(WARN/ERROR는 늘 남긴다). 0 = 버리지 않는다. type: int default: 20 allowed_values: null @@ -766,7 +767,7 @@ env_keys: required_test: log-contract:async-discarding-threshold - name: APP_LOG_JSON_TIMEZONE - # source: feature-log-management-contract — IANA timezone for JSON encoder timestamps + # 출처: feature-log-management-contract — JSON encoder 시각에 쓰는 IANA timezone type: string default: UTC allowed_values: null @@ -779,7 +780,7 @@ env_keys: required_test: log-contract:json-timezone - name: APP_LOG_JSON_TIMESTAMP_PATTERN - # source: feature-log-management-contract — JSON encoder timestamp pattern (ISO 8601 default) + # 출처: feature-log-management-contract — JSON encoder 시각 형식 (기본 ISO 8601) type: string default: "yyyy-MM-dd'T'HH:mm:ss.SSSXXX" allowed_values: null @@ -792,7 +793,7 @@ env_keys: required_test: log-contract:json-timestamp-pattern - name: APP_LOG_JSON_INCLUDE_CALLER_DATA - # source: feature-log-management-contract — include file/method/line (significant perf cost) + # 출처: feature-log-management-contract — 파일·메서드·줄 번호를 넣는다 (성능 비용이 크다) type: boolean default: false allowed_values: [true, false] @@ -805,7 +806,7 @@ env_keys: required_test: log-contract:json-include-caller-data - name: APP_LOG_JSON_LOGGER_NAME_LENGTH - # source: feature-log-management-contract — logger name abbreviation (0 = full name) + # 출처: feature-log-management-contract — logger 이름 줄이기 (0 = 전체 이름) type: int default: 0 allowed_values: null @@ -818,7 +819,7 @@ env_keys: required_test: log-contract:json-logger-name-length - name: APP_LOG_SAMPLING_RATE - # source: feature-log-management-contract 2026-05-22 + # 출처: feature-log-management-contract 2026-05-22 # "log sampling(prod 10%) > trace sampling(prod 1%)" + Sampling Policy 표 (prod 10%, dev/local 100%) type: string default: "1.0" @@ -831,12 +832,13 @@ env_keys: compatibility_impact: behavior-change required_test: log-contract:sample-rate-per-profile - # === Privacy: user_principal pseudonymization (feature-data-retention-privacy-contract) === + # === 개인정보: user_principal 가명화 (feature-data-retention-privacy-contract) === - name: APP_PRIVACY_PSEUDONYMIZATION_SALT - # source: feature-data-retention-privacy-contract — "pseudonymization key = HMAC-SHA-256 - # with rotating salt (90d)". Consumed by feature-log-management-contract (DRIFT-6) - # to record user_principal in pseudonymized form. secret 분류로 secrets-classification.yaml에서 owns. + # 출처: feature-data-retention-privacy-contract — "pseudonymization key = HMAC-SHA-256 + # with rotating salt (90d)" (가명화 키는 90일마다 바뀌는 salt의 HMAC-SHA-256). feature-log-management-contract + # (DRIFT-6)가 user_principal을 가명 형태로 남기는 데 쓴다. secret 분류라 secrets-classification.yaml이 행을 + # 가진다. type: string default: null allowed_values: null @@ -851,7 +853,7 @@ env_keys: # === Security / CORS / JWT (feature-security-operational-baseline) === - name: APP_SECURITY_CORS_ORIGINS - # source: feature-security-operational-baseline 2026-05-22 + # 출처: feature-security-operational-baseline 2026-05-22 # "allowlist origin은 env-driven runtime configuration의 APP_SECURITY_CORS_ORIGINS로 주입" type: csv_list default: null @@ -865,7 +867,7 @@ env_keys: required_test: security-contract:cors-allowlist - name: APP_SECURITY_CORS_ENABLED - # source: feature-security-operational-baseline — CORS filter master toggle + # 출처: feature-security-operational-baseline — CORS filter 전체 켜고 끄기 type: boolean default: false allowed_values: [true, false] @@ -878,8 +880,8 @@ env_keys: required_test: security-contract:cors-enabled-toggle - name: APP_SECURITY_CORS_ALLOWED_METHODS - # source: feature-security-operational-baseline — allowed methods - # (empty -> sensible method defaults in CorsSettings) + # 출처: feature-security-operational-baseline — 허용 method + # (빈 값 -> CorsSettings의 무난한 method 기본값) type: csv_list default: null allowed_values: null @@ -892,7 +894,7 @@ env_keys: required_test: security-contract:cors-allowed-methods - name: APP_SECURITY_CORS_ALLOWED_HEADERS - # source: feature-security-operational-baseline — allowed request headers ("*" = any) + # 출처: feature-security-operational-baseline — 허용 요청 헤더 ("*" = 모두) type: csv_list default: "*" allowed_values: null @@ -905,7 +907,7 @@ env_keys: required_test: security-contract:cors-allowed-headers - name: APP_SECURITY_CORS_ALLOW_CREDENTIALS - # source: feature-security-operational-baseline 2026-05-22 + # 출처: feature-security-operational-baseline 2026-05-22 # "CORS는 allowlist default, credentials false default" / "wildcard with credentials forbidden" type: boolean default: false @@ -919,7 +921,7 @@ env_keys: required_test: security-contract:cors-credentials-policy - name: APP_SECURITY_CORS_MAX_AGE - # source: feature-security-operational-baseline 2026-05-22 + # 출처: feature-security-operational-baseline 2026-05-22 # "preflight max-age 600s default" type: duration default: 600s @@ -1029,9 +1031,8 @@ env_keys: required_test: redis-session-contract:csrf-enabled - name: APP_SESSION_REDIS_NAMESPACE_ENVIRONMENT - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1046,9 +1047,8 @@ env_keys: required_test: redis-session-contract:key-namespace - name: APP_SESSION_IDLE_TIMEOUT - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -1063,9 +1063,8 @@ env_keys: required_test: redis-session-contract:idle-expiry - name: APP_SESSION_ABSOLUTE_LIFETIME - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -1080,9 +1079,8 @@ env_keys: required_test: redis-session-contract:absolute-expiry - name: APP_SESSION_TOUCH_INTERVAL - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -1097,9 +1095,8 @@ env_keys: required_test: redis-session-contract:bounded-touch - name: APP_SESSION_TOMBSTONE_TTL - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -1114,9 +1111,8 @@ env_keys: required_test: redis-session-contract:logout-tombstone - name: APP_SESSION_MAXIMUM_ENVELOPE_BYTES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -1131,9 +1127,8 @@ env_keys: required_test: redis-session-contract:serializer-bounded - name: APP_SESSION_MAXIMUM_ATTRIBUTES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -1148,9 +1143,8 @@ env_keys: required_test: redis-session-contract:serializer-bounded - name: APP_SESSION_MAXIMUM_SCALAR_BYTES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -1165,7 +1159,7 @@ env_keys: required_test: redis-session-contract:serializer-bounded - name: APP_SECURITY_JWT_ISSUER - # source: feature-security-operational-baseline 2026-05-22 + # 출처: feature-security-operational-baseline 2026-05-22 # "issuer mismatch | 401 | AUTH_ISSUER_MISMATCH" type: url default: null @@ -1179,7 +1173,7 @@ env_keys: required_test: security-contract:jwt-issuer-set - name: APP_SECURITY_JWT_AUDIENCE - # source: feature-security-operational-baseline 2026-05-22 + # 출처: feature-security-operational-baseline 2026-05-22 # "audience mismatch | 401 | AUTH_AUDIENCE_MISMATCH" type: csv_list default: null @@ -1193,7 +1187,7 @@ env_keys: required_test: security-contract:jwt-audience-set - name: APP_RATE_LIMIT_ENABLED - # Inbound enforcement stays disabled until an exact provider is selected. + # 정확한 provider를 고르기 전까지 inbound 강제는 꺼져 있다. type: boolean default: false allowed_values: [true, false] @@ -1205,14 +1199,14 @@ env_keys: compatibility_impact: additive required_test: redis-rate-limit-contract:transport-provider-default-pair - # APP_RATE_LIMIT_CLIENT_IP_MODE removed (2026-09-25, review follow-up I-5a): its - # forwarded-headers-trusted value keyed unauthenticated callers by the leftmost X-Forwarded-For - # entry, which the caller writes. The client IP is getRemoteAddr(); behind a proxy set - # APP_SERVER_FORWARD_HEADERS_STRATEGY=native and server.tomcat.remoteip.internal-proxies. + # APP_RATE_LIMIT_CLIENT_IP_MODE는 지웠다 (2026-09-25, review follow-up I-5a): 그 값 + # forwarded-headers-trusted는 인증하지 않은 호출자를 X-Forwarded-For의 맨 왼쪽 값으로 구분했는데, 그 값은 + # 호출자가 쓴다. client IP는 getRemoteAddr()다. proxy 뒤라면 + # APP_SERVER_FORWARD_HEADERS_STRATEGY=native와 server.tomcat.remoteip.internal-proxies를 설정한다. - name: APP_RATE_LIMIT_REDIS_ENABLED - # DEPRECATED 2026-08-10: the rate limiter no longer owns a Redis client of its own. One client, built by RedisRuntimeAutoConfiguration, serves every capability, so a second endpoint and a second set of ceilings could only ever disagree with it. - # Replaced by: app.redis.enabled (APP_REDIS_ENABLED). + # 폐기 2026-08-10: rate limiter는 이제 자기 Redis client를 갖지 않는다. RedisRuntimeAutoConfiguration이 만든 client 하나가 모든 capability를 맡으므로, 두 번째 endpoint와 두 번째 상한은 그 client와 어긋날 수밖에 없었다. + # 대체: app.redis.enabled (APP_REDIS_ENABLED). deprecated_orphaned: true removal_deadline: 2026-11-30 type: boolean @@ -1299,8 +1293,8 @@ env_keys: required_test: rate-limit-contract:key-version-bounded - name: APP_RATE_LIMIT_REDIS_HOST - # DEPRECATED 2026-08-10: the rate limiter no longer owns a Redis client of its own. One client, built by RedisRuntimeAutoConfiguration, serves every capability, so a second endpoint and a second set of ceilings could only ever disagree with it. - # Replaced by: app.redis.nodes (APP_REDIS_NODES). + # 폐기 2026-08-10: rate limiter는 이제 자기 Redis client를 갖지 않는다. RedisRuntimeAutoConfiguration이 만든 client 하나가 모든 capability를 맡으므로, 두 번째 endpoint와 두 번째 상한은 그 client와 어긋날 수밖에 없었다. + # 대체: app.redis.nodes (APP_REDIS_NODES). deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1315,8 +1309,8 @@ env_keys: required_test: rate-limit-contract:redis-host-required - name: APP_RATE_LIMIT_REDIS_PORT - # DEPRECATED 2026-08-10: the rate limiter no longer owns a Redis client of its own. One client, built by RedisRuntimeAutoConfiguration, serves every capability, so a second endpoint and a second set of ceilings could only ever disagree with it. - # Replaced by: app.redis.nodes (APP_REDIS_NODES). + # 폐기 2026-08-10: rate limiter는 이제 자기 Redis client를 갖지 않는다. RedisRuntimeAutoConfiguration이 만든 client 하나가 모든 capability를 맡으므로, 두 번째 endpoint와 두 번째 상한은 그 client와 어긋날 수밖에 없었다. + # 대체: app.redis.nodes (APP_REDIS_NODES). deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -1343,8 +1337,8 @@ env_keys: required_test: rate-limit-contract:redis-password-no-leak - name: APP_RATE_LIMIT_REDIS_TRUST_PEM - # DEPRECATED 2026-08-10: the rate limiter no longer owns a Redis client of its own. One client, built by RedisRuntimeAutoConfiguration, serves every capability, so a second endpoint and a second set of ceilings could only ever disagree with it. - # Replaced by: app.redis.tls.trust-material-resource. + # 폐기 2026-08-10: rate limiter는 이제 자기 Redis client를 갖지 않는다. RedisRuntimeAutoConfiguration이 만든 client 하나가 모든 capability를 맡으므로, 두 번째 endpoint와 두 번째 상한은 그 client와 어긋날 수밖에 없었다. + # 대체: app.redis.tls.trust-material-resource. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1383,8 +1377,8 @@ env_keys: required_test: redis-contract:session-password-no-leak - name: APP_SESSION_REDIS_TRUST_PEM - # DEPRECATED 2026-08-10: the session generation that bound this was removed, and the replacement does not own a Redis client of its own either. - # Replaced by: app.redis.tls.trust-material-resource. + # 폐기 2026-08-10: 이 값을 바인딩하던 session 세대를 지웠고, 대신한 것도 자기 Redis client를 갖지 않는다. + # 대체: app.redis.tls.trust-material-resource. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1399,9 +1393,8 @@ env_keys: required_test: redis-contract:session-trust-material-no-leak - name: APP_SESSION_REDIS_KEY_HMAC_SECRET - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1428,8 +1421,8 @@ env_keys: required_test: rate-limit-contract:redis-timeout-bounded - name: APP_RATE_LIMIT_REDIS_MAXIMUM_COMMAND_BYTES - # DEPRECATED 2026-08-10: the rate limiter no longer owns a Redis client of its own. One client, built by RedisRuntimeAutoConfiguration, serves every capability, so a second endpoint and a second set of ceilings could only ever disagree with it. - # Replaced by: app.redis.limits.max-batch-request-bytes. + # 폐기 2026-08-10: rate limiter는 이제 자기 Redis client를 갖지 않는다. RedisRuntimeAutoConfiguration이 만든 client 하나가 모든 capability를 맡으므로, 두 번째 endpoint와 두 번째 상한은 그 client와 어긋날 수밖에 없었다. + # 대체: app.redis.limits.max-batch-request-bytes. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -1444,8 +1437,8 @@ env_keys: required_test: rate-limit-contract:redis-command-bytes-bounded - name: APP_RATE_LIMIT_REDIS_MAXIMUM_QUEUED_COMMANDS - # DEPRECATED 2026-08-10: the rate limiter no longer owns a Redis client of its own. One client, built by RedisRuntimeAutoConfiguration, serves every capability, so a second endpoint and a second set of ceilings could only ever disagree with it. - # Replaced by: app.redis.capacity.maximum-in-flight-commands. + # 폐기 2026-08-10: rate limiter는 이제 자기 Redis client를 갖지 않는다. RedisRuntimeAutoConfiguration이 만든 client 하나가 모든 capability를 맡으므로, 두 번째 endpoint와 두 번째 상한은 그 client와 어긋날 수밖에 없었다. + # 대체: app.redis.capacity.maximum-in-flight-commands. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -1460,8 +1453,8 @@ env_keys: required_test: rate-limit-contract:redis-queue-bounded - name: APP_RATE_LIMIT_REDIS_MAXIMUM_IN_FLIGHT_BYTES - # DEPRECATED 2026-08-10: the rate limiter no longer owns a Redis client of its own. One client, built by RedisRuntimeAutoConfiguration, serves every capability, so a second endpoint and a second set of ceilings could only ever disagree with it. - # Replaced by: app.redis.capacity.maximum-in-flight-bytes. + # 폐기 2026-08-10: rate limiter는 이제 자기 Redis client를 갖지 않는다. RedisRuntimeAutoConfiguration이 만든 client 하나가 모든 capability를 맡으므로, 두 번째 endpoint와 두 번째 상한은 그 client와 어긋날 수밖에 없었다. + # 대체: app.redis.capacity.maximum-in-flight-bytes. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -1476,8 +1469,8 @@ env_keys: required_test: rate-limit-contract:redis-byte-admission-bounded - name: APP_RATE_LIMIT_REDIS_NAMESPACE_ENVIRONMENT - # DEPRECATED 2026-08-10: the rate limiter no longer renders its own key prefix. Four capabilities each joining two free-form tokens produced four prefixes, and the ACL pattern matched none of them. - # Replaced by: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT), shared by every capability. + # 폐기 2026-08-10: rate limiter는 이제 key prefix를 스스로 만들지 않는다. capability 넷이 각자 자유 형식 토큰 둘을 이어 prefix 넷이 생겼고, ACL 패턴은 그중 어느 것과도 맞지 않았다. + # 대체: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT). 모든 capability가 함께 쓴다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1600,12 +1593,11 @@ env_keys: required_test: rate-limit-contract:cleanup-grace-bounded - name: APP_IDEMPOTENCY_TTL - # app.capabilities.idempotency.replay-ttl: how long a completed response stays - # replayable. One value for every provider; IdempotencySettings refuses more than 72h, less than - # APP_IDEMPOTENCY_PROCESSING_LEASE (re-review 2026-11-04 RR-03-11), and more than - # APP_IDEMPOTENCY_FAILURE_RETENTION (RR3-03-02, owner decision 2026-11-04), at startup: raising - # this key alone past the failure retention (default 24h) fails startup, so raise both - # (RR5-03-01). Each record lives for the processing lease plus this value in both stores. + # app.capabilities.idempotency.replay-ttl: 끝난 응답을 다시 돌려줄 수 있는 기간. 모든 provider가 + # 같은 값을 쓴다. IdempotencySettings는 기동할 때 72h보다 길거나, APP_IDEMPOTENCY_PROCESSING_LEASE보다 + # 짧거나(re-review 2026-11-04 RR-03-11), APP_IDEMPOTENCY_FAILURE_RETENTION보다 긴 값(RR3-03-02, 소유자 + # 결정 2026-11-04)을 거부한다. 이 키만 실패 보관 기간(기본 24h)보다 길게 올리면 기동이 실패하니 둘을 같이 + # 올린다(RR5-03-01). 두 저장소 모두에서 기록 하나는 처리 lease에 이 값을 더한 만큼 남는다. type: duration default: 24h allowed_values: null @@ -1618,12 +1610,12 @@ env_keys: required_test: idempotency-contract:ttl-applied - name: APP_IDEMPOTENCY_PROVIDER - # app.capabilities.idempotency.provider. redis and postgresql each contribute only the - # store; app-bootstrap builds the one IdempotencyExecutor and refuses startup unless exactly one - # store exists. postgresql uses the primary data source, applies its Flyway streams at startup - # and refuses a non-PostgreSQL data source, so bootRunH2 runs with disabled or redis. Selection - # is explicit and disabled by default; no implementation wins merely by being on the classpath. - # 2026-09-25: jdbc (the V1 store) was removed; a deployment still setting it fails to bind. + # app.capabilities.idempotency.provider. redis와 postgresql은 각각 저장소만 기여한다. app-bootstrap이 + # IdempotencyExecutor 하나를 만들고, 저장소가 정확히 하나가 아니면 기동을 거부한다. postgresql은 주 + # data source를 쓰고, 기동할 때 자기 Flyway stream을 적용하고, PostgreSQL이 아닌 data source를 거부한다. + # 그래서 bootRunH2는 disabled나 redis로 돈다. 선택은 명시적이고 기본은 disabled다. classpath에 있다는 + # 것만으로 고르는 구현은 없다. + # 2026-09-25: jdbc(V1 저장소)를 지웠다. 아직 이 값을 쓰는 배포는 바인딩에서 실패한다. type: enum default: disabled allowed_values: [disabled, redis, postgresql] @@ -1636,7 +1628,7 @@ env_keys: required_test: redis-idempotency-contract:provider-exclusive - name: APP_IDEMPOTENCY_REDIS_KEY_HMAC_SECRET - # DEPRECATED 2026-09-22: the Redis idempotency adapter consumes caller-supplied scope digests and never read this secret. + # 폐기 2026-09-22: Redis idempotency adapter는 호출자가 준 scope digest를 쓰고 이 비밀을 읽은 적이 없다. deprecated_orphaned: true removal_deadline: 2026-12-31 type: string @@ -1651,8 +1643,8 @@ env_keys: required_test: redis-idempotency-contract:key-hmac-no-leak - name: APP_IDEMPOTENCY_REDIS_NAMESPACE_ENVIRONMENT - # DEPRECATED 2026-08-10: the idempotency store no longer renders its own key prefix. Four capabilities each joining two free-form tokens produced four prefixes, and the ACL pattern matched none of them. - # Replaced by: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT), shared by every capability. + # 폐기 2026-08-10: idempotency store는 이제 key prefix를 스스로 만들지 않는다. capability 넷이 각자 자유 형식 토큰 둘을 이어 prefix 넷이 생겼고, ACL 패턴은 그중 어느 것과도 맞지 않았다. + # 대체: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT). 모든 capability가 함께 쓴다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1667,10 +1659,9 @@ env_keys: required_test: redis-idempotency-contract:key-namespace - name: APP_IDEMPOTENCY_PROCESSING_LEASE - # app.capabilities.idempotency.processing-lease: how long one attempt holds its claim. Longer - # than the in-flight Retry-After (2s), at most 1h, and not longer than APP_IDEMPOTENCY_TTL. A - # claim whose lease runs out is taken over only if it never started; an execution whose lease - # ran out is answered IDEMPOTENCY_RECOVERY_REQUIRED and never run again. + # app.capabilities.idempotency.processing-lease: 시도 하나가 claim을 쥐는 기간. in-flight + # Retry-After(2s)보다 길고, 최대 1h이며, APP_IDEMPOTENCY_TTL보다 길지 않다. lease가 끝난 claim은 시작하지 + # 않았을 때만 넘겨받는다. lease가 끝난 실행은 IDEMPOTENCY_RECOVERY_REQUIRED로 답하고 다시 돌리지 않는다. type: duration default: 30s allowed_values: null @@ -1683,11 +1674,11 @@ env_keys: required_test: redis-idempotency-contract:processing-lease-bounded - name: APP_IDEMPOTENCY_FAILURE_RETENTION - # app.capabilities.idempotency.failure-retention: how long a record the executor marked failed - # (abandoned with an unknown effect, or retryable without one) stays, from the marking. At most - # 30d, and IdempotencySettings refuses less than APP_IDEMPOTENCY_TTL at startup: a shorter one - # lets an abandoned record go first, and a same-key resend runs the work again (re-review - # 2026-11-04 RR3-03-02, owner decision 2026-11-04). + # app.capabilities.idempotency.failure-retention: executor가 실패로 표시한 기록(결과를 모른 채 + # 버렸거나, 결과 없이 다시 시도할 수 있는 것)이 표시한 때부터 남는 기간. 최대 30d이고, + # IdempotencySettings는 기동할 때 APP_IDEMPOTENCY_TTL보다 짧은 값을 거부한다: 더 짧으면 버린 기록이 먼저 + # 사라지고, 같은 key로 다시 보낸 요청이 일을 한 번 더 한다(re-review 2026-11-04 RR3-03-02, 소유자 결정 + # 2026-11-04). type: duration default: 24h allowed_values: null @@ -1712,7 +1703,7 @@ env_keys: required_test: redis-lease-contract:provider-exclusive - name: APP_LEASE_REDIS_KEY_HMAC_SECRET - # DEPRECATED 2026-09-22: the Redis lease adapter consumes caller-supplied resource digests and never read this secret. + # 폐기 2026-09-22: Redis lease adapter는 호출자가 준 resource digest를 쓰고 이 비밀을 읽은 적이 없다. deprecated_orphaned: true removal_deadline: 2026-12-31 type: string @@ -1727,8 +1718,8 @@ env_keys: required_test: redis-lease-contract:key-hmac-no-leak - name: APP_LEASE_REDIS_NAMESPACE_ENVIRONMENT - # DEPRECATED 2026-08-10: the lease no longer renders its own key prefix. Four capabilities each joining two free-form tokens produced four prefixes, and the ACL pattern matched none of them. - # Replaced by: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT), shared by every capability. + # 폐기 2026-08-10: lease는 이제 key prefix를 스스로 만들지 않는다. capability 넷이 각자 자유 형식 토큰 둘을 이어 prefix 넷이 생겼고, ACL 패턴은 그중 어느 것과도 맞지 않았다. + # 대체: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT). 모든 capability가 함께 쓴다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -1754,10 +1745,10 @@ env_keys: compatibility_impact: additive required_test: redis-lease-contract:drift-budget-bounded - # === Cache / Redis (feature-cache-consistency-contract + integration-adapter-templates) === + # === 캐시 / Redis (feature-cache-consistency-contract + integration-adapter-templates) === - name: APP_CACHE_CANONICAL_DEFAULT_PROVIDER - # Canonical default semantic region provider selection; legacy enable is a separate migration path. + # 기본 캐시 영역(canonical default semantic region)의 provider 선택. 옛 켜기 키는 따로 옮겨 가는 경로다. type: enum default: disabled allowed_values: [disabled, redis] @@ -1770,12 +1761,12 @@ env_keys: required_test: redis-cache:canonical-cache-role-composition - name: APP_REDIS_ENABLED - # 2026-09-25 capability packaging: the cache-redis module is on when present (its - # config/module-defaults/cache-redis.yml maps this key with default true); false is the explicit - # off. Absent from the build is the ordinary off state. - # False loads no Redis settings, requires no Redis secret, and creates no client, connection, - # thread or health contributor. Role selectors choose which capabilities compose once Redis is - # on; none of them is a second on/off key. + # 2026-09-25 capability 포장: cache-redis 모듈은 있으면 켜진다(모듈의 + # config/module-defaults/cache-redis.yml이 이 키를 기본 true로 잇는다). false가 명시적으로 끄는 값이다. + # 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. + # false면 Redis 설정을 읽지 않고, Redis 비밀을 요구하지 않고, client·연결·thread·health contributor를 + # 만들지 않는다. Redis가 켜진 뒤 어떤 capability를 조립할지는 role 선택자가 고른다. 그중 어느 것도 두 + # 번째 켜고 끄기 키가 아니다. property: app.redis.enabled owner_module: adapter-outbound-cache-redis type: boolean @@ -1792,8 +1783,8 @@ env_keys: - name: APP_CACHE_REDIS_POSITIVE_HARD_TTL - # How long a cache entry stays usable. The physical Redis TTL equals this and nothing else, so - # an entry can never outlive the deployment's own notion of usability or be discarded early. + # 캐시 항목을 쓸 수 있는 기간. Redis의 실제 TTL은 이 값과 같고 다른 것이 아니다. 그래서 항목이 배포가 + # 정한 사용 기간보다 오래 남거나 일찍 버려지지 않는다. type: duration default: 5m allowed_values: null @@ -1806,8 +1797,8 @@ env_keys: required_test: redis-capability:cache-region-composition - name: APP_CACHE_REDIS_NEGATIVE_TTL - # How long an authoritative absence is cached. Separate from the positive TTL because "the - # source says this does not exist" is a fact with a different shelf life from a value. + # 권위 있는 「없음」을 캐시하는 기간. 「원천에 이것이 없다」는 사실은 값과 유통 기한이 달라서 값의 + # TTL과 따로 둔다. type: duration default: 10s allowed_values: null @@ -1820,9 +1811,9 @@ env_keys: required_test: redis-capability:cache-region-composition - name: APP_CACHE_REDIS_MAXIMUM_SCRIPT_CONNECTIONS - # The cache's own script-lane connections. Separate from APP_REDIS_CAPACITY_MAXIMUM_SCRIPT_CONNECTIONS, - # which idempotency, rate limiting and leases share, so cache fills cannot starve them (review - # 2026-11-03 README section 4, RR-04-02). + # 캐시 자신의 script lane 연결 수. idempotency·rate limit·lease가 함께 쓰는 + # APP_REDIS_CAPACITY_MAXIMUM_SCRIPT_CONNECTIONS와 따로 두어, 캐시 채우기가 그 셋을 굶기지 않게 한다 + # (review 2026-11-03 README 4절, RR-04-02). property: app.capabilities.cache.maximum-script-connections owner_module: adapter-outbound-cache-redis type: integer @@ -1838,7 +1829,7 @@ env_keys: required_test: redis-capability:cache-script-lane-separate-from-correctness - name: APP_IDEMPOTENCY_REDIS_COMMAND_TIMEOUT - # The ceiling on one owner-safe transition. + # owner-safe 전이 하나의 상한. type: duration default: 200ms allowed_values: null @@ -1851,7 +1842,7 @@ env_keys: required_test: redis-capability:idempotency-store-composition - name: APP_LEASE_REDIS_COMMAND_TIMEOUT - # The ceiling on one lease operation. + # lease 연산 하나의 상한. type: duration default: 200ms allowed_values: null @@ -1864,8 +1855,8 @@ env_keys: required_test: redis-capability:lease-composition - name: APP_LEASE_REDIS_CONTENTION_RETRY_AFTER - # What a contended acquire tells the caller to wait. Distinct from the drift budget: one is - # advice to a caller that lost, the other is how much of its own lease a winner does not trust. + # 경합으로 acquire에 실패한 호출자에게 기다리라고 알려 줄 시간. drift 예산과 다르다: 하나는 진 + # 호출자에게 주는 조언이고, 다른 하나는 이긴 쪽이 자기 lease 중 믿지 않는 부분이다. type: duration default: 50ms allowed_values: null @@ -1877,14 +1868,14 @@ env_keys: compatibility_impact: additive required_test: redis-capability:lease-composition - # --- Redis runtime settings (app.redis.*) ---------------------------------- - # Bound only by RedisRuntimeAutoConfiguration in adapter-outbound-redis-runtime while - # APP_REDIS_ENABLED is true. application.yml does not force these values into Redis-free - # deployments; src/.env.example merely documents explicit operator inputs. verifyEnvKeys checks - # the registry against the runtime module's configuration metadata. + # --- Redis 런타임 설정 (app.redis.*) ---------------------------------- + # APP_REDIS_ENABLED가 true일 때만 adapter-outbound-redis-runtime의 RedisRuntimeAutoConfiguration이 + # 바인딩한다. application.yml은 Redis 없는 배포에 이 값을 넣지 않는다. src/.env.example은 운영자가 + # 명시적으로 넣을 값을 적어 둘 뿐이다. verifyEnvKeys가 이 레지스트리를 런타임 모듈의 설정 메타데이터와 + # 대조한다. - name: APP_REDIS_DATABASE - # Cluster supports database 0 only; a non-zero value fails startup there. + # Cluster는 database 0만 지원한다. 0이 아니면 거기서 기동이 실패한다. property: app.redis.database owner_module: adapter-outbound-redis-runtime type: integer @@ -1961,7 +1952,7 @@ env_keys: required_test: redis-sdk:typed-settings-bound-and-validated - name: APP_REDIS_NODES - # CSV of host:port. Cluster and Sentinel take every seed node. + # host:port CSV. Cluster와 Sentinel은 모든 seed node를 받는다. property: app.redis.nodes owner_module: adapter-outbound-redis-runtime type: csv @@ -1992,7 +1983,7 @@ env_keys: required_test: redis-sdk:typed-settings-bound-and-validated - name: APP_REDIS_TIMEOUT_FAST - # Single-key command profile; above 5s produces a startup warning. + # 단일 key 명령 profile. 5s를 넘으면 기동 때 경고를 남긴다. property: app.redis.timeout.fast owner_module: adapter-outbound-redis-runtime type: duration @@ -2022,16 +2013,15 @@ env_keys: compatibility_impact: additive required_test: redis-sdk:typed-settings-bound-and-validated - # --- Redis runtime composition settings (app.redis.*) ---------------------- - # Authentication, Sentinel discovery, TLS, lifecycle, Cluster routing and capacity. Same rule as the rest of app.redis.*: bound only while - # APP_REDIS_ENABLED is true, and deliberately absent from application.yml and .env. + # --- Redis 런타임 조립 설정 (app.redis.*) ---------------------- + # 인증, Sentinel 탐색, TLS, 수명 주기, Cluster 라우팅, 용량. 다른 app.redis.*와 규칙이 같다: + # APP_REDIS_ENABLED가 true일 때만 바인딩하고, application.yml과 .env에는 일부러 두지 않는다. - name: APP_REDIS_AUTHENTICATION_ADVANCED_CREDENTIAL_REFERENCE - # Pointer to the account registered scripts run as, in the same - # secret://@/ form as the application reference. Unset, scripts run - # as the application account and startup logs a warning saying so. The Compose Redis lanes use - # secret://ca-skeleton-application-advanced@environment/REDIS_LANE_ADVANCED_PASSWORD, a fixture - # account of compose/redis/acl/lane-fixture-accounts.acl. + # 등록된 script가 실행될 계정을 가리키는 참조. 애플리케이션 참조와 같은 + # secret://@/ 형식이다. 비우면 script가 애플리케이션 계정으로 돌고 기동 때 그렇다고 + # 경고를 남긴다. Compose Redis lane은 compose/redis/acl/lane-fixture-accounts.acl의 fixture 계정인 + # secret://ca-skeleton-application-advanced@environment/REDIS_LANE_ADVANCED_PASSWORD를 쓴다. property: app.redis.authentication.advanced-credential-reference owner_module: adapter-outbound-cache-redis type: string @@ -2049,19 +2039,18 @@ env_keys: - name: APP_REDIS_AUTHENTICATION_ANONYMOUS_ACCESS_ACCEPTED property: app.redis.authentication.anonymous-access-accepted owner_module: adapter-outbound-cache-redis - # Explicit acknowledgement that Redis runs with no credential. Startup fails without it when - # no credential reference is set, because booting anyway builds an unauthenticated client that - # cannot run a single command on any deployment which disabled the `default` ACL user — the - # failure moves from startup to the first request, where it reads as an outage rather than a - # missing setting. Setting this to true keeps the deployment running and logs the trade. - # No Compose lane sets it: the Redis lanes authenticate with the fixture accounts instead, because - # the warning this logs is the one their "startup is silent" check exists to catch. + # Redis가 자격 증명 없이 돈다는 것을 명시적으로 인정하는 값. 자격 증명 참조가 없을 때 이 값이 없으면 + # 기동이 실패한다. 그대로 기동하면 인증 없는 client가 만들어지고, `default` ACL 사용자를 끈 배포에서는 + # 명령 하나도 돌리지 못한다 — 실패가 기동에서 첫 요청으로 옮겨 가고, 빠진 설정이 아니라 장애처럼 보인다. + # true로 두면 배포는 돌고 그 trade-off를 로그에 남긴다. + # 이 값을 쓰는 Compose lane은 없다: Redis lane은 대신 fixture 계정으로 인증한다. 이 값이 남기는 경고가 바로 + # lane의 「기동은 조용하다」 검사가 잡으려는 것이기 때문이다. type: boolean default: false allowed_values: [true, false] classification: public-config required: false - required_when: app.redis.enabled=true and no credential reference is configured + required_when: app.redis.enabled=true이고 자격 증명 참조를 설정하지 않았을 때 reload_policy: restart-only owner_branch: redis-optionality-and-composition validation: boolean_strict @@ -2069,12 +2058,11 @@ env_keys: required_test: redis-sdk:authentication-required-unless-anonymous-accepted - name: APP_REDIS_AUTHENTICATION_CREDENTIAL_REFERENCE - # Pointer to the application ACL account credential. The value lives in the secret manager. - # Form: secret://@/; the environment source reads the variable - # . Without the account part the client authenticates as `default`, which a hardened - # Redis turns off. The Compose Redis lanes use - # secret://ca-skeleton-application@environment/REDIS_LANE_APPLICATION_PASSWORD, a fixture - # account of compose/redis/acl/lane-fixture-accounts.acl. + # 애플리케이션 ACL 계정 자격 증명을 가리키는 참조. 값은 secret manager에 있다. + # 형식: secret://@/. environment source는 변수 을 읽는다. 계정 부분이 + # 없으면 client가 `default`로 인증하는데, 단단히 설정한 Redis는 그 사용자를 끈다. Compose Redis lane은 + # compose/redis/acl/lane-fixture-accounts.acl의 fixture 계정인 + # secret://ca-skeleton-application@environment/REDIS_LANE_APPLICATION_PASSWORD를 쓴다. property: app.redis.authentication.credential-reference owner_module: adapter-outbound-cache-redis type: string @@ -2105,7 +2093,7 @@ env_keys: required_test: redis-sdk:runtime-composition-binds-and-validates - name: APP_REDIS_CAPACITY_MAXIMUM_SCRIPT_CONNECTIONS - # Physical SCRIPT lane connections are bounded separately from the per-connection command queue. + # 실제 SCRIPT lane 연결 수는 연결마다의 명령 queue와 따로 제한한다. property: app.redis.capacity.maximum-script-connections owner_module: adapter-outbound-redis-runtime type: integer @@ -2121,7 +2109,7 @@ env_keys: required_test: redis-runtime:script-lane-physical-connections-bounded - name: APP_REDIS_CAPACITY_REJECT_WHEN_DISCONNECTED - # True refuses commands while disconnected. False restores the driver offline queue, which replays a burst of writes on reconnect in arbitrary order relative to the outage. + # true면 연결이 끊긴 동안 명령을 거부한다. false면 driver의 offline queue를 되살리는데, 다시 연결될 때 쌓인 쓰기를 끊긴 동안의 순서와 상관없이 몰아서 다시 보낸다. property: app.redis.capacity.reject-when-disconnected owner_module: adapter-outbound-cache-redis type: boolean @@ -2167,7 +2155,7 @@ env_keys: required_test: redis-sdk:runtime-composition-binds-and-validates - name: APP_REDIS_LIFECYCLE_ACQUIRE_TIMEOUT - # How long a lane borrow waits for a returned connection before it is refused as not sent. + # lane이 연결을 빌릴 때, 돌려받은 연결을 기다리는 시간. 넘으면 보내지 않은 것으로 거부한다. property: app.redis.lifecycle.acquire-timeout owner_module: adapter-outbound-cache-redis type: duration @@ -2213,7 +2201,7 @@ env_keys: required_test: redis-sdk:runtime-composition-binds-and-validates - name: APP_REDIS_LIFECYCLE_DRAIN_TIMEOUT - # How long shutdown waits for in-flight commands before closing connections. + # 종료할 때 연결을 닫기 전에 처리 중인 명령을 기다리는 시간. property: app.redis.lifecycle.drain-timeout owner_module: adapter-outbound-cache-redis type: duration @@ -2266,11 +2254,10 @@ env_keys: allowed_values: null classification: sensitive-config required: false - # Applied only when present: RedisTopologyClientFactory sets the sentinel credentials provider - # through ifPresent, so a Sentinel deployment whose sentinels accept unauthenticated discovery - # starts without it. The unconditional "app.redis.mode=sentinel" this used to declare was a - # requirement the runtime never enforced. - required_when: app.redis.mode=sentinel and the sentinels require authentication + # 있을 때만 적용한다: RedisTopologyClientFactory가 sentinel 자격 증명 provider를 ifPresent로 설정한다. + # 그래서 sentinel이 인증 없는 탐색을 받는 Sentinel 배포는 이 값 없이 뜬다. 예전에 적었던 무조건 + # "app.redis.mode=sentinel"은 런타임이 강제한 적 없는 요구였다. + required_when: app.redis.mode=sentinel이고 sentinel이 인증을 요구할 때 reload_policy: restart-only owner_branch: redis-optionality-and-composition validation: nonblank_when_required @@ -2300,9 +2287,9 @@ env_keys: allowed_values: null classification: public-config required: false - # Falls back to app.redis.nodes by design, so a deployment that points nodes at its sentinels - # and says nothing else is the common case rather than a misconfiguration. - required_when: app.redis.mode=sentinel and app.redis.nodes does not list the sentinels + # 설계상 app.redis.nodes로 돌아간다. 그래서 nodes에 sentinel을 적고 다른 것은 말하지 않은 배포가 잘못된 + # 설정이 아니라 흔한 경우다. + required_when: app.redis.mode=sentinel이고 app.redis.nodes에 sentinel이 없을 때 reload_policy: restart-only owner_branch: redis-optionality-and-composition validation: csv_nonempty @@ -2317,9 +2304,9 @@ env_keys: allowed_values: null classification: public-config required: false - # A key manager is configured only when this is present. Ordinary one-way TLS needs no client - # certificate, so requiring one whenever TLS is on was a claim the runtime never made. - required_when: app.redis.tls.enabled=true and the server requires mutual TLS + # key manager는 이 값이 있을 때만 설정한다. 보통의 단방향 TLS에는 client 인증서가 필요 없으니, TLS가 + # 켜질 때마다 요구하는 것은 런타임이 한 적 없는 주장이었다. + required_when: app.redis.tls.enabled=true이고 서버가 mutual TLS를 요구할 때 reload_policy: restart-only owner_branch: redis-optionality-and-composition validation: nonblank_when_required @@ -2334,10 +2321,10 @@ env_keys: allowed_values: null classification: sensitive-config required: false - # A relationship between two settings rather than a switch: a client certificate without its - # key cannot build a key manager. Enforced in RedisRuntimeSettings.validate and covered by - # RedisRuntimeSettingsTest, which is where the registry's prose conditions are proven. - required_when: app.redis.tls.client-certificate-resource is configured + # 켜고 끄는 값이 아니라 두 설정 사이의 관계다: key 없는 client 인증서로는 key manager를 만들 수 없다. + # RedisRuntimeSettings.validate가 강제하고 RedisRuntimeSettingsTest가 다룬다. 레지스트리의 글로 쓴 조건은 + # 거기서 증명한다. + required_when: app.redis.tls.client-certificate-resource를 설정했을 때 reload_policy: restart-only owner_branch: redis-optionality-and-composition validation: nonblank_when_required @@ -2360,7 +2347,7 @@ env_keys: required_test: redis-sdk:runtime-composition-binds-and-validates - name: APP_REDIS_TLS_HOSTNAME_VERIFICATION - # Disabling this accepts any certificate the trust material signs, for any host. + # 이 값을 끄면 trust material이 서명한 모든 인증서를 어떤 host에 대해서도 받는다. property: app.redis.tls.hostname-verification owner_module: adapter-outbound-cache-redis type: boolean @@ -2383,22 +2370,21 @@ env_keys: allowed_values: null classification: public-config required: false - # A trust manager is installed only when this is present; otherwise the JDK default trust - # anchors apply, which is enough for a server certificate from a public CA. - required_when: app.redis.tls.enabled=true and the server certificate is not publicly trusted + # trust manager는 이 값이 있을 때만 설치한다. 없으면 JDK 기본 신뢰 앵커를 쓰고, 공개 CA가 발급한 서버 + # 인증서에는 그것으로 충분하다. + required_when: app.redis.tls.enabled=true이고 서버 인증서가 공개 신뢰 체인에 없을 때 reload_policy: restart-only owner_branch: redis-optionality-and-composition validation: nonblank_when_required compatibility_impact: additive required_test: redis-sdk:runtime-composition-binds-and-validates - name: APP_CACHE_REDIS_ENABLED - # source: feature-integration-adapter-templates 2026-05-22 + # 출처: feature-integration-adapter-templates 2026-05-22 # "Redis | disabled optional module | cache consistency" + Adapter Template Defaults 표 - # DEPRECATED 2026-08-10: this was a second Redis master switch, and the settings class that - # bound it was removed with the previous Redis generation, so the key reached nothing. - # APP_REDIS_ENABLED is the sole global activation authority; the cache role is selected by - # app.capabilities.cache.bindings.default. The row is kept rather than deleted so a - # deployment still setting this key can be told what replaced it. + # 폐기 2026-08-10: 두 번째 Redis 전체 스위치였고, 이를 바인딩하던 settings class를 옛 Redis 세대와 함께 + # 지워서 이 키는 어디에도 닿지 않는다. 전역 켜기는 APP_REDIS_ENABLED 하나가 정한다. 캐시 role은 + # app.capabilities.cache.bindings.default가 고른다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 + # 행을 지우지 않고 둔다. deprecated_orphaned: true deprecated_alias_for: APP_REDIS_ENABLED removal_deadline: 2026-11-30 @@ -2414,9 +2400,8 @@ env_keys: required_test: adapter-contract:redis-disabled-default - name: APP_CACHE_REDIS_CLIENT_MODE - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: enum @@ -2431,12 +2416,11 @@ env_keys: required_test: adapter-contract:redis-client-mode-explicit - name: APP_CACHE_REDIS_HOST - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 - # source: feature-cache-consistency-contract — Redis adapter (활성화 시 endpoint 필요) + # 출처: feature-cache-consistency-contract — Redis adapter (켜면 endpoint가 필요하다) type: string default: null allowed_values: null @@ -2449,12 +2433,11 @@ env_keys: required_test: cache-contract:redis-host-when-enabled - name: APP_CACHE_REDIS_PORT - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 - # source: feature-cache-consistency-contract — Redis adapter endpoint + # 출처: feature-cache-consistency-contract — Redis adapter endpoint type: int default: 6379 allowed_values: null @@ -2467,9 +2450,8 @@ env_keys: required_test: cache-contract:redis-port-bound - name: APP_CACHE_REDIS_PASSWORD - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -2484,8 +2466,8 @@ env_keys: required_test: secrets-contract:redis-password-no-leak - name: APP_CACHE_REDIS_TRUST_PEM - # DEPRECATED 2026-08-10: the cache no longer owns a Redis client of its own, so no code reads this. - # Replaced by: app.redis.tls.trust-material-resource (APP_REDIS_TLS_TRUST_MATERIAL_RESOURCE), which the one Redis client uses for every capability. + # 폐기 2026-08-10: 캐시는 이제 자기 Redis client를 갖지 않아서 이 값을 읽는 코드가 없다. + # 대체: app.redis.tls.trust-material-resource (APP_REDIS_TLS_TRUST_MATERIAL_RESOURCE). Redis client 하나가 모든 capability에 이 값을 쓴다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -2500,9 +2482,8 @@ env_keys: required_test: redis-contract:cache-trust-material-no-leak - name: APP_REDIS_SEMANTIC_PROBE_MINIMUM_INTERVAL - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -2517,9 +2498,8 @@ env_keys: required_test: redis-contract:semantic-probe-cadence-bounded - name: APP_REDIS_SENTINEL_DISCOVERY_REFRESH_PERIOD - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -2534,9 +2514,8 @@ env_keys: required_test: redis-contract:sentinel-discovery-refresh-period-bounded - name: APP_REDIS_SEMANTIC_PROBE_MAXIMUM_STALENESS - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -2551,9 +2530,8 @@ env_keys: required_test: redis-contract:semantic-probe-staleness-bounded - name: APP_CACHE_REDIS_KEY_HMAC_SECRET - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -2568,9 +2546,8 @@ env_keys: required_test: cache-contract:redis-hmac-secret-bounded - name: APP_CACHE_REDIS_COMMAND_TIMEOUT - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -2585,9 +2562,8 @@ env_keys: required_test: cache-contract:redis-command-timeout-bounded - name: APP_CACHE_REDIS_MAXIMUM_QUEUED_COMMANDS - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -2602,9 +2578,8 @@ env_keys: required_test: cache-contract:redis-command-queue-bounded - name: APP_CACHE_REDIS_MAXIMUM_IN_FLIGHT_BYTES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -2631,9 +2606,9 @@ env_keys: required_test: cache-contract:redis-soft-hard-ttl-order - name: APP_CACHE_REDIS_TTL_JITTER - # DEPRECATED 2026-11-02: no settings class binds it. Its only reader was a block in the - # sample module's application.yml that nothing bound either (07-10), removed with it. - # Kept so a deployment still setting it is told it does nothing. + # 폐기 2026-11-02: 바인딩하는 settings class가 없다. 읽던 곳은 샘플 모듈 application.yml의 블록 하나뿐이었고 + # 그것도 바인딩되지 않았다(07-10). 샘플과 함께 지웠다. 아직 이 키를 쓰는 배포에 아무 일도 하지 않는다고 + # 알려 주려고 둔다. deprecated_orphaned: true removal_deadline: 2027-02-28 type: float @@ -2660,12 +2635,10 @@ env_keys: required_test: cache-contract:redis-hard-ttl-minimum - name: APP_CACHE_REDIS_NAMESPACE_ENVIRONMENT - # DEPRECATED 2026-08-10: the cache no longer renders its own key prefix. Four capabilities - # each joining two free-form tokens produced four prefixes, and the ACL pattern that was meant - # to fence the deployment in matched none of them. The row is kept (not deleted) so a - # deployment still setting it can be told what replaced it. - # Replaced by: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT), shared by - # every capability. + # 폐기 2026-08-10: 캐시는 이제 key prefix를 스스로 만들지 않는다. capability 넷이 각자 자유 형식 토큰 둘을 + # 이어 prefix 넷이 생겼고, 배포를 가두려던 ACL 패턴은 그중 어느 것과도 맞지 않았다. 아직 이 키를 쓰는 + # 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. + # 대체: app.redis.namespace.environment (APP_REDIS_NAMESPACE_ENVIRONMENT). 모든 capability가 함께 쓴다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -2680,9 +2653,8 @@ env_keys: required_test: cache-contract:redis-namespace-environment-bound - name: APP_CACHE_REDIS_SEMANTIC_REGION - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: string @@ -2697,9 +2669,8 @@ env_keys: required_test: cache-contract:redis-semantic-region-bound - name: APP_CACHE_REDIS_MAXIMUM_VALUE_BYTES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -2714,9 +2685,8 @@ env_keys: required_test: cache-contract:redis-value-size-bounded - name: APP_CACHE_REDIS_L1_ENABLED - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: boolean @@ -2731,9 +2701,8 @@ env_keys: required_test: cache-contract:redis-l1-disabled-default - name: APP_CACHE_REDIS_L1_MAXIMUM_ENTRIES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -2748,9 +2717,8 @@ env_keys: required_test: cache-contract:redis-l1-cardinality-bounded - name: APP_CACHE_REDIS_L1_MAXIMUM_WEIGHT_BYTES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -2765,9 +2733,8 @@ env_keys: required_test: cache-contract:redis-l1-weight-bounded - name: APP_CACHE_REDIS_L1_MAXIMUM_ENTRY_WEIGHT_BYTES - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -2782,9 +2749,8 @@ env_keys: required_test: cache-contract:redis-l1-entry-weight-bounded - name: APP_CACHE_REDIS_L1_TTL - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -2799,9 +2765,8 @@ env_keys: required_test: cache-contract:redis-l1-ttl-bounded - name: APP_CACHE_REDIS_L1_GENERATION_RECHECK_INTERVAL - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: duration @@ -2816,9 +2781,8 @@ env_keys: required_test: cache-contract:redis-l1-generation-recheck-bounded - name: APP_CACHE_REDIS_L1_INVALIDATION_QUEUE_CAPACITY - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 type: int @@ -2833,12 +2797,11 @@ env_keys: required_test: cache-contract:redis-l1-invalidation-queue-bounded - name: APP_CACHE_DEFAULT_TTL - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 - # source: feature-cache-consistency-contract 2026-05-22 + # 출처: feature-cache-consistency-contract 2026-05-22 # "TTL | explicit per key family | no-cache for sensitive data | immortal cache forbidden" type: duration default: 300s @@ -2852,12 +2815,11 @@ env_keys: required_test: cache-contract:default-ttl-bounded - name: APP_CACHE_NEGATIVE_TTL - # DEPRECATED 2026-08-10: the settings class that bound this property was removed - # with the previous Redis generation, so the key reached nothing. The row is kept - # (not deleted) so a deployment still setting it can be told what replaced it. + # 폐기 2026-08-10: 이 속성을 바인딩하던 settings class를 옛 Redis 세대와 함께 지워서 이 키는 어디에도 + # 닿지 않는다. 아직 이 키를 쓰는 배포에 무엇이 대신하는지 알려 주려고 행을 지우지 않고 둔다. deprecated_orphaned: true removal_deadline: 2026-11-30 - # source: feature-cache-consistency-contract 2026-05-22 + # 출처: feature-cache-consistency-contract 2026-05-22 # "negative cache 정책 = 존재하지 않는 row는 짧은 TTL(60s) 캐싱 허용" type: duration default: 60s @@ -2870,15 +2832,15 @@ env_keys: compatibility_impact: additive required_test: cache-contract:negative-ttl-bounded - # === Messaging / Kafka (feature-domain-event-outbox-contract + integration-adapter-templates) === + # === 메시징 / Kafka (feature-domain-event-outbox-contract + integration-adapter-templates) === - name: APP_MESSAGING_BROKER - # source: messaging multi-broker redesign 2026-06-16 — single active broker selection - # (app.messaging.broker=), read by the vendored messaging platform. Replaces the - # former Kafka-binary APP_MESSAGING_KAFKA_ENABLED. The application bridge no longer reads it: - # the legacy KafkaSender seam that did was removed with the canonical outbox (2026-09-28). + # 출처: messaging multi-broker redesign 2026-06-16 — 활성 broker 하나를 고른다 + # (app.messaging.broker=). 들여온 메시징 플랫폼이 읽는다. 옛 Kafka 전용 APP_MESSAGING_KAFKA_ENABLED를 + # 대신한다. 애플리케이션 bridge는 이제 읽지 않는다: 읽던 옛 KafkaSender seam은 canonical outbox와 함께 + # 지웠다(2026-09-28). type: string - # The Kafka module's config/module-defaults/messaging.yml defaults it to kafka, the only registered broker. + # Kafka 모듈의 config/module-defaults/messaging.yml이 기본값을 등록된 유일한 broker인 kafka로 둔다. default: kafka allowed_values: null classification: public-config @@ -2890,11 +2852,11 @@ env_keys: required_test: adapter-contract:messaging-broker-selection - name: APP_MESSAGING_PRODUCER_ID - # source: canonical messaging platform bridge 2026-09-18 - # Explicit logical producing-service identity for IntegrationEventPublishPort. - # Blank/absent = canonical platform bridge is not exposed; identity is never inferred. - # Every publication, the outbox relay's included, goes through that bridge, so with the - # messaging module present and on a blank value refuses startup (2026-09-28 canonical outbox). + # 출처: canonical messaging platform bridge 2026-09-18 + # IntegrationEventPublishPort가 쓰는, 메시지를 내는 서비스의 논리 이름(명시값). + # 비었거나 없음 = canonical 플랫폼 bridge를 내놓지 않는다. 이름을 짐작하지 않는다. + # outbox relay를 포함해 모든 발행이 그 bridge를 거치므로, 메시징 모듈이 있고 켜진 상태에서 값이 비면 기동을 + # 거부한다(2026-09-28 canonical outbox). type: string default: null allowed_values: null @@ -2908,11 +2870,10 @@ env_keys: required_test: adapter-contract:messaging-platform-producer-id - name: APP_MESSAGING_KAFKA_BROKERS - # source: feature-domain-event-outbox-contract — "Kafka는 optional integration adapter" - # (broker 활성화 시 endpoint 필요) - # Feeds app.messaging.brokers.kafka.bootstrap-servers (the messaging platform's Kafka - # transport) through the Kafka module's config/module-defaults/messaging.yml. - # spring.kafka.bootstrap-servers is not read. + # 출처: feature-domain-event-outbox-contract — "Kafka는 optional integration adapter" + # (broker를 켜면 endpoint가 필요하다) + # Kafka 모듈의 config/module-defaults/messaging.yml을 거쳐 app.messaging.brokers.kafka.bootstrap-servers + # (메시징 플랫폼의 Kafka transport)로 간다. spring.kafka.bootstrap-servers는 읽지 않는다. type: csv_list default: null allowed_values: null @@ -2924,10 +2885,10 @@ env_keys: compatibility_impact: behavior-change required_test: adapter-contract:kafka-brokers-when-enabled - # === Notification adapters (feature-integration-adapter-templates) === + # === 알림 adapter (feature-integration-adapter-templates) === - name: APP_NOTIFICATION_SLACK_WEBHOOK_ENABLED - # source: R0 Slack webhook provider gate; maps to app.notification.slack-webhook.enabled + # 출처: R0 Slack webhook provider 스위치. app.notification.slack-webhook.enabled로 이어진다 type: boolean default: false allowed_values: [true, false] @@ -2940,7 +2901,7 @@ env_keys: required_test: adapter-contract:notification-slack-provider-selection - name: APP_NOTIFICATION_GOOGLE_EMAIL_ENABLED - # source: R0 Google email provider gate; maps to app.notification.google-email.enabled + # 출처: R0 Google email provider 스위치. app.notification.google-email.enabled로 이어진다 type: boolean default: false allowed_values: [true, false] @@ -2952,22 +2913,20 @@ env_keys: compatibility_impact: behavior-change required_test: adapter-contract:notification-email-provider-selection - # === HTTP Client platform (app.httpclient.*) === + # === HTTP Client 플랫폼 (app.httpclient.*) === # - # Only the enabled key is registered here. The per-client surface is an indexed list whose - # element cannot be templated in application.yml without materialising a nameless client in every - # deployment, so it has no deployment-independent value for this registry to hold and is - # registered in docs/httpclient/env-fields.yaml instead. That manifest is derived from - # HttpClientPlatformSettings and enforced in both directions: a field with no entry fails - # HttpClientPlatformEnvManifestTest, and an APP_HTTPCLIENT_ variable with no field fails startup. + # 여기에는 enabled 키만 등록한다. client별 설정은 index가 붙은 목록이라, application.yml에 틀로 적으면 모든 + # 배포에 이름 없는 client가 생긴다. 그래서 배포와 상관없는 값이 없어 이 레지스트리에 둘 것이 없고, + # docs/httpclient/env-fields.yaml에 등록한다. 그 manifest는 HttpClientPlatformSettings에서 나오고 양쪽으로 + # 강제된다: 항목이 없는 필드는 HttpClientPlatformEnvManifestTest가 실패하고, 필드가 없는 APP_HTTPCLIENT_ + # 변수는 기동이 실패한다. - name: APP_HTTPCLIENT_ENABLED - # 2026-09-25 capability packaging: the module is on when present (its own config yml maps - # this key with default true); false is the explicit off. Absent from the build is the - # ordinary off state. - # While false the platform block is not bound at all: the auto-configuration that - # binds it is not processed, so no bean, connection pool, TLS context, credential, thread or - # gateway exists, and a malformed HTTP client setting cannot fail this deployment's startup. + # 2026-09-25 capability 포장: 모듈은 있으면 켜진다(모듈 자신의 설정 yml이 이 키를 기본 true로 잇는다). + # false가 명시적으로 끄는 값이다. 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. + # false인 동안 플랫폼 블록을 전혀 바인딩하지 않는다: 바인딩하는 자동 설정을 처리하지 않으므로 bean, + # connection pool, TLS context, 자격 증명, thread, gateway가 생기지 않고, 잘못된 HTTP client 설정이 이 배포의 + # 기동을 실패시킬 수 없다. type: boolean default: true allowed_values: [true, false] @@ -2980,10 +2939,9 @@ env_keys: required_test: httpclient-platform:off-state-zero-side-effects-and-env-manifest-parity - name: APP_HTTPCLIENT_ROTATION_DRAIN_TIMEOUT - # How long a retired runtime generation may keep draining after a certificate rotation before - # its connection pool is closed underneath whatever is still in flight. Rotation replaces a - # generation rather than mutating material in place, because a pool holds sockets established - # under the previous identity; this value is how long the old identity is allowed to finish. + # 인증서를 교체한 뒤, 물러난 런타임 세대가 처리 중인 것을 마저 끝낼 수 있는 기간. 이 시간이 지나면 + # 그 connection pool을 닫는다. 교체는 자료를 제자리에서 바꾸지 않고 세대를 바꾼다. pool이 옛 신원으로 맺은 + # 소켓을 들고 있기 때문이다. 이 값이 옛 신원이 일을 끝낼 수 있는 시간이다. type: duration default: 30s classification: public-config @@ -2996,11 +2954,10 @@ env_keys: # === Fileserver HTTP platform (app.fileserver-platform.*) === - name: APP_FILESERVER_PLATFORM_ENABLED - # 2026-09-25 capability packaging: the module is on when present (its own config yml maps - # this key with default true); false is the explicit off. Absent from the build is the - # ordinary off state. - # While false the platform block is not bound at all: the auto-configuration that - # binds it is not processed, so no bean, route, thread, schema check or filesystem call exists. + # 2026-09-25 capability 포장: 모듈은 있으면 켜진다(모듈 자신의 설정 yml이 이 키를 기본 true로 잇는다). + # false가 명시적으로 끄는 값이다. 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. + # false인 동안 플랫폼 블록을 전혀 바인딩하지 않는다: 바인딩하는 자동 설정을 처리하지 않으므로 bean, route, + # thread, schema 검사, 파일 시스템 호출이 생기지 않는다. type: boolean default: true allowed_values: [true, false] @@ -3013,8 +2970,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_INSTANCE_ID - # Writer-lease owner; must be unique per instance. The startup gate treats the default as - # single-instance and refuses a shared-metadata claim it cannot support. + # writer lease의 소유자. 인스턴스마다 달라야 한다. 기동 관문은 기본값을 단일 인스턴스로 보고, 지원할 수 + # 없는 공유 메타데이터 claim을 거부한다. type: string default: local-node allowed_values: null @@ -3027,7 +2984,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_DEFAULT_NAMESPACE - # Namespace applied to a request that does not name one. + # namespace를 적지 않은 요청에 쓰는 namespace. type: string default: default allowed_values: null @@ -3040,8 +2997,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_TARGET_NAMESPACES - # Namespaces copy and move may write into besides the default namespace, which is always - # allowed. Empty means the default namespace only; any other target is ACCESS_DENIED. + # copy와 move가 기본 namespace(늘 허용) 밖에 쓸 수 있는 namespace. 비면 기본 namespace만이고, 다른 + # 대상은 ACCESS_DENIED다. type: csv_list default: null allowed_values: null @@ -3054,8 +3011,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_STORAGE_ROOT - # Absolute path on its own volume. A relative root resolves against the process working - # directory, which differs between a container and a test, so it is refused. + # 자기 volume 위의 절대 경로. 상대 경로는 프로세스 실행 위치를 기준으로 풀리는데, 그 위치가 container와 + # 테스트에서 달라서 거부한다. type: string default: /var/lib/backend/files allowed_values: null @@ -3068,7 +3025,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_STORAGE_PUBLISH_MODE - # atomic-move-required fails startup when the probe cannot prove an atomic rename. + # atomic-move-required는 확인 과정이 원자적 이름 바꾸기를 증명하지 못하면 기동을 실패시킨다. type: string default: atomic-move-preferred allowed_values: [atomic-move-required, atomic-move-preferred, metadata-pointer] @@ -3081,7 +3038,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_STORAGE_BUFFER_SIZE - # Bounds every transfer allocation, so resident bytes never scale with file size. + # 모든 전송의 할당을 제한한다. 그래서 메모리에 머무는 바이트가 파일 크기에 따라 늘지 않는다. type: data_size default: 128KB allowed_values: null @@ -3094,8 +3051,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_STORAGE_FORBIDDEN_ROOT_ANCESTORS - # A storage root under a web root turns every upload into a published file; under a config - # root, into a configuration change. Both are refused at binding time. + # web root 아래의 저장소 root는 모든 업로드를 공개 파일로 만들고, config root 아래면 설정 변경으로 + # 만든다. 둘 다 바인딩할 때 거부한다. type: csv_list default: /app,/etc,/usr/share/nginx/html allowed_values: null @@ -3108,8 +3065,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_UPLOAD_MAX_FILE_SIZE - # Also drives spring.servlet.multipart.max-file-size. One placeholder for both: a smaller - # servlet ceiling rejects the upload before any Fileserver code, including its error mapping. + # spring.servlet.multipart.max-file-size도 이 값이 정한다. 둘에 자리표시자 하나다: servlet 상한이 더 + # 작으면 Fileserver 코드(오류 매핑 포함)에 닿기 전에 업로드를 거부한다. type: data_size default: 100MB allowed_values: null @@ -3135,7 +3092,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_UPLOAD_INITIAL_RESERVATION - # Quota reserved for an upload that does not declare its length. + # 길이를 밝히지 않은 업로드에 잡아 두는 할당량. type: data_size default: 8MB allowed_values: null @@ -3148,7 +3105,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_UPLOAD_MAX_PARTS - # Ceiling on parts in one multipart/batch request. + # multipart/batch 요청 하나의 part 수 상한. type: integer default: 16 allowed_values: null @@ -3161,7 +3118,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_UPLOAD_TTL - # Lifetime of an upload resource before it is reclaimable. + # 업로드 자원을 회수할 수 있게 되기까지의 수명. type: duration default: 1h allowed_values: null @@ -3174,7 +3131,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_UPLOAD_RESERVATION_TTL - # Lifetime of a quota reservation whose upload never completed. + # 업로드가 끝나지 않은 할당량 예약의 수명. type: duration default: 24h allowed_values: null @@ -3187,8 +3144,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_UPLOAD_LEASE_DURATION - # Writer lease. Renewed at one third of this while a transfer runs; a transfer that cannot - # renew is fenced out before its next physical write. + # writer lease. 전송하는 동안 이 값의 1/3마다 갱신한다. 갱신하지 못한 전송은 다음 실제 쓰기 전에 + # 막힌다(fenced). type: duration default: 30s allowed_values: null @@ -3201,7 +3158,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_UPLOAD_REQUIRE_CONTENT_LENGTH - # When true a raw upload without Content-Length is refused with 411. + # true면 Content-Length 없는 raw 업로드를 411로 거부한다. type: boolean default: false allowed_values: [true, false] @@ -3214,7 +3171,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_DOWNLOAD_CACHE_CONTROL - # Cache-Control emitted on every download response. + # 모든 다운로드 응답에 붙이는 Cache-Control. type: string default: private, no-store allowed_values: null @@ -3227,7 +3184,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_DOWNLOAD_INLINE_ALLOWED - # Inline rendering is off by default; scriptable content is forced to attachment regardless. + # inline 표시는 기본으로 꺼져 있다. script가 돌 수 있는 내용은 설정과 상관없이 attachment로 보낸다. type: boolean default: false allowed_values: [true, false] @@ -3240,7 +3197,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_DOWNLOAD_MAX_RANGES - # Multi-range is opt-in; above one the response is multipart/byteranges. + # 여러 범위 요청은 켜야 쓴다. 둘 이상이면 응답이 multipart/byteranges다. type: integer default: 1 allowed_values: null @@ -3253,8 +3210,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_DOWNLOAD_MAX_RANGE_BYTES - # Applies to the single-range profile too, so the ceiling is not inert in the default - # configuration that almost every deployment runs. + # 범위 하나 profile에도 적용한다. 그래서 거의 모든 배포가 쓰는 기본 설정에서도 상한이 실제로 + # 작동한다. type: data_size default: 100MB allowed_values: null @@ -3267,7 +3224,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_DOWNLOAD_ZERO_COPY_ENABLED - # Changes only where bytes are copied, never a header or a status. + # 바이트를 복사하는 곳만 바꾼다. 헤더나 상태 코드는 바꾸지 않는다. type: boolean default: true allowed_values: [true, false] @@ -3280,7 +3237,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_DOWNLOAD_ZERO_COPY_MINIMUM_BYTES - # Below this the syscall setup costs more than it saves. + # 이보다 작으면 syscall 준비 비용이 아끼는 것보다 크다. type: data_size default: 16MB allowed_values: null @@ -3293,7 +3250,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_TRANSFER_CORE_SIZE - # Bounded transfer pool; rejection becomes a retryable 429, never caller-runs. + # 크기가 정해진 전송 pool. 거절은 다시 시도할 수 있는 429가 되고, 호출자 스레드에서 돌리지 않는다. type: integer default: 8 allowed_values: null @@ -3306,7 +3263,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_TRANSFER_MAX_SIZE - # Upper bound of the transfer pool. + # 전송 pool의 상한. type: integer default: 32 allowed_values: null @@ -3319,7 +3276,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_TRANSFER_QUEUE_CAPACITY - # Bounded queue; an unbounded one trades a fast 429 for eventual heap exhaustion. + # 크기가 정해진 queue. 무한 queue는 빠른 429를 결국 heap 고갈로 바꾼다. type: integer default: 64 allowed_values: null @@ -3332,7 +3289,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_TRANSFER_AWAIT_SECONDS - # Shutdown drain and per-transfer caller wait. + # 종료 때 남은 일 정리 시간과 전송마다 호출자가 기다리는 시간. type: integer default: 300 allowed_values: null @@ -3345,8 +3302,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_SECURITY_ACCESS_POLICY - # No permissive default. `required` fails startup unless the deployment supplies a - # FileAccessPolicyPort bean; `unenforced` is refused under a production profile. + # 허용하는 기본값이 없다. `required`는 배포가 FileAccessPolicyPort bean을 주지 않으면 기동을 + # 실패시킨다. `unenforced`는 production profile에서 거부한다. type: string default: required allowed_values: [required, role-based, unenforced] @@ -3359,7 +3316,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_SECURITY_READ_ROLES - # Roles accepted for read operations under the role-based policy. + # role 기반 정책에서 읽기 연산에 받는 role. type: csv_list default: ROLE_FILE_READ allowed_values: null @@ -3372,7 +3329,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_SECURITY_WRITE_ROLES - # Roles accepted for write operations under the role-based policy. + # role 기반 정책에서 쓰기 연산에 받는 role. type: csv_list default: ROLE_FILE_WRITE allowed_values: null @@ -3385,8 +3342,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_SECURITY_ADMIN_ROLES - # Roles accepted for the management plane. Admin routes additionally require this role at the - # servlet chain, not only in application policy. + # 관리 기능(management plane)에 받는 role. admin route는 application 정책만이 아니라 servlet chain에서도 + # 이 role을 요구한다. type: csv_list default: ROLE_FILE_ADMIN allowed_values: null @@ -3399,7 +3356,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_VERIFICATION_TIMEOUT - # Whole-chain verification budget for one upload. + # 업로드 하나의 검증 사슬 전체 예산. type: duration default: 5s allowed_values: null @@ -3412,7 +3369,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_VERIFICATION_REQUIRE_MEDIA_TYPE_VERDICT - # When true a file whose type could not be determined is refused rather than published. + # true면 형식을 알아내지 못한 파일을 공개하지 않고 거부한다. type: boolean default: false allowed_values: [true, false] @@ -3425,8 +3382,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_VERIFICATION_INLINE_SAFE_PROFILE - # When true scriptable content is accepted instead of quarantined; only safe when downloads - # are never served inline from a trusted origin. + # true면 script가 돌 수 있는 내용을 격리하지 않고 받는다. 다운로드를 신뢰하는 origin에서 inline으로 + # 절대 내주지 않을 때만 안전하다. type: boolean default: false allowed_values: [true, false] @@ -3439,7 +3396,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_QUOTA_INSTANCE_UPLOAD_PERMITS - # Concurrent uploads admitted per instance. + # 인스턴스마다 받는 동시 업로드 수. type: integer default: 16 allowed_values: null @@ -3452,7 +3409,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_QUOTA_SCOPE_UPLOAD_PERMITS - # Concurrent uploads admitted per caller (principal). + # 호출자(principal)마다 받는 동시 업로드 수. type: integer default: 4 allowed_values: null @@ -3465,7 +3422,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_QUOTA_DIRECT_DOWNLOAD_PERMITS - # Concurrent direct downloads admitted per instance. + # 인스턴스마다 받는 동시 직접 다운로드 수. type: integer default: 64 allowed_values: null @@ -3478,7 +3435,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_QUOTA_SOFT_HIGH_WATER - # Storage fraction at which new uploads start being shed. + # 새 업로드를 덜어내기 시작하는 저장소 사용 비율. type: string default: 0.70 allowed_values: null @@ -3491,7 +3448,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_QUOTA_HARD_HIGH_WATER - # Storage fraction at which every upload is refused. + # 모든 업로드를 거부하는 저장소 사용 비율. type: string default: 0.85 allowed_values: null @@ -3504,8 +3461,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_QUOTA_NAMESPACE_LIMIT - # Most bytes one namespace may hold, live reservations plus committed usage. Empty means - # unlimited; a reservation past a set limit is refused with QUOTA_EXCEEDED (413). + # namespace 하나가 가질 수 있는 최대 바이트(살아 있는 예약과 확정된 사용량의 합). 비면 무제한이다. 정한 + # 상한을 넘는 예약은 QUOTA_EXCEEDED(413)로 거부한다. type: data_size default: null allowed_values: null @@ -3518,8 +3475,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_ADMIN_ENABLED - # Management plane, a separate decision from the data plane. Requires APP_FILESERVER_PLATFORM_ENABLED too: - # enabling it alone now does nothing instead of half-building a bean graph. + # 관리 기능(management plane). 데이터 기능과 따로 정한다. APP_FILESERVER_PLATFORM_ENABLED도 켜야 한다: + # 이 값만 켜면 이제 bean 그래프를 반쯤 만들지 않고 아무 일도 하지 않는다. type: boolean default: false allowed_values: [true, false] @@ -3532,8 +3489,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_ADMIN_ORPHAN_MINIMUM_AGE - # How long an unreferenced object must exist before a scan may name it; anything younger is - # assumed mid-commit rather than abandoned. + # 참조가 없는 객체가 scan에 이름이 오르기까지 있어야 하는 기간. 그보다 어린 것은 버려진 것이 아니라 + # 확정하는 중이라고 본다. type: duration default: 1h allowed_values: null @@ -3546,9 +3503,9 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_CLEANUP_ENABLED - # Background reclamation. On by default: without it cancelled/expired staging and rejected or - # deleted content stay on the volume until the hard high-water mark stops uploads. Turning it - # off logs a startup warning (another node or the admin plane must reclaim instead). + # 뒤에서 도는 회수. 기본으로 켜져 있다: 없으면 취소·만료된 staging과 거부·삭제된 내용이 volume에 남아, + # 결국 높은 수위(high-water mark)가 업로드를 막는다. 끄면 기동 때 경고를 남긴다(다른 노드나 관리 기능이 + # 대신 회수해야 한다). type: boolean default: true allowed_values: [true, false] @@ -3561,8 +3518,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_CLEANUP_INTERVAL - # Fixed delay between batches; sole owner of the schedule, with no @Scheduled placeholder - # carrying a second default. + # batch 사이의 고정 지연. 일정의 유일한 주인이다. 두 번째 기본값을 가진 @Scheduled 자리표시자를 두지 + # 않는다. type: duration default: 60s allowed_values: null @@ -3575,7 +3532,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_CLEANUP_MAX_ITEMS - # Item ceiling for one batch, so a backlog cannot monopolise the scheduler. + # batch 하나의 항목 수 상한. 밀린 일이 scheduler를 독차지하지 못하게 한다. type: integer default: 100 allowed_values: null @@ -3588,7 +3545,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_CLEANUP_MAX_BYTES - # Byte ceiling for one batch. + # batch 하나의 바이트 상한. type: data_size default: 1GB allowed_values: null @@ -3601,7 +3558,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_CLEANUP_RETRY_BACKOFF - # Delay before a failed cleanup item is retried. + # 실패한 정리 항목을 다시 시도하기 전 지연. type: duration default: 5m allowed_values: null @@ -3614,7 +3571,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_TUS_ENABLED - # tus 1.0. Requires APP_FILESERVER_PLATFORM_ENABLED too. + # tus 1.0. APP_FILESERVER_PLATFORM_ENABLED도 켜야 한다. type: boolean default: false allowed_values: [true, false] @@ -3627,7 +3584,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_HTTPBIS_DRAFT12_ENABLED - # Unratified draft whose contract can change without notice. Requires APP_FILESERVER_PLATFORM_ENABLED too. + # 승인되지 않은 초안이라 계약이 예고 없이 바뀔 수 있다. APP_FILESERVER_PLATFORM_ENABLED도 켜야 한다. type: boolean default: false allowed_values: [true, false] @@ -3640,8 +3597,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_NGINX_ENABLED - # Front-proxy delegation. Startup attests the internal mapping by exercising it; a mapping the - # proxy cannot resolve answers 200 with an empty body, so it fails closed instead. + # 앞단 proxy에 맡기기. 기동할 때 내부 매핑을 실제로 써 보고 확인한다. proxy가 풀지 못하는 매핑은 빈 + # 본문으로 200을 답하므로, 그대로 두지 않고 실패시킨다(fail closed). type: boolean default: false allowed_values: [true, false] @@ -3654,7 +3611,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_NGINX_INTERNAL_PREFIX - # Internal location the proxy resolves to the storage root. + # proxy가 저장소 root로 풀어 주는 내부 위치. type: string default: /__files/ allowed_values: null @@ -3667,7 +3624,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_NGINX_OBJECT_SUFFIX - # Suffix appended to the sharded object key in the internal URI. + # 내부 URI에서 shard로 나눈 객체 key 뒤에 붙이는 접미사. type: string default: .bin allowed_values: null @@ -3680,7 +3637,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_NGINX_MINIMUM_SIZE - # Below this the request is served by the application rather than delegated. + # 이보다 작은 요청은 맡기지 않고 애플리케이션이 직접 내준다. type: data_size default: 16MB allowed_values: null @@ -3693,7 +3650,7 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_OBSERVABILITY_METRICS_ENABLED - # When false neither the metrics port nor the fingerprint is created, and no key is required. + # false면 metrics port도 fingerprint도 만들지 않고 key도 요구하지 않는다. type: boolean default: true allowed_values: [true, false] @@ -3706,8 +3663,8 @@ env_keys: required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - name: APP_FILESERVER_PLATFORM_OBSERVABILITY_FINGERPRINT_KEY - # Keyed HMAC over file identifiers. An unkeyed digest of an enumerable identifier is - # reversible, so startup fails while metrics are on and this is blank. + # 파일 식별자에 거는 key 있는 HMAC. 셀 수 있는 식별자의 key 없는 digest는 되돌릴 수 있으므로, metrics가 + # 켜졌는데 이 값이 비면 기동이 실패한다. type: string default: null allowed_values: null @@ -3719,10 +3676,10 @@ env_keys: compatibility_impact: additive required_test: fileserver-platform:off-state-zero-side-effects-and-env-round-trip - # === File / Upload (feature-file-resource-handling-contract) === + # === 파일 / 업로드 (feature-file-resource-handling-contract) === - name: APP_ASYNC_EXECUTOR_CORE_SIZE - # source: feature-background-job-async-contract 2026-05-22 + # 출처: feature-background-job-async-contract 2026-05-22 # "executor pool sizing default = core=10, max=50, queue=200" type: int default: 10 @@ -3736,7 +3693,7 @@ env_keys: required_test: async-contract:executor-core-size - name: APP_ASYNC_EXECUTOR_MAX_SIZE - # source: feature-background-job-async-contract 2026-05-22 + # 출처: feature-background-job-async-contract 2026-05-22 # "core=10, max=50, queue=200" type: int default: 50 @@ -3750,7 +3707,7 @@ env_keys: required_test: async-contract:executor-max-size - name: APP_ASYNC_EXECUTOR_QUEUE_CAPACITY - # source: feature-background-job-async-contract 2026-05-22 + # 출처: feature-background-job-async-contract 2026-05-22 # "queue=200" + "unbounded queue forbidden" type: int default: 200 @@ -3763,18 +3720,15 @@ env_keys: compatibility_impact: behavior-change required_test: async-contract:executor-queue-bounded - # === Notification delivery platform (NTF-025 — configuration surface) === - # The tree exists in application.yml as app.notification.platform, disabled by - # default. Every key carries an inline default so a deployment that leaves the platform off - # supplies nothing. Reference: docs/notification/configuration.md. + # === 알림 전달 플랫폼 (NTF-025 — 설정 표면) === + # application.yml에 app.notification.platform 트리가 있고 기본으로 꺼져 있다. 모든 키가 같은 줄에 기본값을 + # 가지므로, 플랫폼을 끈 배포는 아무것도 주지 않아도 된다. 참고: docs/notification/configuration-reference.md. - name: APP_PERSISTENCE_JPA_ENABLED - # source: five-adapter-runtime-remediation §5.1 — switch for relational persistence, shipped by - # the persistence-jpa module itself (config/module-defaults/persistence-jpa.yml). The module is - # selected by one build line and is on while present; false switches off this module's beans - # (entity scan, repositories, stores, startup guards). Removing the build line removes the - # capability and this key's only reader. The old app.jpa-platform.enabled gated three add-on - # beans while reading like this one. + # 출처: five-adapter-runtime-remediation §5.1 — 관계형 영속성 스위치. persistence-jpa 모듈이 직접 + # 가진다(config/module-defaults/persistence-jpa.yml). 모듈은 빌드 한 줄로 고르고, 있는 동안 켜진다. false면 + # 이 모듈의 bean(entity scan, repository, store, 기동 관문)을 끈다. 빌드 줄을 지우면 기능과 이 키를 읽는 유일한 + # 곳이 함께 사라진다. 옛 app.jpa-platform.enabled는 이 키처럼 읽혔지만 부가 bean 셋만 막았다. type: boolean default: true allowed_values: [true, false] @@ -3861,10 +3815,9 @@ env_keys: required_test: jpa-contract:hibernate-runtime-settings - name: APP_PERSISTENCE_MONGO_ENABLED - # 2026-09-25 capability packaging: the module is on when present (its own config yml maps - # this key with default true); false is the explicit off. Absent from the build is the - # ordinary off state. - # source: five-adapter-runtime-remediation §5.1 — on/off key for MongoDB persistence. + # 2026-09-25 capability 포장: 모듈은 있으면 켜진다(모듈 자신의 설정 yml이 이 키를 기본 true로 잇는다). + # false가 명시적으로 끄는 값이다. 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. + # 출처: five-adapter-runtime-remediation §5.1 — MongoDB 영속성 켜고 끄기. type: boolean default: true allowed_values: [true, false] @@ -3876,9 +3829,8 @@ env_keys: compatibility_impact: behavior-change required_test: adapter-contract:persistence-mongo-disabled-safe - name: APP_PERSISTENCE_MONGO_ACTIVE_PROFILE - # source: five-adapter-runtime-remediation §5.1 — selects exactly one Mongo profile. The runtime - # builds one sync client and one pool; a profile present in the map but not selected has neither - # its secret resolved nor a client created. + # 출처: five-adapter-runtime-remediation §5.1 — Mongo profile을 정확히 하나 고른다. 런타임은 sync client + # 하나와 pool 하나를 만든다. map에 있지만 고르지 않은 profile은 비밀을 풀지도, client를 만들지도 않는다. type: string default: "" classification: public-config @@ -3890,15 +3842,15 @@ env_keys: compatibility_impact: behavior-change required_test: adapter-contract:persistence-mongo-active-profile - name: SPRING_MONGODB_URI - # source: persistence-mongo techlead review C1. Spring Boot 4 consumes this native key as - # spring.mongodb.uri. It is one of two valid connection sources; the alternate is the selected - # typed profile's uri-secret resolved through MongoCredentialResolver. + # 출처: persistence-mongo techlead review C1. Spring Boot 4는 이 자체 키를 spring.mongodb.uri로 쓴다. + # 유효한 연결 출처 둘 중 하나다. 다른 하나는 고른 typed profile의 uri-secret을 MongoCredentialResolver로 푼 + # 값이다. type: string default: null allowed_values: null classification: sensitive-config required: false - required_when: app.persistence-mongo.enabled=true AND no active-profile uri-secret + required_when: app.persistence-mongo.enabled=true이고 활성 profile의 uri-secret이 없을 때 reload_policy: restart-only owner_branch: persistence-mongo-runtime-remediation validation: mongodb_uri_when_selected_as_connection_source @@ -3906,11 +3858,10 @@ env_keys: required_test: adapter-contract:persistence-mongo-connection-source - name: APP_MESSAGING_ENABLED - # 2026-09-25 capability packaging: the module is on when present (its own config yml maps - # this key with default true); false is the explicit off. Absent from the build is the - # ordinary off state. - # source: five-adapter-runtime-remediation §5.1 — on/off key for broker publication. - # APP_MESSAGING_BROKER selects which transport and is no longer the de-facto switch. + # 2026-09-25 capability 포장: 모듈은 있으면 켜진다(모듈 자신의 설정 yml이 이 키를 기본 true로 잇는다). + # false가 명시적으로 끄는 값이다. 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. + # 출처: five-adapter-runtime-remediation §5.1 — broker 발행 켜고 끄기. + # APP_MESSAGING_BROKER는 어느 transport인지만 고르고, 이제 사실상의 스위치가 아니다. type: boolean default: true allowed_values: [true, false] @@ -3921,15 +3872,14 @@ env_keys: validation: boolean compatibility_impact: behavior-change required_test: adapter-contract:messaging-disabled-safe - # === Optional WebSocket build-composition contract === - # These keys map directly to app.websocket.* when the websocket leaf is present in a chosen - # composition. The default bootJar does not contain that leaf; presence remains a build-time - # decision and these rows do not imply runtime membership. + # === 선택형 WebSocket 빌드 조립 계약 === + # 고른 조립에 websocket leaf가 있으면 이 키들이 app.websocket.*로 바로 이어진다. 기본 bootJar에는 그 leaf가 + # 없다. 있을지는 빌드할 때 정하고, 이 행들이 런타임에 들어 있다는 뜻은 아니다. - name: APP_WEBSOCKET_ENABLED - # 2026-09-25 capability packaging: the module is on when present (its own config yml maps - # this key with default true); false is the explicit off. Absent from the build is the - # ordinary off state. + # 2026-09-25 capability 포장: 모듈은 있으면 켜진다(모듈 자신의 설정 yml이 이 키를 + # 기본 true로 잇는다). false가 명시적으로 끄는 값이다. 빌드에 모듈이 없는 것이 + # 보통의 꺼진 상태다. property: app.websocket.enabled owner_module: adapter-inbound-websocket type: boolean @@ -4000,7 +3950,7 @@ env_keys: required_test: websocket-contract:canonical-property-namespace - name: APP_WEBSOCKET_MESSAGE_SIZE_LIMIT - # Spring's own default, now explicit (review 03-06); at most 2147483647 bytes. + # Spring 자체 기본값을 명시했다(review 03-06). 최대 2147483647 bytes. property: app.websocket.message-size-limit owner_module: adapter-inbound-websocket type: data_size @@ -4015,7 +3965,7 @@ env_keys: required_test: websocket-contract:canonical-property-namespace - name: APP_WEBSOCKET_SEND_BUFFER_SIZE_LIMIT - # Spring's own default, now explicit (review 03-06); at most 2147483647 bytes. + # Spring 자체 기본값을 명시했다(review 03-06). 최대 2147483647 bytes. property: app.websocket.send-buffer-size-limit owner_module: adapter-inbound-websocket type: data_size @@ -4030,7 +3980,7 @@ env_keys: required_test: websocket-contract:canonical-property-namespace - name: APP_WEBSOCKET_SEND_TIME_LIMIT - # Spring's own default, now explicit (review 03-06); at most 2147483647 ms. + # Spring 자체 기본값을 명시했다(review 03-06). 최대 2147483647 ms. property: app.websocket.send-time-limit owner_module: adapter-inbound-websocket type: duration @@ -4045,7 +3995,7 @@ env_keys: required_test: websocket-contract:canonical-property-namespace - name: APP_WEBSOCKET_TIME_TO_FIRST_MESSAGE - # Spring's own default, now explicit (review 03-06); at most 2147483647 ms. + # Spring 자체 기본값을 명시했다(review 03-06). 최대 2147483647 ms. property: app.websocket.time-to-first-message owner_module: adapter-inbound-websocket type: duration @@ -4060,7 +4010,8 @@ env_keys: required_test: websocket-contract:canonical-property-namespace - name: APP_WEBSOCKET_MAX_CONNECTIONS - # New per-node STOMP session ceiling (review 03-06); the next session is closed with 1013. 1000 x 512KB send buffer bounds worst-case outbound buffering near 512 MiB. + # 노드마다의 새 STOMP session 상한(review 03-06). 그 다음 session은 1013으로 닫는다. 1000 x 512KB 송신 + # 버퍼라 최악의 송신 버퍼링이 512 MiB 근처로 묶인다. property: app.websocket.max-connections owner_module: adapter-inbound-websocket type: integer @@ -4075,10 +4026,9 @@ env_keys: required_test: websocket-contract:canonical-property-namespace - name: APP_OBJECTSTORAGE_ENABLED - # 2026-11-03 RR-06-07: the explicit off the Compose smoke wrapper sets for every lane that is - # not about object storage. It bound by relaxed binding and was in no registry, so the env - # contract could not tell it from an unread name. The module is on when present; absent from - # the build is the ordinary off state. + # 2026-11-03 RR-06-07: Compose smoke wrapper가 객체 저장소와 상관없는 모든 lane에 거는 명시적 끄기 값. + # relaxed binding으로 바인딩되면서 어느 레지스트리에도 없어, env 계약이 읽히지 않는 이름과 구별하지 못했다. + # 모듈은 있으면 켜진다. 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. property: app.object-storage.enabled owner_module: adapter-outbound-objectstorage type: boolean @@ -4092,9 +4042,9 @@ env_keys: compatibility_impact: none required_test: off-state-zero-side-effects-and-env-round-trip - name: APP_GRPC_SERVER_ENABLED - # 2026-11-03 RR-06-07: the explicit off for the gRPC server the Compose lanes set (it replaced - # CASKELETON_GRPC_ENABLED, which nothing read). The module is on when present; absent from the - # build is the ordinary off state. + # 2026-11-03 RR-06-07: Compose lane이 거는 gRPC 서버의 명시적 끄기 값(아무도 읽지 않던 + # CASKELETON_GRPC_ENABLED를 대신했다). 모듈은 있으면 켜진다. 빌드에 모듈이 없는 것이 보통의 꺼진 + # 상태다. property: app.grpc.server.enabled owner_module: adapter-inbound-grpc type: boolean @@ -4108,11 +4058,10 @@ env_keys: compatibility_impact: none required_test: off-state-zero-side-effects-and-env-round-trip - name: APP_GRAPHQL_ENABLED - # 2026-09-25 capability packaging: the module is on when present (its own config yml maps - # this key with default true); false is the explicit off. Absent from the build is the - # ordinary off state. - # source: five-adapter-runtime-remediation §5.1 — on/off key for the GraphQL transport. - # false publishes no /graphql route, including the one Spring GraphQL would publish by itself. + # 2026-09-25 capability 포장: 모듈은 있으면 켜진다(모듈 자신의 설정 yml이 이 키를 기본 true로 잇는다). + # false가 명시적으로 끄는 값이다. 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. + # 출처: five-adapter-runtime-remediation §5.1 — GraphQL transport 켜고 끄기. + # false면 /graphql route를 내지 않는다. Spring GraphQL이 스스로 내는 route도 포함이다. type: boolean default: true allowed_values: [true, false] @@ -4124,10 +4073,9 @@ env_keys: compatibility_impact: behavior-change required_test: adapter-contract:graphql-disabled-safe - name: APP_GRAPHQL_DEPLOYMENT_MODE - # source: five-adapter-runtime-remediation §5.1 / GQL-INT-002 — replaces app.graphql.production - # and app.graphql.environment, which defaulted to production=false with - # environment=PRODUCTION_PUBLIC and let anonymous-principal and allow-by-default authorization - # read one axis while the other claimed production. + # 출처: five-adapter-runtime-remediation §5.1 / GQL-INT-002 — app.graphql.production과 + # app.graphql.environment를 대신한다. 둘의 기본값이 production=false와 environment=PRODUCTION_PUBLIC이라, + # 익명 principal과 기본 허용 권한 검사는 한 축을 읽고 다른 축은 production이라 주장했다. type: enum default: "" allowed_values: [LOCAL, DEV, PRODUCTION_INTERNAL, PRODUCTION_PUBLIC] @@ -4290,9 +4238,9 @@ env_keys: required_test: graphql-contract:wired-operator-settings - name: APP_OUTBOX_ENABLED - # source: five-adapter-runtime-remediation §6.1 JPA-INT-004 — the outbox capability switch. - # relay-enabled below only starts the scheduler; conflating the two meant a relay-off deployment - # still assembled outbox metrics over a store port a database-less runtime does not have. + # 출처: five-adapter-runtime-remediation §6.1 JPA-INT-004 — outbox 기능 스위치. + # 아래 relay-enabled는 scheduler만 시작한다. 둘을 섞으면 relay를 끈 배포도 DB 없는 런타임에는 없는 store + # port 위에 outbox metrics를 조립했다. type: boolean default: false allowed_values: [true, false] @@ -4304,10 +4252,9 @@ env_keys: compatibility_impact: behavior-change required_test: adapter-contract:outbox-capability-disabled-safe - name: APP_OUTBOX_RELAY_ENABLED - # source: five-adapter-runtime-remediation §6.3 MSG-INT-001 — starts the relay scheduler. - # Requires APP_OUTBOX_ENABLED, APP_PERSISTENCE_JPA_ENABLED and APP_MESSAGING_ENABLED with - # APP_MESSAGING_PRODUCER_ID; the shipped default was true beside a blank broker, which refused - # every startup. + # 출처: five-adapter-runtime-remediation §6.3 MSG-INT-001 — relay scheduler를 시작한다. + # APP_OUTBOX_ENABLED, APP_PERSISTENCE_JPA_ENABLED, APP_MESSAGING_ENABLED와 APP_MESSAGING_PRODUCER_ID가 + # 필요하다. 예전 기본값은 broker가 빈 채로 true라 모든 기동을 거부했다. type: boolean default: false allowed_values: [true, false] @@ -4319,10 +4266,10 @@ env_keys: compatibility_impact: behavior-change required_test: adapter-contract:outbox-relay-dependency - name: APP_NOTIFICATION_PLATFORM_ENABLED - # 2026-09-25 capability packaging: the notification-platform module is on when present (its - # config/module-defaults/notification.yml maps this key with default true); false is the - # explicit off and binds nothing at all. Absent from the build is the ordinary off state. - # source: NTF-025. + # 2026-09-25 capability 포장: notification-platform 모듈은 있으면 켜진다(모듈의 + # config/module-defaults/notification.yml이 이 키를 기본 true로 잇는다). false가 명시적으로 끄는 값이고 + # 아무것도 바인딩하지 않는다. 빌드에 모듈이 없는 것이 보통의 꺼진 상태다. + # 출처: NTF-025. type: boolean default: true allowed_values: [true, false] @@ -4335,9 +4282,8 @@ env_keys: required_test: adapter-contract:notification-platform-disabled-safe - name: APP_NOTIFICATION_PLATFORM_DEFAULT_LOCALE - # I-6b: the locale a submission that names none is rendered in. The accept use case applies - # it; the HTTP controller used to pick the host JVM's Locale.getDefault(), so the same request - # rendered differently per node. + # I-6b: locale을 적지 않은 제출을 그릴 locale. 접수 use case가 적용한다. 예전에는 HTTP controller가 host + # JVM의 Locale.getDefault()를 골라, 같은 요청이 노드마다 다르게 그려졌다. type: string default: ko-KR allowed_values: null @@ -4350,10 +4296,10 @@ env_keys: required_test: application-contract:notification-default-locale - name: APP_NOTIFICATION_PLATFORM_CONTACT_ENCRYPTION_KEY - # source: NTF-INT-007 — Encrypts recipient contact points at rest — addresses and phone numbers. - # Full row owned by secrets-classification.yaml. Bound by - # app.notification.platform.secrets.contact-encryption-key; the platform decodes it at startup and - # refuses to boot if it is blank, shorter than 32 bytes, or equal to another purpose's key. + # 출처: NTF-INT-007 — 저장된 수신자 연락처(주소와 전화번호)를 암호화한다. + # 행 전체는 secrets-classification.yaml이 가진다. 바인딩 위치: + # app.notification.platform.secrets.contact-encryption-key. 플랫폼이 기동할 때 값을 풀고, + # 비었거나 32바이트보다 짧거나 다른 용도의 key와 같으면 기동을 거부한다. type: string default: null allowed_values: null @@ -4366,10 +4312,10 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_CONTACT_LOOKUP_HMAC_KEY - # source: NTF-INT-007 — Blind index over contact points, so a lookup never needs the plaintext. - # Full row owned by secrets-classification.yaml. Bound by - # app.notification.platform.secrets.contact-lookup-hmac-key; the platform decodes it at startup and - # refuses to boot if it is blank, shorter than 32 bytes, or equal to another purpose's key. + # 출처: NTF-INT-007 — 연락처의 blind index. 조회에 평문이 필요 없게 한다. + # 행 전체는 secrets-classification.yaml이 가진다. 바인딩 위치: + # app.notification.platform.secrets.contact-lookup-hmac-key. 플랫폼이 기동할 때 값을 풀고, + # 비었거나 32바이트보다 짧거나 다른 용도의 key와 같으면 기동을 거부한다. type: string default: null allowed_values: null @@ -4382,10 +4328,10 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_CALLBACK_SIGNING_KEY - # source: NTF-INT-007 — Signs the callback URLs a provider posts delivery outcomes back to. - # Full row owned by secrets-classification.yaml. Bound by - # app.notification.platform.secrets.callback-signing-key; the platform decodes it at startup and - # refuses to boot if it is blank, shorter than 32 bytes, or equal to another purpose's key. + # 출처: NTF-INT-007 — provider가 전달 결과를 보내는 callback URL에 서명한다. + # 행 전체는 secrets-classification.yaml이 가진다. 바인딩 위치: + # app.notification.platform.secrets.callback-signing-key. 플랫폼이 기동할 때 값을 풀고, + # 비었거나 32바이트보다 짧거나 다른 용도의 key와 같으면 기동을 거부한다. type: string default: null allowed_values: null @@ -4398,10 +4344,10 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY - # source: NTF-INT-007 — Encrypts stored provider credentials, which are themselves secrets. - # Full row owned by secrets-classification.yaml. Bound by - # app.notification.platform.secrets.provider-credential-key; the platform decodes it at startup and - # refuses to boot if it is blank, shorter than 32 bytes, or equal to another purpose's key. + # 출처: NTF-INT-007 — 저장된 provider 자격 증명(그 자체가 비밀)을 암호화한다. + # 행 전체는 secrets-classification.yaml이 가진다. 바인딩 위치: + # app.notification.platform.secrets.provider-credential-key. 플랫폼이 기동할 때 값을 풀고, + # 비었거나 32바이트보다 짧거나 다른 용도의 key와 같으면 기동을 거부한다. type: string default: null allowed_values: null @@ -4414,10 +4360,10 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY - # source: NTF-INT-007 — Encrypts notification variables and retained callback bodies at rest. - # Full row owned by secrets-classification.yaml. Bound by - # app.notification.platform.secrets.payload-encryption-key; the platform decodes it at startup and - # refuses to boot if it is blank, shorter than 32 bytes, or equal to another purpose's key. + # 출처: NTF-INT-007 — 저장된 알림 변수와 보관한 callback 본문을 암호화한다. + # 행 전체는 secrets-classification.yaml이 가진다. 바인딩 위치: + # app.notification.platform.secrets.payload-encryption-key. 플랫폼이 기동할 때 값을 풀고, + # 비었거나 32바이트보다 짧거나 다른 용도의 key와 같으면 기동을 거부한다. type: string default: null allowed_values: null @@ -4430,10 +4376,10 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY - # source: NTF-INT-007 — Keyed hash of provider request ids, which are provider-side identifiers. - # Full row owned by secrets-classification.yaml. Bound by - # app.notification.platform.secrets.provider-request-lookup-hmac-key; the platform decodes it at startup and - # refuses to boot if it is blank, shorter than 32 bytes, or equal to another purpose's key. + # 출처: NTF-INT-007 — provider 쪽 식별자인 provider request id의 key 있는 hash. + # 행 전체는 secrets-classification.yaml이 가진다. 바인딩 위치: + # app.notification.platform.secrets.provider-request-lookup-hmac-key. 플랫폼이 기동할 때 값을 풀고, + # 비었거나 32바이트보다 짧거나 다른 용도의 key와 같으면 기동을 거부한다. type: string default: null allowed_values: null @@ -4446,10 +4392,10 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_CALLBACK_FINGERPRINT_HMAC_KEY - # source: NTF-INT-007 — Keyed fingerprint of callback bodies, used to detect replays. - # Full row owned by secrets-classification.yaml. Bound by - # app.notification.platform.secrets.callback-fingerprint-hmac-key; the platform decodes it at startup and - # refuses to boot if it is blank, shorter than 32 bytes, or equal to another purpose's key. + # 출처: NTF-INT-007 — callback 본문의 key 있는 fingerprint. replay를 찾는 데 쓴다. + # 행 전체는 secrets-classification.yaml이 가진다. 바인딩 위치: + # app.notification.platform.secrets.callback-fingerprint-hmac-key. 플랫폼이 기동할 때 값을 풀고, + # 비었거나 32바이트보다 짧거나 다른 용도의 key와 같으면 기동을 거부한다. type: string default: null allowed_values: null @@ -4462,9 +4408,9 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_CONTACT_ENCRYPTION_KEY_ID - # source: NTF-INT-007 — the id written into every envelope the CONTACT_ENCRYPTION key produces. - # An identifier, not key material, so it is public-config; the material itself is the - # APP_NOTIFICATION_PLATFORM_CONTACT_ENCRYPTION_KEY row above. Bound into + # 출처: NTF-INT-007 — CONTACT_ENCRYPTION key가 만드는 모든 envelope에 적는 id. + # key 자료가 아니라 식별자라 public-config다. 자료 자체는 위의 + # APP_NOTIFICATION_PLATFORM_CONTACT_ENCRYPTION_KEY 행이다. 바인딩 위치: # app.notification.platform.secrets.active-key-ids.CONTACT_ENCRYPTION. type: string default: null @@ -4478,9 +4424,9 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_CONTACT_LOOKUP_HMAC_KEY_ID - # source: NTF-INT-007 — the id written into every envelope the CONTACT_LOOKUP_HMAC key produces. - # An identifier, not key material, so it is public-config; the material itself is the - # APP_NOTIFICATION_PLATFORM_CONTACT_LOOKUP_HMAC_KEY row above. Bound into + # 출처: NTF-INT-007 — CONTACT_LOOKUP_HMAC key가 만드는 모든 envelope에 적는 id. + # key 자료가 아니라 식별자라 public-config다. 자료 자체는 위의 + # APP_NOTIFICATION_PLATFORM_CONTACT_LOOKUP_HMAC_KEY 행이다. 바인딩 위치: # app.notification.platform.secrets.active-key-ids.CONTACT_LOOKUP_HMAC. type: string default: null @@ -4494,9 +4440,9 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_CALLBACK_SIGNING_KEY_ID - # source: NTF-INT-007 — the id written into every envelope the CALLBACK_SIGNING key produces. - # An identifier, not key material, so it is public-config; the material itself is the - # APP_NOTIFICATION_PLATFORM_CALLBACK_SIGNING_KEY row above. Bound into + # 출처: NTF-INT-007 — CALLBACK_SIGNING key가 만드는 모든 envelope에 적는 id. + # key 자료가 아니라 식별자라 public-config다. 자료 자체는 위의 + # APP_NOTIFICATION_PLATFORM_CALLBACK_SIGNING_KEY 행이다. 바인딩 위치: # app.notification.platform.secrets.active-key-ids.CALLBACK_SIGNING. type: string default: null @@ -4510,9 +4456,9 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY_ID - # source: NTF-INT-007 — the id written into every envelope the PROVIDER_CREDENTIAL key produces. - # An identifier, not key material, so it is public-config; the material itself is the - # APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY row above. Bound into + # 출처: NTF-INT-007 — PROVIDER_CREDENTIAL key가 만드는 모든 envelope에 적는 id. + # key 자료가 아니라 식별자라 public-config다. 자료 자체는 위의 + # APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY 행이다. 바인딩 위치: # app.notification.platform.secrets.active-key-ids.PROVIDER_CREDENTIAL. type: string default: null @@ -4526,9 +4472,9 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY_ID - # source: NTF-INT-007 — the id written into every envelope the PAYLOAD_ENCRYPTION key produces. - # An identifier, not key material, so it is public-config; the material itself is the - # APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY row above. Bound into + # 출처: NTF-INT-007 — PAYLOAD_ENCRYPTION key가 만드는 모든 envelope에 적는 id. + # key 자료가 아니라 식별자라 public-config다. 자료 자체는 위의 + # APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY 행이다. 바인딩 위치: # app.notification.platform.secrets.active-key-ids.PAYLOAD_ENCRYPTION. type: string default: null @@ -4542,9 +4488,9 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY_ID - # source: NTF-INT-007 — the id written into every envelope the PROVIDER_REQUEST_LOOKUP_HMAC key produces. - # An identifier, not key material, so it is public-config; the material itself is the - # APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY row above. Bound into + # 출처: NTF-INT-007 — PROVIDER_REQUEST_LOOKUP_HMAC key가 만드는 모든 envelope에 적는 id. + # key 자료가 아니라 식별자라 public-config다. 자료 자체는 위의 + # APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY 행이다. 바인딩 위치: # app.notification.platform.secrets.active-key-ids.PROVIDER_REQUEST_LOOKUP_HMAC. type: string default: null @@ -4558,9 +4504,9 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_CALLBACK_FINGERPRINT_HMAC_KEY_ID - # source: NTF-INT-007 — the id written into every envelope the CALLBACK_FINGERPRINT_HMAC key produces. - # An identifier, not key material, so it is public-config; the material itself is the - # APP_NOTIFICATION_PLATFORM_CALLBACK_FINGERPRINT_HMAC_KEY row above. Bound into + # 출처: NTF-INT-007 — CALLBACK_FINGERPRINT_HMAC key가 만드는 모든 envelope에 적는 id. + # key 자료가 아니라 식별자라 public-config다. 자료 자체는 위의 + # APP_NOTIFICATION_PLATFORM_CALLBACK_FINGERPRINT_HMAC_KEY 행이다. 바인딩 위치: # app.notification.platform.secrets.active-key-ids.CALLBACK_FINGERPRINT_HMAC. type: string default: null @@ -4574,7 +4520,7 @@ env_keys: required_test: adapter-contract:notification-secret-material-required - name: APP_NOTIFICATION_PLATFORM_SES_ENABLED - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: boolean default: false allowed_values: [true, false] @@ -4587,7 +4533,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_PRIMARY - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: boolean default: false allowed_values: [true, false] @@ -4600,7 +4546,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_ENVIRONMENT - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: string default: PRODUCTION allowed_values: null @@ -4613,7 +4559,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_CREDENTIAL_KEY_ID - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: string default: null allowed_values: null @@ -4626,7 +4572,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_TIMEOUT - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: duration default: 10s allowed_values: null @@ -4639,7 +4585,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_MAX_CONCURRENCY - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: int default: 8 allowed_values: null @@ -4652,7 +4598,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_RATE_PER_SECOND - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: int default: 20 allowed_values: null @@ -4665,7 +4611,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_ENDPOINT - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: string default: https://email.us-east-1.amazonaws.com allowed_values: null @@ -4678,7 +4624,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_REGION - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: string default: us-east-1 allowed_values: null @@ -4691,7 +4637,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_SENDER_IDENTITY - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: string default: null allowed_values: null @@ -4704,7 +4650,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_ACCESS_KEY_ID - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: string default: null allowed_values: null @@ -4717,7 +4663,7 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_CONFIGURATION_SET - # source: notification/fileserver H4-B — shipped SES dispatch assembler. + # 출처: notification/fileserver H4-B — 기본으로 들어 있는 SES 발송 조립기. type: string default: null allowed_values: null @@ -4730,9 +4676,9 @@ env_keys: required_test: adapter-contract:notification-ses-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SES_ALLOWED_TOPIC_ARNS - # source: 2026-09-24 module review Critical #10 — SNS topics whose SES event callbacks the - # shipped SES profile accepts. A valid SNS signature only proves AWS sent the message and - # anyone can own a topic, so binding fails when callbacks are enabled and this is empty. + # 출처: 2026-09-24 module review Critical #10 — 기본 SES profile이 받는 SES 이벤트 callback의 SNS topic. + # SNS 서명이 맞다는 것은 AWS가 보냈다는 것만 증명하고, topic은 누구나 가질 수 있다. 그래서 callback을 켰는데 + # 이 값이 비면 바인딩이 실패한다. type: csv default: "" allowed_values: null @@ -4745,7 +4691,7 @@ env_keys: required_test: adapter-contract:notification-ses-callback-topic-allowlist - name: APP_NOTIFICATION_PLATFORM_SMTP_ENABLED - # source: NTF-INT-001 — on/off key of the shipped SMTP provider profile; false means assembly skips it entirely. + # 출처: NTF-INT-001 — 기본 SMTP provider profile 켜고 끄기. false면 조립에서 통째로 뺀다. type: boolean default: false allowed_values: [true, false] @@ -4758,7 +4704,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_PRIMARY - # source: NTF-INT-001 — whether this profile is the primary route for EMAIL; exactly one primary per channel. + # 출처: NTF-INT-001 — 이 profile이 EMAIL의 주 경로인지. 채널마다 주 경로는 정확히 하나다. type: boolean default: true allowed_values: [true, false] @@ -4771,7 +4717,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_ENVIRONMENT - # source: NTF-INT-001 — the profile's declared environment, carried on every dispatch record. + # 출처: NTF-INT-001 — profile이 밝힌 환경. 모든 발송 기록에 실린다. type: string default: local allowed_values: null @@ -4784,7 +4730,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_CREDENTIAL_PROFILE - # source: NTF-INT-001 — the credential profile the relay's credentials are resolved through. + # 출처: NTF-INT-001 — relay 자격 증명을 푸는 credential profile. type: string default: default allowed_values: null @@ -4797,7 +4743,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_TIMEOUT - # source: NTF-INT-001 — per-attempt provider timeout for this profile. + # 출처: NTF-INT-001 — 이 profile의 시도마다 provider timeout. type: duration default: 10s allowed_values: null @@ -4810,7 +4756,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_MAX_CONCURRENCY - # source: NTF-INT-001 — how many attempts this profile may have in flight. + # 출처: NTF-INT-001 — 이 profile이 동시에 처리할 수 있는 시도 수. type: int default: 4 allowed_values: null @@ -4823,7 +4769,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_RATE_PER_SECOND - # source: NTF-INT-001 — the profile's attempt rate limit. + # 출처: NTF-INT-001 — profile의 시도 속도 제한. type: int default: 10 allowed_values: null @@ -4836,7 +4782,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_SENDER_IDENTITY - # source: NTF-INT-001 — the envelope sender every message is sent as. + # 출처: NTF-INT-001 — 모든 메시지를 보내는 envelope 발신자. type: string default: no-reply@example.invalid allowed_values: null @@ -4849,7 +4795,7 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: APP_NOTIFICATION_PLATFORM_SMTP_DISPATCH_CONCURRENCY - # source: NTF-INT-001 — size of the bounded executor SMTP sends run on. + # 출처: NTF-INT-001 — SMTP 발송이 도는, 크기가 정해진 executor의 크기. type: int default: 4 allowed_values: null @@ -4862,8 +4808,8 @@ env_keys: required_test: adapter-contract:notification-smtp-provider-assembled - name: SPRING_MAIL_HOST - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.host owner_module: adapter-outbound-notification type: string @@ -4879,8 +4825,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_PORT - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.port owner_module: adapter-outbound-notification type: integer @@ -4896,8 +4842,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_USERNAME - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.username owner_module: adapter-outbound-notification type: string @@ -4913,8 +4859,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_PASSWORD - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.password owner_module: adapter-outbound-notification type: string @@ -4930,8 +4876,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_PROPERTIES_MAIL_SMTP_STARTTLS_ENABLE - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.properties.mail.smtp.starttls.enable owner_module: adapter-outbound-notification type: boolean @@ -4947,8 +4893,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_PROPERTIES_MAIL_SMTP_STARTTLS_REQUIRED - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.properties.mail.smtp.starttls.required owner_module: adapter-outbound-notification type: boolean @@ -4964,8 +4910,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_PROPERTIES_MAIL_SMTP_CONNECTIONTIMEOUT - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.properties.mail.smtp.connectiontimeout owner_module: adapter-outbound-notification type: integer @@ -4981,8 +4927,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_PROPERTIES_MAIL_SMTP_TIMEOUT - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.properties.mail.smtp.timeout owner_module: adapter-outbound-notification type: integer @@ -4998,8 +4944,8 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: SPRING_MAIL_PROPERTIES_MAIL_SMTP_WRITETIMEOUT - # source: notification/fileserver techlead review H2 — native Spring Mail transport - # consumed by the JavaMailSender that the shipped SMTP assembler validates and uses. + # 출처: notification/fileserver techlead review H2 — Spring Mail 자체 transport 설정. 기본 SMTP 조립기가 + # 검증하고 쓰는 JavaMailSender가 읽는다. property: spring.mail.properties.mail.smtp.writetimeout owner_module: adapter-outbound-notification type: integer @@ -5015,9 +4961,9 @@ env_keys: required_test: adapter-contract:notification-smtp-transport - name: APP_OPENAPI_DOCS_ENABLED - # source: five-adapter-runtime-remediation §9 — whether /v3/api-docs is served; application-prod.yml pins it false. Stated rather than defaulted because - # SpringDoc warns on every startup until a deployment decides, and a warning on every start is - # one nobody reads. + # 출처: five-adapter-runtime-remediation §9 — /v3/api-docs를 내줄지. application-prod.yml이 false로 + # 고정한다. 기본값에 맡기지 않고 적는 이유: 배포가 정할 때까지 SpringDoc이 기동마다 경고하고, 기동마다 나는 + # 경고는 아무도 읽지 않는다. type: boolean default: true allowed_values: [true, false] @@ -5030,9 +4976,9 @@ env_keys: required_test: env-contract:openapi-exposure-decided - name: APP_OPENAPI_UI_ENABLED - # source: five-adapter-runtime-remediation §9 — whether the Swagger UI is served; application-prod.yml pins it false. Stated rather than defaulted because - # SpringDoc warns on every startup until a deployment decides, and a warning on every start is - # one nobody reads. + # 출처: five-adapter-runtime-remediation §9 — Swagger UI를 내줄지. application-prod.yml이 false로 고정한다. + # 기본값에 맡기지 않고 적는 이유: 배포가 정할 때까지 SpringDoc이 기동마다 경고하고, 기동마다 나는 경고는 + # 아무도 읽지 않는다. type: boolean default: true allowed_values: [true, false] @@ -5045,10 +4991,10 @@ env_keys: required_test: env-contract:openapi-exposure-decided - name: APP_NOTIFICATION_PLATFORM_MODE - # source: NTF-025 — SERVING refuses to start without a working provider; INGEST_ONLY stores and does not dispatch. - # The constant is INGEST_ONLY. This row said ACCEPT_ONLY, a name NotificationPlatformMode has - # never had, so an operator following the registry got a binding failure naming a value the - # documentation does not mention. NotificationModeSsotTest derives the list below from the enum. + # 출처: NTF-025 — SERVING은 동작하는 provider 없이 기동을 거부한다. INGEST_ONLY는 저장만 하고 보내지 않는다. + # 상수는 INGEST_ONLY다. 이 행은 ACCEPT_ONLY라 했는데, NotificationPlatformMode에 그런 이름은 없었다. 그래서 + # 레지스트리를 따른 운영자는 문서에 없는 값을 지목하는 바인딩 실패를 받았다. NotificationModeSsotTest가 아래 + # 목록을 enum에서 만든다. type: enum default: SERVING allowed_values: [SERVING, INGEST_ONLY] @@ -5061,7 +5007,7 @@ env_keys: required_test: adapter-contract:notification-platform-mode - name: APP_NOTIFICATION_PLATFORM_CLAIM_BATCH_SIZE - # source: NTF-025 — how many recipient deliveries one scheduler pass claims; 1..1000, refused outside that at binding + # 출처: NTF-025 — scheduler 한 번이 claim하는 수신자 전달 수. 1..1000이고 밖이면 바인딩에서 거부한다 type: integer default: 50 allowed_values: null @@ -5074,7 +5020,7 @@ env_keys: required_test: adapter-contract:notification-dispatch-bounds - name: APP_NOTIFICATION_PLATFORM_LEASE_DURATION - # source: NTF-025 — must outlast a provider call plus its timeout, or a live worker's delivery is claimed by a second one + # 출처: NTF-025 — provider 호출과 그 timeout보다 길어야 한다. 아니면 살아 있는 worker의 전달을 다른 worker가 claim한다 type: duration default: 2m allowed_values: null @@ -5087,7 +5033,7 @@ env_keys: required_test: adapter-contract:notification-lease-fencing - name: APP_NOTIFICATION_PLATFORM_POLL_INTERVAL - # source: NTF-025 — how often the scheduler asks for work when the last pass claimed nothing + # 출처: NTF-025 — 지난 차례에 claim한 것이 없을 때 scheduler가 일을 다시 묻는 간격 type: duration default: 1s allowed_values: null @@ -5100,7 +5046,7 @@ env_keys: required_test: adapter-contract:notification-dispatch-bounds - name: APP_NOTIFICATION_PLATFORM_MAX_CONCURRENCY - # source: NTF-025 — ceiling on in-flight provider calls across the whole process + # 출처: NTF-025 — 프로세스 전체에서 처리 중인 provider 호출 수 상한 type: integer default: 64 allowed_values: null @@ -5113,7 +5059,7 @@ env_keys: required_test: adapter-contract:notification-dispatch-bounds - name: APP_NOTIFICATION_PLATFORM_MAX_ADDITIONAL_ATTEMPTS - # source: NTF-025 — retries after the first attempt; 0 means one attempt and no retry + # 출처: NTF-025 — 첫 시도 뒤의 재시도 수. 0이면 한 번 시도하고 재시도하지 않는다 type: integer default: 4 allowed_values: null @@ -5126,7 +5072,7 @@ env_keys: required_test: adapter-contract:notification-retry-policy - name: APP_NOTIFICATION_PLATFORM_ESTIMATED_DISPATCH_DURATION - # source: NTF-025 — dispatch latency estimate used by lease/retry planning + # 출처: NTF-025 — lease·재시도 계획에 쓰는 발송 지연 추정값 type: duration default: 2s allowed_values: null @@ -5139,7 +5085,7 @@ env_keys: required_test: adapter-contract:notification-dispatch-bounds - name: APP_NOTIFICATION_PLATFORM_MAX_QUEUE_AGE - # source: NTF-025 — after this, a queued delivery expires rather than being sent late + # 출처: NTF-025 — 이 시간이 지나면 queue의 전달은 늦게 보내지 않고 만료된다 type: duration default: 24h allowed_values: null @@ -5152,7 +5098,7 @@ env_keys: required_test: adapter-contract:notification-expiry - name: APP_NOTIFICATION_PLATFORM_ALLOW_AMBIGUOUS_FALLBACK - # source: NTF-025 — an ambiguous attempt reached the provider with an unread outcome; falling back risks a duplicate send + # 출처: NTF-025 — 결과를 읽지 못한 애매한 시도가 provider에 닿았다. 다른 경로로 넘기면 두 번 보낼 위험이 있다 type: boolean default: false allowed_values: [true, false] @@ -5167,7 +5113,7 @@ env_keys: - name: APP_NOTIFICATION_PLATFORM_SHUTDOWN_GRACE - # source: NTF-025 — upper bound for worker drain during process termination + # 출처: NTF-025 — 프로세스 종료 때 worker 정리 시간의 상한 type: duration default: 20s allowed_values: null @@ -5180,7 +5126,7 @@ env_keys: required_test: adapter-contract:notification-shutdown-grace - name: APP_NOTIFICATION_PLATFORM_MAX_BACKLOG_DEPTH - # source: NTF-OBS-001 — readiness threshold for due and unclaimed deliveries + # 출처: NTF-OBS-001 — 기한이 됐는데 claim되지 않은 전달의 readiness 기준 type: integer default: 100000 allowed_values: null @@ -5193,7 +5139,7 @@ env_keys: required_test: adapter-contract:notification-serving-thresholds - name: APP_NOTIFICATION_PLATFORM_MAX_OLDEST_DUE_AGE - # source: NTF-OBS-001 — readiness threshold for the oldest due delivery + # 출처: NTF-OBS-001 — 기한이 된 가장 오래된 전달의 readiness 기준 type: duration default: 10m allowed_values: null @@ -5206,7 +5152,7 @@ env_keys: required_test: adapter-contract:notification-serving-thresholds - name: APP_NOTIFICATION_PLATFORM_MAX_STUCK_LEASES - # source: NTF-OBS-001 — readiness threshold for expired/stuck delivery leases + # 출처: NTF-OBS-001 — 만료되거나 멈춘 전달 lease의 readiness 기준 type: integer default: 50 allowed_values: null @@ -5219,7 +5165,7 @@ env_keys: required_test: adapter-contract:notification-serving-thresholds - name: APP_NOTIFICATION_PLATFORM_MAX_PENDING_PROJECTIONS - # source: NTF-OBS-001 — readiness threshold for unapplied provider-event projections + # 출처: NTF-OBS-001 — 적용되지 않은 provider 이벤트 projection의 readiness 기준 type: integer default: 50000 allowed_values: null @@ -5232,7 +5178,7 @@ env_keys: required_test: adapter-contract:notification-serving-thresholds - name: APP_NOTIFICATION_PLATFORM_MAX_FAILED_PROJECTIONS - # source: NTF-OBS-001 — readiness threshold for failed provider-event projections + # 출처: NTF-OBS-001 — 실패한 provider 이벤트 projection의 readiness 기준 type: integer default: 1000 allowed_values: null @@ -5245,7 +5191,7 @@ env_keys: required_test: adapter-contract:notification-serving-thresholds - name: APP_NOTIFICATION_PLATFORM_MAX_OLDEST_PENDING_PROJECTION_AGE - # source: NTF-OBS-001 — readiness threshold for the oldest pending projection + # 출처: NTF-OBS-001 — 가장 오래 기다린 projection의 readiness 기준 type: duration default: 15m allowed_values: null @@ -5258,7 +5204,7 @@ env_keys: required_test: adapter-contract:notification-serving-thresholds - name: APP_NOTIFICATION_PLATFORM_MAX_OLDEST_RECONCILIATION_AGE - # source: NTF-OBS-001 — readiness threshold for the oldest unresolved reconciliation + # 출처: NTF-OBS-001 — 가장 오래 풀리지 않은 대조(reconciliation)의 readiness 기준 type: duration default: 30m allowed_values: null @@ -5271,7 +5217,7 @@ env_keys: required_test: adapter-contract:notification-serving-thresholds - name: APP_NOTIFICATION_PLATFORM_CALLBACKS_ENABLED - # source: NTF-025 — whether the platform exposes provider callback endpoints + # 출처: NTF-025 — 플랫폼이 provider callback endpoint를 내놓을지 type: boolean default: false allowed_values: [true, false] @@ -5284,7 +5230,7 @@ env_keys: required_test: adapter-contract:notification-callback-ingestion - name: APP_NOTIFICATION_PLATFORM_CALLBACK_MAX_BODY_BYTES - # source: NTF-025 — ceiling is 65251 = ciphertext column minus the largest envelope (version, key-id length, 255-byte key id, AES-GCM nonce and tag); larger is refused at binding + # 출처: NTF-025 — 상한 65251 = 암호문 칸 크기에서 가장 큰 envelope(version, key-id 길이, 255바이트 key id, AES-GCM nonce와 tag)를 뺀 값. 더 크면 바인딩에서 거부한다 type: integer default: 65251 allowed_values: null @@ -5297,8 +5243,8 @@ env_keys: required_test: adapter-contract:notification-callback-body-bound - name: APP_NOTIFICATION_PLATFORM_CALLBACK_REPLAY_SKEW - # source: NTF-025 — how far a callback timestamp may differ from local time before it is treated as a replay - # review 05-20 — 1h covers SNS's whole HTTP/S retry period (capped at 3,600 s); a replay inside it is a ledger duplicate + # 출처: NTF-025 — callback 시각이 로컬 시각과 이만큼 넘게 다르면 replay로 본다 + # review 05-20 — 1h는 SNS의 HTTP/S 재시도 기간 전체(최대 3,600 s)를 덮는다. 그 안의 replay는 ledger 중복이다 type: duration default: 1h allowed_values: null diff --git a/docs/registries/error-codes.yaml b/docs/registries/error-codes.yaml index 821c32c1..929d5a8b 100644 --- a/docs/registries/error-codes.yaml +++ b/docs/registries/error-codes.yaml @@ -2,24 +2,24 @@ # Schema owner: feature-contract-registry-governance # Category enum owner: feature-operational-error-observability-foundation # Last updated: 2026-11-06 -# Scope: skeleton-wide OperationalError SSOT. Product/fork ApiErrorCode enums own local registries/contracts. +# 범위: 저장소 전체 OperationalError의 정본. 제품·fork의 ApiErrorCode enum은 자기 레지스트리·계약을 가진다. # -# Schema (per row): +# 행마다의 칸: # code: UPPER_SNAKE_CASE # category: VALIDATION | AUTH | AUTHZ | NOT_FOUND | CONFLICT | # RATE_LIMIT | TRANSIENT_DEPENDENCY | PERMANENT_DEPENDENCY | # DATA_INTEGRITY | INTERNAL -# http_status: int (async-only failures use 500 placeholder) +# http_status: int (비동기에서만 나는 실패는 자리표시로 500) # retryable: bool # retry_after_seconds: int | null (RATE_LIMIT/TRANSIENT 권고 backoff) # owner_layer: presentation | application | domain | infrastructure | crosscut # client_safe_message: = shared-contract ClientErrorMessages.of(category) — category별 한국어 문구 표 -# 하나(소유자 결정 11). no token / no principal raw / no internal path / no stack trace -# runbook_link: runbook://area/scenario OR null (client-error만 null 허용) +# 하나(소유자 결정 11). 토큰·principal 원문·내부 경로·stack trace를 담지 않는다 +# runbook_link: runbook://area/scenario 또는 null (client-error만 null 허용) # compatibility_impact: none | additive | behavior-change | breaking -# required_test: owning contract test identifier +# required_test: 이 행을 지키는 계약 테스트 식별자 # -# Runbook policy (operational-runbook-contract L80): +# runbook 규칙 (operational-runbook-contract L80): # retryable=false + category ∈ {AUTH, AUTHZ, RATE_LIMIT, INTERNAL, # TRANSIENT_DEPENDENCY, PERMANENT_DEPENDENCY} ⇒ runbook_link 필수. # VALIDATION/NOT_FOUND/CONFLICT/DATA_INTEGRITY는 client-error로 runbook 면제 가능. @@ -38,7 +38,7 @@ errors: # AUTH (feature-security-operational-baseline / Decision Matrix) # ============================================================ - # source: feature-security-operational-baseline L82 — "token 누락 | 401 | AUTH_TOKEN_MISSING | AUTH" + # 출처: feature-security-operational-baseline L82 — "token 누락 | 401 | AUTH_TOKEN_MISSING | AUTH" - code: AUTH_TOKEN_MISSING category: AUTH http_status: 401 @@ -51,7 +51,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L83 — "token malformed (parse fail) | 401 | AUTH_TOKEN_MALFORMED | AUTH" + # 출처: feature-security-operational-baseline L83 — "token malformed (parse fail) | 401 | AUTH_TOKEN_MALFORMED | AUTH" - code: AUTH_TOKEN_MALFORMED category: AUTH http_status: 401 @@ -64,7 +64,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L84 — "token expired (clock skew tolerance 60s 초과) | 401 | AUTH_TOKEN_EXPIRED | AUTH" + # 출처: feature-security-operational-baseline L84 — "token expired (clock skew tolerance 60s 초과) | 401 | AUTH_TOKEN_EXPIRED | AUTH" - code: AUTH_TOKEN_EXPIRED category: AUTH http_status: 401 @@ -77,7 +77,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L85 — "invalid signature | 401 | AUTH_TOKEN_INVALID_SIGNATURE | AUTH" + # 출처: feature-security-operational-baseline L85 — "invalid signature | 401 | AUTH_TOKEN_INVALID_SIGNATURE | AUTH" - code: AUTH_TOKEN_INVALID_SIGNATURE category: AUTH http_status: 401 @@ -90,7 +90,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L86 — "issuer mismatch | 401 | AUTH_ISSUER_MISMATCH | AUTH" + # 출처: feature-security-operational-baseline L86 — "issuer mismatch | 401 | AUTH_ISSUER_MISMATCH | AUTH" - code: AUTH_ISSUER_MISMATCH category: AUTH http_status: 401 @@ -103,7 +103,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L87 — "audience mismatch | 401 | AUTH_AUDIENCE_MISMATCH | AUTH" + # 출처: feature-security-operational-baseline L87 — "audience mismatch | 401 | AUTH_AUDIENCE_MISMATCH | AUTH" - code: AUTH_AUDIENCE_MISMATCH category: AUTH http_status: 401 @@ -116,7 +116,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L88 — "unknown kid (JWKS 미캐시) | 401 + Retry-After 5s | AUTH_KID_UNKNOWN | AUTH" + # 출처: feature-security-operational-baseline L88 — "unknown kid (JWKS 미캐시) | 401 + Retry-After 5s | AUTH_KID_UNKNOWN | AUTH" - code: AUTH_KID_UNKNOWN category: AUTH http_status: 401 @@ -130,7 +130,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L89 — "JWKS endpoint outage ... | AUTH_JWKS_UNAVAILABLE | TRANSIENT_DEPENDENCY" + # 출처: feature-security-operational-baseline L89 — "JWKS endpoint outage ... | AUTH_JWKS_UNAVAILABLE | TRANSIENT_DEPENDENCY" - code: AUTH_JWKS_UNAVAILABLE category: TRANSIENT_DEPENDENCY http_status: 503 @@ -143,7 +143,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-security-operational-baseline L90 — "claim mapping failure ... | 401 | AUTH_CLAIM_MAPPING_FAILED | AUTH" + # 출처: feature-security-operational-baseline L90 — "claim mapping failure ... | 401 | AUTH_CLAIM_MAPPING_FAILED | AUTH" - code: AUTH_CLAIM_MAPPING_FAILED category: AUTH http_status: 401 @@ -160,7 +160,7 @@ errors: # AUTHZ (feature-security-operational-baseline) # ============================================================ - # source: feature-security-operational-baseline L91 — "valid token + 권한 부족 | 403 | AUTHZ_INSUFFICIENT_PERMISSION | AUTHZ" + # 출처: feature-security-operational-baseline L91 — "valid token + 권한 부족 | 403 | AUTHZ_INSUFFICIENT_PERMISSION | AUTHZ" - code: AUTHZ_INSUFFICIENT_PERMISSION category: AUTHZ http_status: 403 @@ -173,7 +173,7 @@ errors: compatibility_impact: none required_test: contract-verification:authz-category - # source: feature-security-operational-baseline L92 — "valid token + tenant cross-access | 403 | AUTHZ_TENANT_MISMATCH | AUTHZ" + # 출처: feature-security-operational-baseline L92 — "valid token + tenant cross-access | 403 | AUTHZ_TENANT_MISMATCH | AUTHZ" - code: AUTHZ_TENANT_MISMATCH category: AUTHZ http_status: 403 @@ -190,7 +190,7 @@ errors: # INTERNAL (feature-security-operational-baseline + container-runtime) # ============================================================ - # source: feature-security-operational-baseline L93 — "public path misconfiguration ... | 500 + P1 alert | INTERNAL_AUTH_MISCONFIGURATION | INTERNAL" + # 출처: feature-security-operational-baseline L93 — "public path misconfiguration ... | 500 + P1 alert | INTERNAL_AUTH_MISCONFIGURATION | INTERNAL" - code: INTERNAL_AUTH_MISCONFIGURATION category: INTERNAL http_status: 500 @@ -203,7 +203,7 @@ errors: compatibility_impact: none required_test: contract-verification:auth-category - # source: feature-container-runtime-contract L113 — "JVM OutOfMemoryError → ExitOnOutOfMemoryError로 137 exit, log에 error.code=JVM_OOM 명시" + # 출처: feature-container-runtime-contract L113 — "JVM OutOfMemoryError → ExitOnOutOfMemoryError로 137 exit, log에 error.code=JVM_OOM 명시" - code: JVM_OOM category: INTERNAL http_status: 500 @@ -217,10 +217,10 @@ errors: required_test: contract-verification:container-runtime-oom # ============================================================ - # DB / Persistence (feature-persistence-failure-baseline / SQLState Matrix) + # DB / 영속성 (feature-persistence-failure-baseline / SQLState Matrix) # ============================================================ - # source: feature-persistence-failure-baseline L85 — "08* | all | TRANSIENT_DEPENDENCY | DB_UNAVAILABLE | true" + # 출처: feature-persistence-failure-baseline L85 — "08* | all | TRANSIENT_DEPENDENCY | DB_UNAVAILABLE | true" - code: DB_UNAVAILABLE category: TRANSIENT_DEPENDENCY http_status: 503 @@ -233,7 +233,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L86 — "40001 | Postgres/MySQL | CONFLICT | DB_SERIALIZATION_FAILURE | true" + # 출처: feature-persistence-failure-baseline L86 — "40001 | Postgres/MySQL | CONFLICT | DB_SERIALIZATION_FAILURE | true" - code: DB_SERIALIZATION_FAILURE category: CONFLICT http_status: 409 @@ -246,7 +246,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L87 — "40P01 | Postgres | CONFLICT | DB_DEADLOCK | true (backoff)" + # 출처: feature-persistence-failure-baseline L87 — "40P01 | Postgres | CONFLICT | DB_DEADLOCK | true (backoff)" - code: DB_DEADLOCK category: CONFLICT http_status: 409 @@ -259,7 +259,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L88 — "23502 | Postgres | DATA_INTEGRITY | DB_NULL_VIOLATION | false" + # 출처: feature-persistence-failure-baseline L88 — "23502 | Postgres | DATA_INTEGRITY | DB_NULL_VIOLATION | false" - code: DB_NULL_VIOLATION category: DATA_INTEGRITY http_status: 409 @@ -272,7 +272,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L89 — "23503 | Postgres | DATA_INTEGRITY | DB_FK_VIOLATION | false" + # 출처: feature-persistence-failure-baseline L89 — "23503 | Postgres | DATA_INTEGRITY | DB_FK_VIOLATION | false" - code: DB_FK_VIOLATION category: DATA_INTEGRITY http_status: 409 @@ -285,7 +285,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L90 — "23505 | Postgres | CONFLICT | DB_UNIQUE_VIOLATION | false (business mapping)" + # 출처: feature-persistence-failure-baseline L90 — "23505 | Postgres | CONFLICT | DB_UNIQUE_VIOLATION | false (business mapping)" - code: DB_UNIQUE_VIOLATION category: CONFLICT http_status: 409 @@ -298,7 +298,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L91 — "23514 | Postgres | DATA_INTEGRITY | DB_CHECK_VIOLATION | false" + # 출처: feature-persistence-failure-baseline L91 — "23514 | Postgres | DATA_INTEGRITY | DB_CHECK_VIOLATION | false" - code: DB_CHECK_VIOLATION category: DATA_INTEGRITY http_status: 409 @@ -311,7 +311,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L92 — "25P03 | Postgres | TRANSIENT_DEPENDENCY | DB_IDLE_IN_TX_TIMEOUT | true" + # 출처: feature-persistence-failure-baseline L92 — "25P03 | Postgres | TRANSIENT_DEPENDENCY | DB_IDLE_IN_TX_TIMEOUT | true" - code: DB_IDLE_IN_TX_TIMEOUT category: TRANSIENT_DEPENDENCY http_status: 503 @@ -324,7 +324,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: feature-persistence-failure-baseline L93 — "57014 | Postgres | TRANSIENT_DEPENDENCY | DB_QUERY_CANCELED | false" + # 출처: feature-persistence-failure-baseline L93 — "57014 | Postgres | TRANSIENT_DEPENDENCY | DB_QUERY_CANCELED | false" - code: DB_QUERY_CANCELED category: TRANSIENT_DEPENDENCY http_status: 503 @@ -337,7 +337,7 @@ errors: compatibility_impact: none required_test: contract-verification:persistence-mapping - # source: review-followup P15 (S2-lead-4) — JPA OPTIMISTIC_CONFLICT (@Version check failed at flush/commit) + # 출처: review-followup P15 (S2-lead-4) — JPA OPTIMISTIC_CONFLICT (flush·commit 때 @Version 검사 실패) - code: DB_OPTIMISTIC_CONFLICT category: CONFLICT http_status: 409 @@ -350,7 +350,7 @@ errors: compatibility_impact: additive required_test: persistence-jpa:JpaPersistenceExceptionCodeTest - # source: review-followup P15 (S2-lead-4) — JPA COMPLETION_UNKNOWN (40003 / commit-phase connection loss) + # 출처: review-followup P15 (S2-lead-4) — JPA COMPLETION_UNKNOWN (40003 / commit 단계 연결 끊김) - code: DB_COMPLETION_UNKNOWN category: DATA_INTEGRITY http_status: 500 @@ -367,7 +367,7 @@ errors: # Rate limit / Idempotency (feature-rate-limit-idempotency-contract) # ============================================================ - # source: feature-rate-limit-idempotency-contract — rate limit response/log 기준 / Retry-After header 기준 (scope L29, L33) + # 출처: feature-rate-limit-idempotency-contract — rate limit 응답·로그 기준 / Retry-After 헤더 기준 (scope L29, L33) - code: RATE_LIMIT_EXCEEDED category: RATE_LIMIT http_status: 429 @@ -380,7 +380,7 @@ errors: compatibility_impact: none required_test: contract-verification:rate-limit - # source: docs/web/http-contract.md §2 (2026-11-01 소유자 결정, 리뷰 02-01 대안 A) — 결과 불명. 같은 Idempotency-Key로 Retry-After 뒤 재전송. 새 키 금지. + # 출처: docs/web/http-contract.md §2 (2026-11-01 소유자 결정, 리뷰 02-01 대안 A) — 결과 불명. 같은 Idempotency-Key로 Retry-After 뒤 재전송. 새 키 금지. # 2초 = 기본 processing lease(30s)보다 짧은 고정값. 이전 "client는 polling"(retryable=false)은 조회 엔드포인트가 없어 폐기. # 값 하나: IdempotencyExecutor.IN_FLIGHT_RETRY_AFTER. processing-lease가 이 값 이하면 기동 실패(재리뷰 RR-02-05). # behavior-change: retryable false→true는 web Envelope뿐 아니라 gRPC trailer error-retryable(status ABORTED)과 @@ -397,7 +397,7 @@ errors: compatibility_impact: behavior-change required_test: contract-verification:idempotency - # source: feature-rate-limit-idempotency-contract L72 — "fingerprint mismatch (same key + different body) = 422 IDEMPOTENT_REQUEST_MISMATCH" + # 출처: feature-rate-limit-idempotency-contract L72 — "fingerprint mismatch (same key + different body) = 422 IDEMPOTENT_REQUEST_MISMATCH" - code: IDEMPOTENT_REQUEST_MISMATCH category: VALIDATION http_status: 422 @@ -410,7 +410,7 @@ errors: compatibility_impact: none required_test: contract-verification:idempotency - # source: review-followup P15 (X2-P2-2a) — IdempotencyExecutor fail-closed refusal before the action + # 출처: review-followup P15 (X2-P2-2a) — IdempotencyExecutor가 동작 전에 닫힌 채 거절한다(fail-closed) - code: IDEMPOTENCY_UNAVAILABLE category: TRANSIENT_DEPENDENCY http_status: 503 @@ -423,7 +423,7 @@ errors: compatibility_impact: additive required_test: contract-verification:idempotency - # source: 재리뷰 2026-11-03 README 4절 결정, RR-02-03 — action이 돈 뒤 complete 단계에서 저장소가 응답하지 않음. + # 출처: 재리뷰 2026-11-03 README 4절 결정, RR-02-03 — action이 돈 뒤 complete 단계에서 저장소가 응답하지 않음. # 실행 전 거부(IDEMPOTENCY_UNAVAILABLE)와 code로 구분한다. 결과 불명: 같은 키로 재전송하면 서버가 replay·in-flight· # recovery-required로 판정한다. 새 키 금지. docs/web/http-contract.md §2. - code: IDEMPOTENCY_COMPLETION_UNKNOWN @@ -438,7 +438,7 @@ errors: compatibility_impact: additive required_test: contract-verification:idempotency - # source: review-followup P15 (X2-P2-2a) — replay cannot decide whether an external effect happened + # 출처: review-followup P15 (X2-P2-2a) — replay가 외부 효과가 일어났는지 정할 수 없다 - code: IDEMPOTENCY_RECOVERY_REQUIRED category: DATA_INTEGRITY http_status: 500 @@ -452,20 +452,19 @@ errors: required_test: contract-verification:idempotency # ============================================================ - # File / Resource (feature-file-resource-handling-contract) + # 파일 / 자원 (feature-file-resource-handling-contract) # ============================================================ - # source: feature-file-resource-handling-contract L69 — "spring.servlet.multipart.max-file-size 10MB ... Spring 단의 enforcement가 실패 시 envelope 응답 보장" / 테스트 계약 "oversized upload가 generic 500으로 처리되면 실패" + # 출처: feature-file-resource-handling-contract L69 — "spring.servlet.multipart.max-file-size 10MB ... Spring 단의 enforcement가 실패 시 envelope 응답 보장" / 테스트 계약 "oversized upload가 generic 500으로 처리되면 실패" # ============================================================ - # API contract transport-standard codes (feature-api-contract-baseline) + # API 계약의 전송 표준 코드 (feature-api-contract-baseline) # ============================================================ - # NOTE: feature-api-contract-baseline owns the transport-shape failure - # classification (D8 413/414, D9 406/415, D12 405, D15 412). These rows mirror - # dev.caskeleton.shared.error.OperationalError; the D11 status-mapping - # consistency test (owner: this branch, producer) fails the build when a code's - # registry http_status and the enum httpStatus() drift apart. + # 참고: 전송 모양 실패의 분류는 feature-api-contract-baseline이 가진다 + # (D8 413/414, D9 406/415, D12 405, D15 412). 이 행들은 dev.caskeleton.shared.error.OperationalError를 + # 그대로 옮긴 것이다. D11 상태 대응 일관성 테스트(소유: 이 branch, 생산자)가 코드의 레지스트리 http_status와 + # enum httpStatus()가 어긋나면 빌드를 실패시킨다. - # source: feature-api-contract-baseline.md D12 — "405 Method Not Allowed + Allow header 의무" + # 출처: feature-api-contract-baseline.md D12 — "405 Method Not Allowed + Allow header 의무" - code: METHOD_NOT_ALLOWED category: VALIDATION http_status: 405 @@ -478,7 +477,7 @@ errors: compatibility_impact: none required_test: contract-verification:api-contract-status-mapping - # source: feature-api-contract-baseline.md D9 — "406 Not Acceptable = 응답 표현 협상 실패" + # 출처: feature-api-contract-baseline.md D9 — "406 Not Acceptable = 응답 표현 협상 실패" - code: NOT_ACCEPTABLE category: VALIDATION http_status: 406 @@ -491,7 +490,7 @@ errors: compatibility_impact: none required_test: contract-verification:api-contract-status-mapping - # source: feature-api-contract-baseline.md D15 — "If-Match mismatch 시 412 Precondition Failed" + # 출처: feature-api-contract-baseline.md D15 — "If-Match mismatch 시 412 Precondition Failed" - code: PRECONDITION_FAILED category: CONFLICT http_status: 412 @@ -504,7 +503,7 @@ errors: compatibility_impact: none required_test: contract-verification:api-contract-status-mapping - # source: feature-api-contract-baseline.md D8 — "request size limit 실패 분류 (413)" + # 출처: feature-api-contract-baseline.md D8 — "request size limit 실패 분류 (413)" - code: PAYLOAD_TOO_LARGE category: VALIDATION http_status: 413 @@ -517,10 +516,9 @@ errors: compatibility_impact: none required_test: contract-verification:api-contract-status-mapping - # source: feature-api-contract-baseline.md D8 형제 — "URI 길이 실패 분류 (414)" - # NOTE: enforcement is Tomcat/gateway-owned (rejected before Spring dispatch); - # this row + code exist for status-mapping consistency. End-to-end 414 contract - # test is `planned` (gateway/Tomcat maxHttpHeaderSize 8KB boundary). + # 출처: feature-api-contract-baseline.md D8 형제 — "URI 길이 실패 분류 (414)" + # 참고: 강제는 Tomcat·gateway가 한다(Spring dispatch 전에 거절). 이 행과 코드는 상태 대응 일관성을 위해 + # 있다. 끝에서 끝까지의 414 계약 테스트는 `planned`다 (gateway/Tomcat maxHttpHeaderSize 8KB 경계). - code: URI_TOO_LONG category: VALIDATION http_status: 414 @@ -533,7 +531,7 @@ errors: compatibility_impact: none required_test: contract-verification:api-contract-status-mapping - # source: feature-api-contract-baseline.md D9 — "415 Unsupported Media Type = 요청 본문 format 미지원" + # 출처: feature-api-contract-baseline.md D9 — "415 Unsupported Media Type = 요청 본문 format 미지원" - code: UNSUPPORTED_MEDIA_TYPE category: VALIDATION http_status: 415 @@ -550,7 +548,7 @@ errors: # Tenant (feature-tenant-context-policy) # ============================================================ - # source: feature-tenant-context-policy L71 — "tenant 미지원 모드에서 X-Tenant-Id 헤더 수신 시 400 TENANT_NOT_SUPPORTED (filter 단계)" + # 출처: feature-tenant-context-policy L71 — "tenant 미지원 모드에서 X-Tenant-Id 헤더 수신 시 400 TENANT_NOT_SUPPORTED (filter 단계)" # ============================================================ # Validation / Business rule (feature-business-rule-validation-contract) # ============================================================ @@ -560,17 +558,17 @@ errors: # (feature-operational-error-observability-foundation L110). 실제 도메인별 code는 # Phase D(도메인 feature 적용) 시 본 registry에 추가. - # source: feature-operational-error-observability-foundation L110 — "code: VALIDATION_EMAIL_FORMAT, // registry-registered code" (validation field error JSON shape example) + # 출처: feature-operational-error-observability-foundation L110 — "code: VALIDATION_EMAIL_FORMAT, // registry-registered code" (validation 필드 오류 JSON 모양 예) # ============================================================ - # Cache (feature-cache-consistency-contract) + # 캐시 (feature-cache-consistency-contract) # ============================================================ - # source: feature-cache-consistency-contract — Decisionized Work Items "Redis unavailable | degrade only if declared | fail-fast for required cache | generic INTERNAL | unavailable mapping" / 테스트 "Redis unavailable이 degrade 가능 여부 없이 INTERNAL로 처리되면 실패" + # 출처: feature-cache-consistency-contract — Decisionized Work Items "Redis unavailable | degrade only if declared | fail-fast for required cache | generic INTERNAL | unavailable mapping" / 테스트 "Redis unavailable이 degrade 가능 여부 없이 INTERNAL로 처리되면 실패" # ============================================================ - # Outbound HTTP (feature-outbound-http-client-baseline) + # 외부 HTTP 호출 (feature-outbound-http-client-baseline) # ============================================================ - # source: feature-outbound-http-client-baseline L70 — "outbound HTTP timeout default = connect 2s / read 5s / global call 10s" + scope "timeout/connect/DNS failure 분류" / 테스트 "upstream timeout은 retryable dependency failure로 분류되어야 함" + # 출처: feature-outbound-http-client-baseline L70 — "outbound HTTP timeout default = connect 2s / read 5s / global call 10s" + scope "timeout/connect/DNS failure 분류" / 테스트 "upstream timeout은 retryable dependency failure로 분류되어야 함" - code: DEPENDENCY_TIMEOUT category: TRANSIENT_DEPENDENCY http_status: 504 @@ -583,7 +581,7 @@ errors: compatibility_impact: none required_test: contract-verification:outbound-http - # source: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류" + L70 connect=2s timeout + # 출처: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류" + L70 connect=2s timeout - code: DEPENDENCY_CONNECT_FAILED category: TRANSIENT_DEPENDENCY http_status: 503 @@ -596,7 +594,7 @@ errors: compatibility_impact: none required_test: contract-verification:outbound-http - # source: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류" + # 출처: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류" - code: DEPENDENCY_DNS_FAILED category: TRANSIENT_DEPENDENCY http_status: 503 @@ -609,7 +607,7 @@ errors: compatibility_impact: none required_test: contract-verification:outbound-http - # source: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류" / 테스트 "401/403은 credential/scope/config 문제로 분류되어야 함" + # 출처: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류" / 테스트 "401/403은 credential/scope/config 문제로 분류되어야 함" - code: DEPENDENCY_4XX_CLIENT category: PERMANENT_DEPENDENCY http_status: 502 @@ -622,7 +620,7 @@ errors: compatibility_impact: none required_test: contract-verification:outbound-http - # source: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류" + # 출처: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류" - code: DEPENDENCY_5XX_SERVER category: TRANSIENT_DEPENDENCY http_status: 502 @@ -635,7 +633,7 @@ errors: compatibility_impact: none required_test: contract-verification:outbound-http - # source: feature-outbound-http-client-baseline L69 — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용" + Decisionized "circuit breaker | Resilience4j optional env" + # 출처: feature-outbound-http-client-baseline L69 — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용" + Decisionized "circuit breaker | Resilience4j optional env" - code: DEPENDENCY_CIRCUIT_OPEN category: TRANSIENT_DEPENDENCY http_status: 503 @@ -652,7 +650,7 @@ errors: # Outbox (feature-domain-event-outbox-contract) # ============================================================ - # source: feature-domain-event-outbox-contract L67 — "outbox row status enum = PENDING / IN_FLIGHT / PUBLISHED / FAILED / DEAD" + scope "publish 실패 분류" / 판정 "publish 실패가 retry/DLQ/log/runbook 기준 없이 삼켜지면 실패" + # 출처: feature-domain-event-outbox-contract L67 — "outbox row status enum = PENDING / IN_FLIGHT / PUBLISHED / FAILED / DEAD" + scope "publish 실패 분류" / 판정 "publish 실패가 retry/DLQ/log/runbook 기준 없이 삼켜지면 실패" - code: OUTBOX_PUBLISH_FAILED category: TRANSIENT_DEPENDENCY http_status: 500 @@ -665,7 +663,7 @@ errors: compatibility_impact: none required_test: contract-verification:outbox-publish - # source: feature-domain-event-outbox-contract L67 — outbox status enum "DEAD" / Outbox Defaults "DLQ | background-job branch owner" + # 출처: feature-domain-event-outbox-contract L67 — outbox status enum "DEAD" / Outbox Defaults "DLQ | background-job branch owner" - code: OUTBOX_DEAD_LETTER category: INTERNAL http_status: 500 @@ -679,10 +677,10 @@ errors: required_test: contract-verification:outbox-dlq # ============================================================ - # Background job / Async (feature-background-job-async-contract) + # 백그라운드 작업 / 비동기 (feature-background-job-async-contract) # ============================================================ - # source: feature-background-job-async-contract — Decisionized "saturation | bounded executor + rejection log" / L72 "saturation policy default = AbortPolicy" / 테스트 "executor rejection이 structured log 없이 발생하면 실패" + # 출처: feature-background-job-async-contract — Decisionized "saturation | bounded executor + rejection log" / L72 "saturation policy default = AbortPolicy" / 테스트 "executor rejection이 structured log 없이 발생하면 실패" - code: JOB_EXECUTOR_REJECTED category: TRANSIENT_DEPENDENCY http_status: 503 @@ -695,7 +693,7 @@ errors: compatibility_impact: none required_test: contract-verification:async-saturation - # source: feature-background-job-async-contract L69 — "기본 backoff는 exponential backoff with jitter, max attempts 3, DLQ after exhausted attempts" + scope "shutdown 중 job 처리 기준" / L73 graceful shutdown ≤19s + # 출처: feature-background-job-async-contract L69 — "기본 backoff는 exponential backoff with jitter, max attempts 3, DLQ after exhausted attempts" + scope "shutdown 중 job 처리 기준" / L73 graceful shutdown ≤19s - code: JOB_TIMEOUT category: TRANSIENT_DEPENDENCY http_status: 500 @@ -708,7 +706,7 @@ errors: compatibility_impact: none required_test: contract-verification:async-timeout - # source: feature-background-job-async-contract L69 — "DLQ after exhausted attempts" + Decisionized "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted | ... | infinite retry" + # 출처: feature-background-job-async-contract L69 — "DLQ after exhausted attempts" + Decisionized "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted | ... | infinite retry" - code: JOB_DEAD_LETTER category: INTERNAL http_status: 500 @@ -722,10 +720,10 @@ errors: required_test: contract-verification:async-dlq # ============================================================ - # Distributed Lock (feature-distributed-lock-contract) + # 분산 lock (feature-distributed-lock-contract) # ============================================================ - # source: feature-distributed-lock-contract D7 — "lock 획득 실패/timeout 의 error code = + # 출처: feature-distributed-lock-contract D7 — "lock 획득 실패/timeout 의 error code = # LOCK_ACQUISITION_TIMEOUT (category CONFLICT, retryable true, client_safe true) + metric # lock.acquisition" / D5 — "try-lock + 유한 waitTime + lease(TTL) 필수, 무한 blocking 금지". # category CONFLICT 는 기존 enum 재사용; retryable=true — 락 보유자가 임계 구역을 빠져나오면 @@ -746,10 +744,10 @@ errors: required_test: contract-verification:lock-acquisition-timeout # ============================================================ - # Migration / Startup (feature-migration-startup-contract) + # Migration / 기동 (feature-migration-startup-contract) # ============================================================ - # source: feature-migration-startup-contract L71 — "startup exit code 표준 = ... migration 실패=70 ..." + Decisionized "startup failure log | structured log with startup.phase, error.code, error.category" + # 출처: feature-migration-startup-contract L71 — "startup exit code 표준 = ... migration 실패=70 ..." + Decisionized "startup failure log | structured log with startup.phase, error.code, error.category" - code: ADAPTER_DISABLED category: INTERNAL http_status: 500 @@ -762,12 +760,12 @@ errors: compatibility_impact: none required_test: adapter-contract:adapter-disabled-runtime-call - # source: feature-migration-startup-contract L71 — "startup exit code 표준 = ... profile mismatch=71" / 테스트 "prod profile에서 local-only 설정이 켜지면 실패" + # 출처: feature-migration-startup-contract L71 — "startup exit code 표준 = ... profile mismatch=71" / 테스트 "prod profile에서 local-only 설정이 켜지면 실패" # ============================================================ - # Management / Actuator (feature-management-actuator-security-contract) + # 관리 포트 / Actuator (feature-management-actuator-security-contract) # ============================================================ - # source: feature-management-actuator-security-contract — Exposure Policy "env/configprops | forbidden" "heapdump/threaddump | forbidden unless break-glass runbook" "shutdown | forbidden" / 테스트 "prod에서 env/configprops endpoint가 노출되면 실패" + # 출처: feature-management-actuator-security-contract — 노출 정책 "env/configprops | forbidden" "heapdump/threaddump | forbidden unless break-glass runbook" "shutdown | forbidden" / 테스트 "prod에서 env/configprops endpoint가 노출되면 실패" - code: ACTUATOR_FORBIDDEN category: AUTHZ http_status: 403 @@ -781,9 +779,9 @@ errors: required_test: contract-verification:management-actuator # ============================================================ - # CURRENT CODE RECONCILIATION (2026-09-21) - # Skeleton-wide OperationalError entries that were live in code but absent from the Phase-B - # registry. Product-specific ApiErrorCode enums remain owned by their product modules. + # 지금 코드와 맞춤 (2026-09-21) + # 코드에는 있었지만 Phase-B 레지스트리에 없던 저장소 전체 OperationalError 항목. 제품별 ApiErrorCode enum은 + # 자기 제품 모듈이 가진다. # ============================================================ - code: VALIDATION_FAILED diff --git a/docs/registries/headers.yaml b/docs/registries/headers.yaml index e8c8a3fe..21168e03 100644 --- a/docs/registries/headers.yaml +++ b/docs/registries/headers.yaml @@ -2,14 +2,14 @@ # Schema owner: feature-contract-registry-governance # Last updated: 2026-05-22 # -# Conventions: -# - HTTP header name: kebab-case (X-Request-Id, X-Correlation-Id) -# - W3C standard headers: lowercase (traceparent, tracestate) -# - mdc_key: snake_case (foundation SSOT) -# - envelope_meta_field: camelCase (envelope SSOT) +# 표기 규칙 +# - HTTP 헤더 이름: kebab-case (X-Request-Id, X-Correlation-Id) +# - W3C 표준 헤더: 소문자 (traceparent, tracestate) +# - mdc_key: snake_case (foundation이 정본) +# - envelope_meta_field: camelCase (envelope이 정본) headers: - # source: feature-operational-error-observability-foundation.md L97 + # 출처: feature-operational-error-observability-foundation.md L97 # "request_id | inbound filter (생성 또는 X-Request-Id 헤더) | response header X-Request-Id" - name: X-Request-Id direction: both @@ -23,7 +23,7 @@ headers: compatibility_impact: none required_test: contract-verification:envelope-headers - # source: feature-api-contract-baseline.md L77 / feature-rate-limit-idempotency-contract.md L66-67 + # 출처: feature-api-contract-baseline.md L77 / feature-rate-limit-idempotency-contract.md L66-67 # "idempotency header 이름은 Idempotency-Key" / "기본 scope는 (authenticatedPrincipal, idempotencyKey, useCaseName)" - name: Idempotency-Key direction: inbound @@ -37,7 +37,7 @@ headers: compatibility_impact: additive required_test: contract-verification:idempotency-replay - # source: feature-rate-limit-idempotency-contract.md L85 / foundation L85 + # 출처: feature-rate-limit-idempotency-contract.md L85 / foundation L85 # "RATE_LIMIT | ... | 429 | true (Retry-After 이후)" / "retry-after 기준 없이 429를 반환하면 실패" - name: Retry-After direction: outbound @@ -51,7 +51,7 @@ headers: compatibility_impact: additive required_test: contract-verification:rate-limit-headers - # source: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준) + # 출처: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준) # app.rate-limit.enabled=true인 요청 경로에서만 생성되는 rate-limit 응답 표면 - name: X-RateLimit-Limit direction: outbound @@ -65,7 +65,7 @@ headers: compatibility_impact: additive required_test: contract-verification:rate-limit-headers - # source: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준) + # 출처: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준) - name: X-RateLimit-Remaining direction: outbound type: numeric @@ -78,7 +78,7 @@ headers: compatibility_impact: additive required_test: contract-verification:rate-limit-headers - # source: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준) + # 출처: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준) - name: X-RateLimit-Reset direction: outbound type: rfc3339-date @@ -91,7 +91,7 @@ headers: compatibility_impact: additive required_test: contract-verification:rate-limit-headers - # source: feature-api-compatibility-deprecation-contract.md L87 + # 출처: feature-api-compatibility-deprecation-contract.md L87 # "deprecation marker | OpenAPI deprecated: true + design record | response header optional" - name: Deprecation direction: outbound @@ -105,7 +105,7 @@ headers: compatibility_impact: additive required_test: contract-verification:deprecation-marker - # source: feature-api-compatibility-deprecation-contract.md L87 + # 출처: feature-api-compatibility-deprecation-contract.md L87 # "deprecation marker | OpenAPI deprecated: true + design record | response header optional" (RFC 8594 Sunset) - name: Sunset direction: outbound @@ -119,7 +119,7 @@ headers: compatibility_impact: additive required_test: contract-verification:deprecation-marker - # source: feature-distributed-tracing-contract.md L64, L85 + # 출처: feature-distributed-tracing-contract.md L64, L85 # "propagation header는 W3C traceparent default" / "HTTP | traceparent, tracestate (W3C)" - name: traceparent direction: both @@ -133,7 +133,7 @@ headers: compatibility_impact: none required_test: contract-verification:trace-propagation - # source: feature-distributed-tracing-contract.md L66, L85 + # 출처: feature-distributed-tracing-contract.md L66, L85 # "propagation format = W3C traceparent + tracestate only. B3 propagation은 forbidden" - name: tracestate direction: both @@ -147,7 +147,7 @@ headers: compatibility_impact: none required_test: contract-verification:trace-propagation - # source: feature-operational-error-observability-foundation.md L100 + # 출처: feature-operational-error-observability-foundation.md L100 # "correlation_id | inbound header X-Correlation-Id 또는 생성 | HTTP X-Correlation-Id, message header correlation_id" - name: X-Correlation-Id direction: both @@ -161,8 +161,8 @@ headers: compatibility_impact: none required_test: contract-verification:envelope-headers - # source: feature-security-operational-baseline.md L66 - # "JWT Resource Server를 baseline security model로 둠" (Bearer token via Authorization header) + # 출처: feature-security-operational-baseline.md L66 + # "JWT Resource Server를 baseline security model로 둠" (Authorization 헤더의 Bearer 토큰) - name: Authorization direction: inbound type: bearer-token @@ -175,8 +175,8 @@ headers: compatibility_impact: none required_test: contract-verification:jwt-resource-server - # source: feature-security-operational-baseline.md L83-90 (AuthN/AuthZ Decision Matrix) - # 401 응답 시 WWW-Authenticate (Bearer realm/error) — Spring Security JWT Resource Server 표준 challenge header + # 출처: feature-security-operational-baseline.md L83-90 (AuthN/AuthZ 판정 표) + # 401 응답 시 WWW-Authenticate (Bearer realm/error) — Spring Security JWT Resource Server의 표준 challenge 헤더 - name: WWW-Authenticate direction: outbound type: string diff --git a/docs/registries/mdc-keys.yaml b/docs/registries/mdc-keys.yaml index 3d041296..e3944d49 100644 --- a/docs/registries/mdc-keys.yaml +++ b/docs/registries/mdc-keys.yaml @@ -3,13 +3,13 @@ # MDC SSOT: feature-operational-error-observability-foundation # Last updated: 2026-05-22 # -# Conventions: -# - MDC key naming: snake_case (foundation L93 "snake_case 강제. camelCase / dot.case 금지.") +# 표기 규칙 +# - MDC key 이름: snake_case (foundation L93 "snake_case 강제. camelCase / dot.case 금지.") # - cardinality_safe_for_metric=true 인 key만 metric tag로 사용 가능 -# - foundation L93-102 표 "MDC Key Standard (final)" 6개가 core SSOT +# - foundation L93-102 표 "MDC Key Standard (final)"의 key들이 핵심 정본이다 mdc_keys: - # source: feature-operational-error-observability-foundation.md L97 + # 출처: feature-operational-error-observability-foundation.md L97 # "request_id | inbound filter (생성 또는 X-Request-Id 헤더) | response header X-Request-Id" - key: request_id type: ulid @@ -24,7 +24,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-mdc-keys - # source: feature-operational-error-observability-foundation.md L98 + # 출처: feature-operational-error-observability-foundation.md L98 # "trace_id | Micrometer Tracing | W3C traceparent header" - key: trace_id type: string @@ -39,7 +39,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-mdc-keys - # source: feature-operational-error-observability-foundation.md L99 + # 출처: feature-operational-error-observability-foundation.md L99 # "span_id | Micrometer Tracing | W3C traceparent" # NOTE: background-job-async-contract L71 "span_id는 Micrometer Observation context에서 자동 전파(MDC explicit copy 불필요)" - key: span_id @@ -55,7 +55,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-mdc-keys - # source: feature-operational-error-observability-foundation.md L100 + # 출처: feature-operational-error-observability-foundation.md L100 # "correlation_id | inbound header X-Correlation-Id 또는 생성 | HTTP X-Correlation-Id, message header correlation_id" - key: correlation_id type: ulid @@ -70,7 +70,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-mdc-keys - # source: feature-operational-error-observability-foundation.md L101 + feature-tenant-context-policy.md L70 + # 출처: feature-operational-error-observability-foundation.md L101 + feature-tenant-context-policy.md L70 # "tenant_id | tenant context (활성 시) | downstream HTTP X-Tenant-Id (with allowlist)" / # "tenant ID format = opaque ULID (26 chars Crockford base32)" # NOTE: tenant L73 "tenant_id ULID 원본은 metric tag에 직접 사용 금지" @@ -87,7 +87,7 @@ mdc_keys: compatibility_impact: additive required_test: contract-verification:tenant-leakage - # source: feature-operational-error-observability-foundation.md L102 + # 출처: feature-operational-error-observability-foundation.md L102 # "user_principal | security context (pseudonymized only) | log only, headers forbidden" - key: user_principal type: string @@ -102,10 +102,10 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-mdc-keys - # ── log type extensions (log-management-contract L101-109 "Log Type별 필수 필드") ── + # ── 로그 종류별 확장 (log-management-contract L101-109 "Log Type별 필수 필드") ── - # source: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms" - # NOTE: application-port-usecase-contract / business 측 operation 식별자 (uri_template과 별도 application-set) + # 출처: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms" + # 참고: application-port-usecase-contract / 업무 쪽 operation 식별자 (uri_template과 따로 application이 정한다) - key: operation type: string source: application_set @@ -119,7 +119,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms" + # 출처: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms" - key: method type: string source: inbound_filter @@ -133,8 +133,8 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms" - # NOTE: metrics L86 "status_code | 7 (1xx-5xx + ok/other)" — bounded + # 출처: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms" + # 참고: metrics L86 "status_code | 7 (1xx-5xx + ok/other)" — 값 개수가 정해져 있다 - key: status type: numeric source: inbound_filter @@ -148,7 +148,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L105-106 "request | ... duration_ms" / "dependency | ... duration_ms" + # 출처: feature-log-management-contract.md L105-106 "request | ... duration_ms" / "dependency | ... duration_ms" - key: duration_ms type: numeric source: application_set @@ -162,8 +162,8 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L106 "dependency | dependency_name, dependency_type, duration_ms, outcome, error_code" - # NOTE: metrics L88 "dependency_name | 50" — bounded + # 출처: feature-log-management-contract.md L106 "dependency | dependency_name, dependency_type, duration_ms, outcome, error_code" + # 참고: metrics L88 "dependency_name | 50" — 값 개수가 정해져 있다 - key: dependency_name type: string source: application_set @@ -177,7 +177,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L106 "dependency | dependency_name, dependency_type, ..." + # 출처: feature-log-management-contract.md L106 "dependency | dependency_name, dependency_type, ..." - key: dependency_type type: string source: application_set @@ -191,7 +191,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L106 + metrics L91 "outcome (resilience4j) | 5 (SUCCESS/FAILURE/CIRCUIT_OPEN/TIMEOUT/REJECTED)" + # 출처: feature-log-management-contract.md L106 + metrics L91 "outcome (resilience4j) | 5 (SUCCESS/FAILURE/CIRCUIT_OPEN/TIMEOUT/REJECTED)" - key: outcome type: string source: application_set @@ -205,8 +205,8 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L106 "dependency | ... error_code (실패 시)" - # NOTE: metrics L89 "error_code | 100 — error registry row 상한과 정합" — bounded + # 출처: feature-log-management-contract.md L106 "dependency | ... error_code (실패 시)" + # 참고: metrics L89 "error_code | 100 — error registry row 상한과 정합" — 값 개수가 정해져 있다 - key: error_code type: string source: application_set @@ -220,7 +220,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L107 + # 출처: feature-log-management-contract.md L107 # "security | event_type, user_principal (pseudonymized), source_ip (anonymized — last octet zeroed)" - key: event_type type: string @@ -235,7 +235,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L107 "security | ... source_ip (anonymized — last octet zeroed)" + # 출처: feature-log-management-contract.md L107 "security | ... source_ip (anonymized — last octet zeroed)" # NOTE: metrics L93 "high-cardinality 금지 tag: ... ip_address" - key: source_ip_anon type: string @@ -250,7 +250,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L108 "audit | actor, action, target, before_hash, after_hash, occurred_at" + # 출처: feature-log-management-contract.md L108 "audit | actor, action, target, before_hash, after_hash, occurred_at" - key: actor type: string source: security_context @@ -264,7 +264,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L108 "audit | actor, action, target, ..." + # 출처: feature-log-management-contract.md L108 "audit | actor, action, target, ..." - key: action type: string source: application_set @@ -278,7 +278,7 @@ mdc_keys: compatibility_impact: none required_test: contract-verification:log-fields - # source: feature-log-management-contract.md L108 "audit | actor, action, target, ..." + # 출처: feature-log-management-contract.md L108 "audit | actor, action, target, ..." - key: target type: string source: application_set diff --git a/docs/registries/metrics.yaml b/docs/registries/metrics.yaml index a3ba89d8..8f7a6164 100644 --- a/docs/registries/metrics.yaml +++ b/docs/registries/metrics.yaml @@ -3,18 +3,20 @@ # Owner branch: feature-metrics-alerting-contract # Last updated: 2026-05-22 # -# Notes -# - Naming: Micrometer dot.case + unit suffix (.seconds | .bytes | .total). -# - Tag cardinality bounds are SSOT of feature-metrics-alerting-contract "Cardinality Bounds" table. -# - High-cardinality tags forbidden globally: user_id, request_id, raw_url, raw_query, -# raw_header_value, ip_address. These MUST NOT appear in any row. -# - tenant_id label is bounded mapping table id OR cohort bucket only (ULID raw forbidden). -# - error_code tag cardinality_limit follows error-codes.yaml row count (max 100). +# 읽는 법 +# - 이름: Micrometer dot.case에 단위 접미사(.seconds | .bytes | .total)를 붙인다. +# - tag 값 개수(cardinality) 상한의 정본은 feature-metrics-alerting-contract의 "Cardinality Bounds" 표다. +# - 값 개수가 많은 tag는 어디서도 쓰지 않는다: user_id, request_id, raw_url, raw_query, +# raw_header_value, ip_address. 어떤 행에도 나오면 안 된다. +# - tenant_id label은 크기가 정해진 매핑 표의 id나 cohort bucket만 쓴다(ULID 원문 금지). +# - error_code tag의 cardinality_limit은 error-codes.yaml 행 수를 따른다(최대 100). +# - alert_severity_thresholds 값은 경보 조건을 사람이 읽는 글로 적은 것이다. 지표 이름·연산자· +# 기간(5m, 1h)은 원문 그대로 두고, 테스트는 키(p1·p2·p3)와 값이 비어 있지 않은지만 본다. metrics: - # === HTTP server (inbound) === - # source: feature-metrics-alerting-contract — Metric/Alert Defaults + # === HTTP 서버 (inbound) === + # 출처: feature-metrics-alerting-contract — Metric/Alert Defaults # "HTTP metric | http.server.requests with method/status/uri-template | raw URL or user id tag" - name: http.server.requests type: timer @@ -32,15 +34,15 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p1: "error_rate > 5% for 5m OR > 10% for 1m" - p2: "error_rate > 1% for 10m" - p3: "error_rate > 0.1% for 1h" + p1: "error_rate > 5%가 5m 동안, 또는 > 10%가 1m 동안" + p2: "error_rate > 1%가 10m 동안" + p3: "error_rate > 0.1%가 1h 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [method, status, uri_template] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-metrics-alerting-contract — P1/P2/P3 정량 기준 (HTTP latency p99) + # 출처: feature-metrics-alerting-contract — P1/P2/P3 정량 기준 (HTTP latency p99) # "P1: p99 > 5s 5분 / P2: p99 > 1s 10분 / P3: p99 > 500ms 30분" - name: http.server.requests.latency type: timer @@ -55,18 +57,18 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p1: "p99 > 5s for 5m" - p2: "p99 > 1s for 10m" - p3: "p99 > 500ms for 30m" + p1: "p99 > 5s가 5m 동안" + p2: "p99 > 1s가 10m 동안" + p3: "p99 > 500ms가 30m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [method, uri_template, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === HTTP client (outbound dependency) === - # source: feature-metrics-alerting-contract — Metric/Alert Defaults + # === HTTP client (outbound 의존 대상) === + # 출처: feature-metrics-alerting-contract — Metric/Alert Defaults # "dependency metric | dependency.client.requests with dependency.name/type/outcome | endpoint with secret tag" - # source: feature-outbound-http-client-baseline — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용" + # 출처: feature-outbound-http-client-baseline — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용" - name: dependency.client.requests type: timer unit: seconds @@ -82,17 +84,17 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p1: "required dep unavailable for 2m" - p2: "optional dep degraded for 5m" - p3: "spike alert (10x baseline)" + p1: "필수 의존 대상이 2m 동안 응답하지 않음" + p2: "선택 의존 대상이 5m 동안 저하됨" + p3: "급증 경보(기준선의 10배)" owner_branch: feature-metrics-alerting-contract log_field_mapping: [dependency_name, dependency_type, outcome, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-outbound-http-client-baseline — decisions - # "retry/circuit breaker 기본 라이브러리는 Resilience4j" - # source: feature-metrics-alerting-contract — "retry/CB minimum: resilience4j.retry.calls{outcome}" + # 출처: feature-outbound-http-client-baseline — 결정 + # "retry/circuit breaker 기본 라이브러리는 Resilience4j" + # 출처: feature-metrics-alerting-contract — "retry/CB minimum: resilience4j.retry.calls{outcome}" - name: resilience4j.retry.calls type: counter unit: total @@ -105,13 +107,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "retry exhaustion rate > 1% for 10m" + p2: "재시도 소진 비율 > 1%가 10m 동안" owner_branch: feature-outbound-http-client-baseline log_field_mapping: [dependency_name, outcome, retry_attempt] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.state" + # 출처: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.state" - name: resilience4j.circuitbreaker.state type: gauge unit: total @@ -124,14 +126,14 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p1: "state == OPEN for required dependency for 2m" - p2: "state == OPEN for optional dependency for 5m" + p1: "필수 의존 대상의 state == OPEN이 2m 동안" + p2: "선택 의존 대상의 state == OPEN이 5m 동안" owner_branch: feature-outbound-http-client-baseline log_field_mapping: [dependency_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.calls{outcome}" + # 출처: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.calls{outcome}" - name: resilience4j.circuitbreaker.calls type: timer unit: seconds @@ -144,16 +146,16 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p2: "CIRCUIT_OPEN rate > 1% for 10m" + p2: "CIRCUIT_OPEN 비율 > 1%가 10m 동안" owner_branch: feature-outbound-http-client-baseline log_field_mapping: [dependency_name, outcome, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === DB connection pool === - # source: feature-persistence-failure-baseline — Hikari Alert Threshold + # 출처: feature-persistence-failure-baseline — Hikari Alert Threshold # "pool wait p99 > 100ms 5분 지속 → P2 / pool exhaustion (active = max) > 1분 → P1" - # source: feature-metrics-alerting-contract — "hikaricp.connections.acquire{outcome='timeout'} p99 > 100ms" + # 출처: feature-metrics-alerting-contract — "hikaricp.connections.acquire{outcome='timeout'} p99 > 100ms" - name: hikaricp.connections.acquire type: timer unit: seconds @@ -166,14 +168,14 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p1: "pool exhaustion (active == max) for 1m" - p2: "acquire p99 > 100ms for 5m" + p1: "pool 고갈(active == max)이 1m 동안" + p2: "acquire p99 > 100ms가 5m 동안" owner_branch: feature-persistence-failure-baseline log_field_mapping: [pool, outcome] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-persistence-failure-baseline — In scope "Hikari metric 노출 기준" + Hikari Alert Threshold + # 출처: feature-persistence-failure-baseline — 범위 안 "Hikari metric 노출 기준" + Hikari Alert Threshold - name: hikaricp.connections.usage type: timer unit: seconds @@ -183,13 +185,13 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p2: "usage p99 elevated > 10m" + p2: "usage p99가 10m 넘게 높음" owner_branch: feature-persistence-failure-baseline log_field_mapping: [pool] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-persistence-failure-baseline — In scope "Hikari metric 노출 기준" + # 출처: feature-persistence-failure-baseline — 범위 안 "Hikari metric 노출 기준" - name: hikaricp.connections.active type: gauge unit: total @@ -199,13 +201,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p1: "active == max for 1m" + p1: "active == max가 1m 동안" owner_branch: feature-persistence-failure-baseline log_field_mapping: [pool] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-metrics-alerting-contract — Histogram Buckets/Percentile "DB query: same" + # 출처: feature-metrics-alerting-contract — Histogram Buckets/Percentile "DB query: same" - name: db.query.duration type: timer unit: seconds @@ -219,14 +221,14 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p2: "p99 > 1s for 10m" + p2: "p99 > 1s가 10m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [operation, outcome, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === Background job / async executor === - # source: feature-background-job-async-contract — Decisionized Work Items "saturation policy" + # === 백그라운드 작업 / 비동기 executor === + # 출처: feature-background-job-async-contract — Decisionized Work Items "saturation policy" # "AbortPolicy default (core=10, max=50, queue=200)" - name: executor.saturation type: gauge @@ -237,14 +239,14 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "queue size > 80% capacity for 5m" - p1: "rejection rate > 0 for 1m" + p2: "queue 크기 > 용량의 80%가 5m 동안" + p1: "거절 비율 > 0이 1m 동안" owner_branch: feature-background-job-async-contract log_field_mapping: [executor_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-background-job-async-contract — Decisionized Work Items "saturation | bounded executor + rejection log" + # 출처: feature-background-job-async-contract — 결정한 작업 항목 "saturation | bounded executor + rejection log" - name: executor.rejected.total type: counter unit: total @@ -257,13 +259,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p1: "rejection_count > 0 for 1m" + p1: "rejection_count > 0이 1m 동안" owner_branch: feature-background-job-async-contract log_field_mapping: [executor_name, policy] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-background-job-async-contract — Decisionized Work Items "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted" + # 출처: feature-background-job-async-contract — 결정한 작업 항목 "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted" - name: job.retry.total type: counter unit: total @@ -276,13 +278,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "EXHAUSTED rate > 1% for 10m" + p2: "EXHAUSTED 비율 > 1%가 10m 동안" owner_branch: feature-background-job-async-contract log_field_mapping: [job_name, outcome, retry_attempt] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-background-job-async-contract — "DLQ after exhausted attempts" + # 출처: feature-background-job-async-contract — "DLQ after exhausted attempts" - name: job.dlq.total type: counter unit: total @@ -292,14 +294,14 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p1: "DLQ rate sustained > 0 for 5m" + p1: "DLQ 비율 > 0이 5m 동안 계속" owner_branch: feature-background-job-async-contract log_field_mapping: [job_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === Distributed lock === - # source: feature-distributed-lock-contract D7 — "metric lock.acquisition (tag: outcome = + # 출처: feature-distributed-lock-contract D7 — "metric lock.acquisition (tag: outcome = # acquired/timeout/error) — 신규 제안" / D5 — try-lock + 유한 waitTime + lease(TTL). 분산 # 상호배제(distributedLockProvider) 획득 시도 결과를 센다. key 는 tag 로 넣지 않는다 # (무한 cardinality — 위 전역 금지 규칙). timeout outcome 은 LOCK_ACQUISITION_TIMEOUT 발생과 1:1. @@ -313,18 +315,17 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "timeout rate > 5% for 10m" + p2: "timeout 비율 > 5%가 10m 동안" owner_branch: feature-distributed-lock-contract log_field_mapping: [outcome] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-distributed-lock-contract §Edge / D5 (SI-LOCK-C5) — "lease 만료 후 unlock → - # ConcurrentModificationException — 삼킴 금지, 로그+metric 후 정상 흐름 복귀". Counts releases that - # found the lease already expired (the JdbcLock row was reclaimed by another instance before - # the holder called close()). A sustained nonzero rate means lease TTL is shorter than real - # critical-section duration — raise APP/lease TTL or shorten the protected work. Not an - # acquisition outcome, hence a separate counter from lock.acquisition. + # 출처: feature-distributed-lock-contract §Edge / D5 (SI-LOCK-C5) — "lease 만료 후 unlock → + # ConcurrentModificationException — 삼킴 금지, 로그+metric 후 정상 흐름 복귀". lease가 이미 만료된 뒤의 + # 해제를 센다(보유자가 close()를 부르기 전에 다른 인스턴스가 JdbcLock 행을 회수함). 0이 아닌 비율이 + # 이어지면 lease TTL이 실제 임계 구역 시간보다 짧다는 뜻이다 — APP/lease TTL을 늘리거나 보호하는 일을 + # 줄인다. 획득 결과가 아니라서 lock.acquisition과 다른 counter다. - name: lock.lease.expired type: counter unit: total @@ -332,14 +333,14 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "lease-expired rate sustained > 0 for 10m" + p2: "lease-expired 비율 > 0이 10m 동안 계속" owner_branch: feature-distributed-lock-contract log_field_mapping: [] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === Outbox publisher === - # source: feature-domain-event-outbox-contract — Outbox Defaults + # === Outbox 발행기 === + # 출처: feature-domain-event-outbox-contract — Outbox Defaults # "DB outbox table with eventId, aggregateId, eventType, payload, occurredAt, status, attemptCount, nextAttemptAt" - name: outbox.publisher.published.total type: counter @@ -349,20 +350,20 @@ metrics: cardinality_limit: 50 - name: outcome cardinality_limit: 5 - # The relay cycle outcomes (OutboxRelayResult.Outcome), not row statuses: IN_FLIGHT is a status - # and is never counted. STALE: the relay's claim was taken over before its result could be - # written (V17 lease fence). RELEASED: a stopping relay gave back a claim it had not used. + # 행 상태가 아니라 relay 한 바퀴의 결과(OutboxRelayResult.Outcome)다. IN_FLIGHT는 상태라 세지 않는다. + # STALE: relay의 claim을 결과를 쓰기 전에 다른 쪽이 넘겨받았다(V17 lease fence). RELEASED: 멈추는 relay가 + # 쓰지 않은 claim을 돌려줬다. allowed_values: [PUBLISHED, FAILED, DEAD, STALE, RELEASED] percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "FAILED rate > 1% for 10m, or STALE > 0 for 10m (in-flight timeout shorter than a relay stall)" + p2: "FAILED 비율 > 1%가 10m 동안, 또는 STALE > 0이 10m 동안(in-flight timeout이 relay 정지보다 짧다)" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [event_type, outcome, event_id] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-domain-event-outbox-contract — row status enum PENDING/IN_FLIGHT/PUBLISHED/FAILED/DEAD + # 출처: feature-domain-event-outbox-contract — 행 상태 enum PENDING/IN_FLIGHT/PUBLISHED/FAILED/DEAD - name: outbox.publisher.lag type: gauge unit: seconds @@ -372,15 +373,15 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "lag > 60s for 10m" - p1: "lag > 300s for 5m" + p2: "lag > 60s가 10m 동안" + p1: "lag > 300s가 5m 동안" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [event_type] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-domain-event-outbox-contract — row status enum + Outbox Defaults attemptCount - # PARKED: an operator held a row that was retried without end (re-review 2026-11-03 RR-05-03). + # 출처: feature-domain-event-outbox-contract — row status enum + Outbox Defaults attemptCount + # PARKED: 끝없이 재시도되던 행을 운영자가 붙잡아 둠 (re-review 2026-11-03 RR-05-03). - name: outbox.pending.size type: gauge unit: total @@ -390,19 +391,19 @@ metrics: allowed_values: [PENDING, IN_FLIGHT, PUBLISHED, FAILED, DEAD, PARKED] percentiles: null histogram_buckets: null - # DEAD > 0: the claim moves a row it will not hand out to DEAD without a relay result, so - # outbox.publisher.published.total{outcome=DEAD} misses it (re-review round 2, RR-02-12). + # DEAD > 0: claim은 내주지 않을 행을 relay 결과 없이 DEAD로 옮기므로 + # outbox.publisher.published.total{outcome=DEAD}가 그것을 놓친다 (re-review round 2, RR-02-12). alert_severity_thresholds: p1: "DEAD > 0 (runbook://outbox/dead-letter)" - p2: "PENDING size growing for 10m" + p2: "PENDING 크기가 10m 동안 늘어남" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [status] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: re-review 2026-11-03 RR-05-03 — a refusal for now and an unanswered publish are retried - # without end; these count the FAILED rows deferred at least 10 times (OutboxMetrics - # LONG_RETRY_DEFERRED_CLAIMS, the publish-failed runbook's §4.1 query) and age the oldest of them. + # 출처: re-review 2026-11-03 RR-05-03 — 지금의 거절과 답이 없는 발행은 끝없이 재시도된다. 이 둘은 + # 10번 이상 미뤄진 FAILED 행을 세고(OutboxMetrics LONG_RETRY_DEFERRED_CLAIMS, publish-failed runbook §4.1 + # 조회), 그중 가장 오래된 것의 나이를 잰다. - name: outbox.retry.long.size type: gauge unit: total @@ -410,7 +411,7 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "> 0 for 10m (runbook://outbox/publish-failed §4.1)" + p2: "> 0이 10m 동안 (runbook://outbox/publish-failed §4.1)" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [] compatibility_impact: additive @@ -429,8 +430,8 @@ metrics: compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === Cache === - # source: feature-cache-consistency-contract — Decisionized Work Items "cache pattern | cache-aside default" + # === 캐시 === + # 출처: feature-cache-consistency-contract — Decisionized Work Items "cache pattern | cache-aside default" - name: cache.gets.total type: counter unit: total @@ -443,13 +444,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p3: "hit_ratio < baseline 0.5x for 1h" + p3: "hit_ratio < 기준선의 0.5배가 1h 동안" owner_branch: feature-cache-consistency-contract log_field_mapping: [cache_name, result] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-cache-consistency-contract — "invalidation = after-commit only", "invalidation 실패가 조용히 무시되면 실패" + # 출처: feature-cache-consistency-contract — "invalidation = after-commit only", "invalidation 실패가 조용히 무시되면 실패" - name: cache.invalidations.total type: counter unit: total @@ -462,13 +463,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "FAILURE rate > 0 for 5m" + p2: "FAILURE 비율 > 0이 5m 동안" owner_branch: feature-cache-consistency-contract log_field_mapping: [cache_name, outcome] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: redis-production-capability — optional bounded cache-only L1 + # 출처: redis-production-capability — 크기가 정해진 캐시 전용 L1 (선택) - name: cache.local.requests.total type: counter unit: total @@ -481,13 +482,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p3: "bypass or error rate above baseline for 15m" + p3: "bypass 또는 error 비율이 기준선보다 높은 상태가 15m 동안" owner_branch: redis-production-capability log_field_mapping: [cache_name, result] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: redis-production-capability — local stale-age bound + # 출처: redis-production-capability — 로컬 stale 나이 상한 - name: cache.local.entry.age.seconds type: timer unit: seconds @@ -497,13 +498,13 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p3: "p99 approaches configured local TTL for 30m" + p3: "p99가 설정한 로컬 TTL에 가까운 상태가 30m 동안" owner_branch: redis-production-capability log_field_mapping: [cache_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: redis-production-capability — bounded invalidation and generation reconciliation + # 출처: redis-production-capability — 크기가 정해진 무효화와 세대 대조(reconciliation) - name: cache.local.maintenance.total type: counter unit: total @@ -530,37 +531,36 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "reconcile_error, subscriber_overflow, or sustained disconnects for 5m" + p2: "reconcile_error, subscriber_overflow, 또는 끊김이 5m 동안 계속" owner_branch: redis-production-capability log_field_mapping: [cache_name, event] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === Redis connection lanes === - # source: review 2026-11-03 RR-04-02 — the cache's conditional writes got their own lane - # (CACHE_SCRIPT) so that cache fills cannot take the SCRIPT lane's connections from idempotency, - # rate limiting and leases. These meters show, per lane, whether that holds. Emitted by - # redis-runtime RedisLaneMetrics for every lane RedisRuntimeOwner pools, only when the context has - # a MeterRegistry. Every counter series is registered at zero at startup. + # === Redis 연결 lane === + # 출처: review 2026-11-03 RR-04-02 — 캐시의 조건부 쓰기는 자기 lane(CACHE_SCRIPT)을 받았다. 캐시 채우기가 + # idempotency·rate limiting·lease의 SCRIPT lane 연결을 가져가지 못하게 하려는 것이다. 이 meter들이 lane마다 + # 그것이 지켜지는지 보여 준다. redis-runtime RedisLaneMetrics가 RedisRuntimeOwner가 pool로 가진 모든 lane에 + # 대해, context에 MeterRegistry가 있을 때만 낸다. 모든 counter 계열은 기동 때 0으로 등록한다. - name: redis.lane.acquire.wait.seconds type: timer unit: seconds tags: - name: lane - # The lane's name: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, - # TRANSACTION, ADMIN (redis-sdk), plus any lane a service composes as a RedisLaneContribution. + # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, + # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 - name: outcome cardinality_limit: 2 allowed_values: [admitted, refused] - # As RedisLaneMetrics registers it: a percentile histogram (publishPercentileHistogram, expected - # range 1ms..10s) and no client-side percentiles and no SLO boundaries. The p99 below is a - # histogram_quantile over the buckets (re-review 2026-11-04 RR-03-17). + # RedisLaneMetrics가 등록하는 모양: percentile histogram(publishPercentileHistogram, 예상 범위 + # 1ms..10s)이고, client 쪽 percentile과 SLO 경계는 없다. 아래 p99는 bucket 위의 histogram_quantile이다 + # (re-review 2026-11-04 RR-03-17). percentiles: null histogram_buckets: percentile_histogram alert_severity_thresholds: - p2: "SCRIPT admitted p99 > 100ms for 10m (the correctness lane is queueing)" - p3: "CACHE_SCRIPT admitted p99 > 100ms for 30m" + p2: "SCRIPT admitted p99 > 100ms가 10m 동안(정확성 lane이 줄을 서고 있다)" + p3: "CACHE_SCRIPT admitted p99 > 100ms가 30m 동안" owner_branch: redis-production-capability log_field_mapping: [lane, outcome] compatibility_impact: additive @@ -571,8 +571,8 @@ metrics: unit: total tags: - name: lane - # The lane's name: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, - # TRANSACTION, ADMIN (redis-sdk), plus any lane a service composes as a RedisLaneContribution. + # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, + # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 - name: reason cardinality_limit: 4 @@ -580,8 +580,8 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p1: "SCRIPT or REGULAR saturated or connect_failed above zero for 2m while a correctness role is selected" - p2: "CACHE_SCRIPT saturated above baseline for 10m" + p1: "정확성 role을 고른 상태에서 SCRIPT 또는 REGULAR의 saturated나 connect_failed가 0보다 큰 상태가 2m 동안" + p2: "CACHE_SCRIPT saturated가 기준선보다 높은 상태가 10m 동안" owner_branch: redis-production-capability log_field_mapping: [lane, reason] compatibility_impact: additive @@ -592,13 +592,13 @@ metrics: unit: total tags: - name: lane - # The lane's name: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, - # TRANSACTION, ADMIN (redis-sdk), plus any lane a service composes as a RedisLaneContribution. + # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, + # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 percentiles: null histogram_buckets: null alert_severity_thresholds: - p3: "opened rate after warm-up above baseline for 15m (reconnect churn against a slow Redis)" + p3: "warm-up 뒤 opened 비율이 기준선보다 높은 상태가 15m 동안(느린 Redis에 다시 연결하며 흔들림)" owner_branch: redis-production-capability log_field_mapping: [lane] compatibility_impact: additive @@ -609,8 +609,8 @@ metrics: unit: total tags: - name: lane - # The lane's name: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, - # TRANSACTION, ADMIN (redis-sdk), plus any lane a service composes as a RedisLaneContribution. + # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, + # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 - name: reason cardinality_limit: 2 @@ -618,7 +618,7 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p3: "invalidated rate above baseline for 15m (timed-out or failed calls discarding connections)" + p3: "invalidated 비율이 기준선보다 높은 상태가 15m 동안(timeout·실패한 호출이 연결을 버림)" owner_branch: redis-production-capability log_field_mapping: [lane, reason] compatibility_impact: additive @@ -629,13 +629,13 @@ metrics: unit: total tags: - name: lane - # The lane's name: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, - # TRANSACTION, ADMIN (redis-sdk), plus any lane a service composes as a RedisLaneContribution. + # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, + # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "SCRIPT active == configured maximum-script-connections for 5m" + p2: "SCRIPT active == 설정한 maximum-script-connections가 5m 동안" owner_branch: redis-production-capability log_field_mapping: [lane] compatibility_impact: additive @@ -646,20 +646,20 @@ metrics: unit: total tags: - name: lane - # The lane's name: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, - # TRANSACTION, ADMIN (redis-sdk), plus any lane a service composes as a RedisLaneContribution. + # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, + # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "SCRIPT pending > 0 for 5m" + p2: "SCRIPT pending > 0이 5m 동안" owner_branch: redis-production-capability log_field_mapping: [lane] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === Log appender === - # source: feature-log-management-contract — Sampling Policy (final) + # === 로그 appender === + # 출처: feature-log-management-contract — Sampling Policy (final) # "async appender overflow default: drop oldest INFO/DEBUG with counter metric (log.appender.dropped.total)" - name: log.appender.dropped.total type: counter @@ -673,14 +673,14 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "dropped > 0 sustained for 10m" + p2: "dropped > 0이 10m 동안 계속" owner_branch: feature-log-management-contract log_field_mapping: [appender, level] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === Distributed tracing === - # source: feature-distributed-tracing-contract — decisions + # === 분산 추적 === + # 출처: feature-distributed-tracing-contract — decisions # "trace sampling rate default = prod 1%, dev/local 100%; shipped runtime profiles are local|dev|prod" - name: tracing.sampling.rate type: gauge @@ -692,14 +692,14 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p3: "effective rate deviates from configured for 1h" + p3: "실제 비율이 설정값과 1h 동안 어긋남" owner_branch: feature-distributed-tracing-contract log_field_mapping: [profile] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # === JVM baseline === - # source: feature-metrics-alerting-contract — In scope "JVM/process metric" + # === JVM 기본 === + # 출처: feature-metrics-alerting-contract — In scope "JVM/process metric" - name: jvm.memory.used type: gauge unit: bytes @@ -712,13 +712,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p2: "heap used / max > 0.85 for 10m" + p2: "heap used / max > 0.85가 10m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [area, id] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-metrics-alerting-contract — In scope "JVM/process metric" + # 출처: feature-metrics-alerting-contract — 범위 안 \"JVM/process metric\" - name: jvm.gc.pause type: timer unit: seconds @@ -730,13 +730,13 @@ metrics: percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: - p2: "p99 pause > 500ms for 10m" + p2: "p99 pause > 500ms가 10m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [action, cause] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-metrics-alerting-contract — In scope "JVM/process metric" + # 출처: feature-metrics-alerting-contract — 범위 안 \"JVM/process metric\" - name: jvm.threads.live type: gauge unit: total @@ -744,13 +744,13 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p3: "thread count > 2x baseline for 30m" + p3: "thread 수 > 기준선의 2배가 30m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - # source: feature-metrics-alerting-contract — In scope "JVM/process metric" (process uptime) + # 출처: feature-metrics-alerting-contract — 범위 안 \"JVM/process metric\" (process uptime) - name: process.uptime type: gauge unit: seconds @@ -758,7 +758,7 @@ metrics: percentiles: null histogram_buckets: null alert_severity_thresholds: - p1: "uptime reset unexpectedly < 60s (crash loop signal)" + p1: "uptime이 예상 밖으로 < 60s로 초기화됨(crash loop 신호)" owner_branch: feature-metrics-alerting-contract log_field_mapping: [] compatibility_impact: additive diff --git a/docs/registries/object-storage-readiness.yaml b/docs/registries/object-storage-readiness.yaml index b9d2d0ae..9efa7038 100644 --- a/docs/registries/object-storage-readiness.yaml +++ b/docs/registries/object-storage-readiness.yaml @@ -14,9 +14,9 @@ claims: required_tasks: - ":adapter:outbound:objectstorage:check" limitations: - - single-process control CAS only; no multi-node linearizability - - fsync and atomic move tests do not prove power-loss durability - - local development provider is forbidden in production profiles + - 한 프로세스 안의 control CAS만 보장한다. 여러 노드의 선형성(linearizability)은 없다 + - fsync·atomic move 시험은 전원이 꺼져도 남는다는 것을 증명하지 않는다 + - 로컬 개발용 제공자는 production profile에서 쓸 수 없다 - card_id: object-storage-managed-upload-multipart provider_type: filesystem-local-dev @@ -28,7 +28,7 @@ claims: required_tasks: - ":application-core:check" limitations: - - multipart publication protocol is not implemented + - multipart 게시 프로토콜은 구현하지 않았다 - card_id: object-storage-managed-download provider_type: filesystem-local-dev @@ -40,8 +40,8 @@ claims: required_tasks: - ":adapter:outbound:objectstorage:check" limitations: - - local functional full and range reads are not production-provider qualification - - no multi-node or power-loss durability claim + - 로컬의 전체·범위 읽기 기능 시험은 운영 제공자 qualification이 아니다 + - 여러 노드나 전원 손실에 대한 내구성은 주장하지 않는다 - card_id: object-storage-direct-upload-single provider_type: filesystem-local-dev @@ -53,7 +53,7 @@ claims: required_tasks: - ":application-core:check" limitations: - - direct grant provider and public inbound endpoint are not implemented + - 직접 grant 제공자와 공개 inbound endpoint는 구현하지 않았다 - card_id: object-storage-direct-upload-multipart provider_type: filesystem-local-dev @@ -65,7 +65,7 @@ claims: required_tasks: - ":application-core:check" limitations: - - direct multipart session and public inbound endpoint are not implemented + - 직접 multipart session과 공개 inbound endpoint는 구현하지 않았다 - card_id: object-storage-direct-download provider_type: filesystem-local-dev @@ -77,7 +77,7 @@ claims: required_tasks: - ":application-core:check" limitations: - - direct download grant and public inbound endpoint are not implemented + - 직접 download grant와 공개 inbound endpoint는 구현하지 않았다 - card_id: object-storage-quarantine-publication provider_type: filesystem-local-dev @@ -89,7 +89,7 @@ claims: required_tasks: - ":application-core:check" limitations: - - scanner handoff and verdict fencing are not implemented + - scanner 인계와 판정 fencing은 구현하지 않았다 - card_id: object-storage-retention provider_type: filesystem-local-dev @@ -101,8 +101,8 @@ claims: required_tasks: - ":application-core:check" limitations: - - retention and legal-hold provider enforcement are not implemented - - privileged purge composition remains intentionally empty + - 보존(retention)·법적 보존(legal hold)의 제공자 쪽 강제는 구현하지 않았다 + - 특권 purge 조립은 일부러 비워 두었다 - card_id: object-storage-reconciliation provider_type: filesystem-local-dev @@ -114,5 +114,5 @@ claims: required_tasks: - ":application-core:check" limitations: - - local create resolution is single-process functional evidence only - - production response-loss and multi-node reconciliation are not implemented + - 로컬 create 해소는 한 프로세스 안의 기능 증거일 뿐이다 + - 운영 환경의 응답 유실과 여러 노드 사이의 맞춤(reconciliation)은 구현하지 않았다 diff --git a/docs/registries/secrets-classification.yaml b/docs/registries/secrets-classification.yaml index bddb0aeb..860b33f3 100644 --- a/docs/registries/secrets-classification.yaml +++ b/docs/registries/secrets-classification.yaml @@ -3,8 +3,8 @@ # Owner branch: feature-secrets-config-source-contract # Last updated: 2026-05-22 # -# Conventions: -# - 3-tier classification (feature-secrets-config-source-contract 2026-05-22): +# 표기 규칙 +# - 분류는 세 등급이다 (feature-secrets-config-source-contract 2026-05-22): # public-config | sensitive-config | secret # - `secret` rows: prod_default 항상 null. dev fake 식별자는 `__LOCAL_DEV_` prefix # (feature-secrets-config-source-contract 2026-05-22: "dev/local sentinel value prefix = __LOCAL_DEV_"). @@ -15,22 +15,23 @@ # RR-07-04). 비밀값만 본다: 이 파일의 `secret` 행(SecretSourceValidator.CLASSIFIED_SECRETS, # SecretsClassificationRegistryTest가 1:1로 묶음), 모듈이 기여한 비밀, `secret://…/` 참조가 # 가리키는 변수. HOSTNAME·앱 이름 같은 비밀이 아닌 값은 보지 않는다 (review 2026-11-04 RR2-04-01). -# - Masking 기본 = `full_except_last_4` (feature-secrets-config-source-contract 2026-05-22: -# "full mask except last 4 chars for non-secret tokens"). 진짜 secret(password/private key)은 `full`. -# - Naming suffix는 보조 신호 (feature-secrets-config-source-contract: "_TOKEN, _KEY, _PASSWORD"). +# - 가림(masking) 기본 = `full_except_last_4` (feature-secrets-config-source-contract 2026-05-22: +# "full mask except last 4 chars for non-secret tokens" — 비밀이 아닌 토큰은 끝 4자만 남기고 가린다). +# 진짜 secret(password/private key)은 `full`. +# - 이름 접미사는 보조 신호다 (feature-secrets-config-source-contract: "_TOKEN, _KEY, _PASSWORD"). # - public-config 항목은 env-keys.yaml에서 직접 정의되며 본 파일에는 reference row만 둠. secrets: - # === Tier 3: secret (true secret — password/private-key/HMAC-salt) === + # === 3등급: secret (진짜 비밀 — password/private-key/HMAC-salt) === - name: APP_DATASOURCE_PASSWORD - # source: feature-secrets-config-source-contract 2026-05-22 + # 출처: feature-secrets-config-source-contract 2026-05-22 # "DB credential은 dual-bind 60s" + "__LOCAL_DEV_FAKE_DB_PASSWORD" 예시 classification: secret source: secret-manager - # Contributed by persistence-jpa (JpaStartupAutoConfiguration#jpaProductionSecrets) while the - # module is on; the composition root's guard no longer reads the module switch (P22-new-1). + # persistence-jpa가 모듈이 켜진 동안 기여한다(JpaStartupAutoConfiguration#jpaProductionSecrets). 조립 루트의 + # 관문은 이제 모듈 스위치를 읽지 않는다(P22-new-1). required_when: app.persistence-jpa.enabled=true rotation_policy: dual-bind-60s prod_default: null @@ -41,8 +42,8 @@ secrets: required_test: secrets-contract:db-password-no-leak-in-actuator - name: SPRING_MAIL_PASSWORD - # source: notification/fileserver techlead review H2 — credential consumed natively by Spring - # Mail and therefore intentionally retains the SPRING_* name rather than gaining an APP_* alias. + # 출처: notification/fileserver techlead review H2 — Spring Mail이 직접 읽는 자격 증명이라 APP_* 별칭을 두지 + # 않고 일부러 SPRING_* 이름을 유지한다. classification: secret source: secret-manager rotation_policy: restart-only @@ -55,14 +56,14 @@ secrets: required_test: secrets-contract:smtp-password-no-leak - name: APP_CACHE_REDIS_PASSWORD - # source: feature-secrets-config-source-contract 2026-05-22 - # 3-tier classification "secret" + feature-integration-adapter-templates "Redis | disabled optional module" - # (Redis enabled + auth 사용 시 secret으로 분류) + # 출처: feature-secrets-config-source-contract 2026-05-22 + # 3등급 분류 "secret" + feature-integration-adapter-templates "Redis | disabled optional module" + # (Redis를 켜고 인증을 쓰면 secret으로 분류) classification: secret source: secret-manager rotation_policy: restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.capabilities.cache.bindings.default=redis dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: feature-secrets-config-source-contract @@ -71,7 +72,7 @@ secrets: required_test: secrets-contract:redis-password-no-leak - name: APP_CACHE_REDIS_TRUST_PEM - # Public CA bundle content, but integrity-sensitive and supplied by the mounted environment. + # 공개 CA bundle 내용이지만 무결성이 중요하고, 마운트된 환경이 준다. classification: sensitive-config source: mounted-env rotation_policy: restart-only @@ -83,12 +84,12 @@ secrets: required_test: secrets-contract:redis-trust-reference-no-leak - name: APP_CACHE_REDIS_KEY_HMAC_SECRET - # Stable cache-key HMAC material. It is distinct from the Redis authentication credential. + # 바뀌지 않는 캐시 key HMAC 자료. Redis 인증 자격 증명과 다르다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.capabilities.cache.bindings.default=redis dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: codex-phase-a-ci-recovery @@ -97,12 +98,12 @@ secrets: required_test: secrets-contract:redis-key-hmac-no-leak - name: APP_RATE_LIMIT_REDIS_PASSWORD - # Dedicated coordination-role Redis credential. It is never inherited from cache Redis. + # coordination role 전용 Redis 자격 증명. 캐시 Redis에서 물려받지 않는다. classification: secret source: secret-manager rotation_policy: restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.capabilities.rate-limit.provider=redis dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: redis-distributed-rate-limit @@ -111,7 +112,7 @@ secrets: required_test: secrets-contract:rate-limit-redis-password-no-leak - name: APP_RATE_LIMIT_REDIS_TRUST_PEM - # Coordination-role CA bundle content; integrity-sensitive but not credential material. + # coordination role CA bundle 내용. 무결성이 중요하지만 자격 증명 자료는 아니다. classification: sensitive-config source: mounted-env rotation_policy: restart-only @@ -123,12 +124,12 @@ secrets: required_test: secrets-contract:rate-limit-redis-trust-reference-no-leak - name: APP_RATE_LIMIT_REDIS_KEY_HMAC_SECRET - # Stable private-key derivation material for rate-limit subjects and policy revisions. + # rate-limit 대상과 정책 개정에 쓰는, 바뀌지 않는 비공개 key 파생 자료. classification: secret source: secret-manager rotation_policy: dual-read-restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.capabilities.rate-limit.provider=redis dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: redis-distributed-rate-limit @@ -137,12 +138,12 @@ secrets: required_test: secrets-contract:rate-limit-redis-key-hmac-no-leak - name: APP_SESSION_REDIS_PASSWORD - # Dedicated session-role ACL credential; never shared implicitly with cache or coordination. + # session role 전용 ACL 자격 증명. 캐시나 coordination과 몰래 함께 쓰지 않는다. classification: secret source: secret-manager rotation_policy: restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.security.auth-mode=redis-session dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: redis-production-capability @@ -151,7 +152,7 @@ secrets: required_test: secrets-contract:session-redis-password-no-leak - name: APP_SESSION_REDIS_TRUST_PEM - # Session-role CA bundle content; integrity-sensitive but not credential material. + # session role CA bundle 내용. 무결성이 중요하지만 자격 증명 자료는 아니다. classification: sensitive-config source: mounted-env rotation_policy: restart-only @@ -163,12 +164,12 @@ secrets: required_test: secrets-contract:session-redis-trust-reference-no-leak - name: APP_SESSION_REDIS_KEY_HMAC_SECRET - # Stable private derivation material for pseudonymous Redis session keys. + # 가명 Redis session key에 쓰는, 바뀌지 않는 비공개 파생 자료. classification: secret source: secret-manager rotation_policy: dual-read-restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.security.auth-mode=redis-session dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: redis-production-capability @@ -177,12 +178,12 @@ secrets: required_test: secrets-contract:session-redis-key-hmac-no-leak - name: APP_IDEMPOTENCY_REDIS_KEY_HMAC_SECRET - # Owner-safe request-replay keys must not expose tenant/scope/request identifiers. + # owner-safe 요청 replay key가 tenant·scope·요청 식별자를 드러내면 안 된다. classification: secret source: secret-manager rotation_policy: cold-cutover-restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.capabilities.idempotency.provider=redis dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: redis-production-capability-completion @@ -191,12 +192,12 @@ secrets: required_test: secrets-contract:idempotency-redis-key-hmac-no-leak - name: APP_LEASE_REDIS_KEY_HMAC_SECRET - # Efficiency-lease resource and owner scopes use a dedicated derivation key. + # 효율 lease의 자원·소유자 scope는 전용 파생 key를 쓴다. classification: secret source: secret-manager rotation_policy: cold-cutover-restart-only prod_default: null - # Required with app.redis.enabled=true and this role selected; checked by adapter-outbound-cache-redis RedisProductionSecrets. + # app.redis.enabled=true이고 이 role을 고르면 필요하다. adapter-outbound-cache-redis의 RedisProductionSecrets가 확인한다. required_when: app.capabilities.lease.provider=redis dev_sentinel_prefix: __LOCAL_DEV_ owner_branch: redis-production-capability-completion @@ -205,7 +206,7 @@ secrets: required_test: secrets-contract:lease-redis-key-hmac-no-leak - name: APP_PRIVACY_PSEUDONYMIZATION_SALT - # source: feature-data-retention-privacy-contract 2026-05-22 + # 출처: feature-data-retention-privacy-contract 2026-05-22 # "pseudonymization key = HMAC-SHA-256 with rotating salt. salt rotation interval = 90일. # rotation 시 old salt 90일 retain (lookup 가능)." # + feature-tenant-context-policy "tenant identifier는 raw PII가 아니어야 하며 ... pseudonymized id" @@ -219,13 +220,12 @@ secrets: compatibility_impact: breaking required_test: secrets-contract:pseudonymization-salt-rotation - # === Tier 2: sensitive-config (token-bearing URL or id with exposure restriction) === + # === 2등급: sensitive-config (토큰이 든 URL이나 노출을 제한할 id) === - name: APP_NOTIFICATION_PLATFORM_CONTACT_ENCRYPTION_KEY - # Encrypts recipient contact points at rest — addresses and phone numbers. - # One of seven purpose-scoped keys. They must all differ: a single key reused across purposes - # means a compromise of any one of them is a compromise of all seven, and the platform enforces - # the distinction at startup rather than trusting the deployment to have noticed. + # 저장된 수신자 연락처(주소와 전화번호)를 암호화한다. + # purpose별 key 일곱 중 하나다. 모두 달라야 한다: 한 key를 여러 용도에 다시 쓰면 하나가 털릴 때 일곱이 모두 + # 털린다. 플랫폼은 배포가 알아챘으리라 믿지 않고 기동할 때 구별을 강제한다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only @@ -238,10 +238,9 @@ secrets: required_test: secrets-contract:notification-contact-encryption-no-leak - name: APP_NOTIFICATION_PLATFORM_CONTACT_LOOKUP_HMAC_KEY - # Blind index over contact points, so a lookup never needs the plaintext. - # One of seven purpose-scoped keys. They must all differ: a single key reused across purposes - # means a compromise of any one of them is a compromise of all seven, and the platform enforces - # the distinction at startup rather than trusting the deployment to have noticed. + # 연락처의 blind index. 조회에 평문이 필요 없게 한다. + # purpose별 key 일곱 중 하나다. 모두 달라야 한다: 한 key를 여러 용도에 다시 쓰면 하나가 털릴 때 일곱이 모두 + # 털린다. 플랫폼은 배포가 알아챘으리라 믿지 않고 기동할 때 구별을 강제한다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only @@ -254,10 +253,9 @@ secrets: required_test: secrets-contract:notification-contact-lookup-hmac-no-leak - name: APP_NOTIFICATION_PLATFORM_CALLBACK_SIGNING_KEY - # Signs the callback URLs a provider posts delivery outcomes back to. - # One of seven purpose-scoped keys. They must all differ: a single key reused across purposes - # means a compromise of any one of them is a compromise of all seven, and the platform enforces - # the distinction at startup rather than trusting the deployment to have noticed. + # provider가 전달 결과를 보내는 callback URL에 서명한다. + # purpose별 key 일곱 중 하나다. 모두 달라야 한다: 한 key를 여러 용도에 다시 쓰면 하나가 털릴 때 일곱이 모두 + # 털린다. 플랫폼은 배포가 알아챘으리라 믿지 않고 기동할 때 구별을 강제한다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only @@ -270,10 +268,9 @@ secrets: required_test: secrets-contract:notification-callback-signing-no-leak - name: APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY - # Encrypts stored provider credentials, which are themselves secrets. - # One of seven purpose-scoped keys. They must all differ: a single key reused across purposes - # means a compromise of any one of them is a compromise of all seven, and the platform enforces - # the distinction at startup rather than trusting the deployment to have noticed. + # 저장된 provider 자격 증명(그 자체가 비밀)을 암호화한다. + # purpose별 key 일곱 중 하나다. 모두 달라야 한다: 한 key를 여러 용도에 다시 쓰면 하나가 털릴 때 일곱이 모두 + # 털린다. 플랫폼은 배포가 알아챘으리라 믿지 않고 기동할 때 구별을 강제한다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only @@ -286,10 +283,9 @@ secrets: required_test: secrets-contract:notification-provider-credential-no-leak - name: APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY - # Encrypts notification variables and retained callback bodies at rest. - # One of seven purpose-scoped keys. They must all differ: a single key reused across purposes - # means a compromise of any one of them is a compromise of all seven, and the platform enforces - # the distinction at startup rather than trusting the deployment to have noticed. + # 저장된 알림 변수와 보관한 callback 본문을 암호화한다. + # purpose별 key 일곱 중 하나다. 모두 달라야 한다: 한 key를 여러 용도에 다시 쓰면 하나가 털릴 때 일곱이 모두 + # 털린다. 플랫폼은 배포가 알아챘으리라 믿지 않고 기동할 때 구별을 강제한다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only @@ -302,10 +298,9 @@ secrets: required_test: secrets-contract:notification-payload-encryption-no-leak - name: APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY - # Keyed hash of provider request ids, which are provider-side identifiers. - # One of seven purpose-scoped keys. They must all differ: a single key reused across purposes - # means a compromise of any one of them is a compromise of all seven, and the platform enforces - # the distinction at startup rather than trusting the deployment to have noticed. + # provider 쪽 식별자인 provider request id의 key 있는 hash. + # purpose별 key 일곱 중 하나다. 모두 달라야 한다: 한 key를 여러 용도에 다시 쓰면 하나가 털릴 때 일곱이 모두 + # 털린다. 플랫폼은 배포가 알아챘으리라 믿지 않고 기동할 때 구별을 강제한다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only @@ -318,10 +313,9 @@ secrets: required_test: secrets-contract:notification-provider-request-lookup-hmac-no-leak - name: APP_NOTIFICATION_PLATFORM_CALLBACK_FINGERPRINT_HMAC_KEY - # Keyed fingerprint of callback bodies, used to detect replays. - # One of seven purpose-scoped keys. They must all differ: a single key reused across purposes - # means a compromise of any one of them is a compromise of all seven, and the platform enforces - # the distinction at startup rather than trusting the deployment to have noticed. + # callback 본문의 key 있는 fingerprint. replay를 찾는 데 쓴다. + # purpose별 key 일곱 중 하나다. 모두 달라야 한다: 한 key를 여러 용도에 다시 쓰면 하나가 털릴 때 일곱이 모두 + # 털린다. 플랫폼은 배포가 알아챘으리라 믿지 않고 기동할 때 구별을 강제한다. classification: secret source: secret-manager rotation_policy: dual-read-restart-only @@ -334,7 +328,7 @@ secrets: required_test: secrets-contract:notification-callback-fingerprint-hmac-no-leak - name: APP_NOTIFICATION_SLACK_WEBHOOK_URL - # source: feature-integration-adapter-templates 2026-05-22 + # 출처: feature-integration-adapter-templates 2026-05-22 # "Slack | disabled optional module | notification failure policy" # Slack webhook URL은 token을 path에 포함하므로 sensitive-config (URL 형태이지만 secret과 동급 취급) classification: sensitive-config @@ -348,8 +342,8 @@ secrets: required_test: secrets-contract:slack-webhook-no-leak - name: APP_SECURITY_GOOGLE_OAUTH_CLIENT_ID - # source: feature-secrets-config-source-contract 2026-05-22 - # "sensitive-config" tier (id이지만 노출 제한) + # 출처: feature-secrets-config-source-contract 2026-05-22 + # "sensitive-config" 등급 (id이지만 노출 제한) # + feature-integration-adapter-templates "Google Email | disabled optional module" classification: sensitive-config source: mounted-env @@ -362,7 +356,7 @@ secrets: required_test: secrets-contract:google-oauth-client-id-masked - name: APP_DATASOURCE_USERNAME - # source: feature-secrets-config-source-contract 2026-05-22 — "sensitive-config" tier + # 출처: feature-secrets-config-source-contract 2026-05-22 — "sensitive-config" 등급 # (DB user는 password와 함께 노출되면 위험하므로 sensitive-config) classification: sensitive-config source: mounted-env @@ -375,8 +369,8 @@ secrets: required_test: secrets-contract:datasource-username-masked-in-actuator - name: SPRING_MONGODB_URI - # MongoDB URIs can carry username/password material and must never be logged as public config. - # Typed-profile deployments should prefer uri-secret so the URI itself never becomes env data. + # MongoDB URI에는 사용자 이름·비밀번호가 들어 있을 수 있어 public config로 로그에 남기면 안 된다. + # typed profile 배포는 URI 자체가 env 데이터가 되지 않게 uri-secret을 쓰는 편이 낫다. classification: sensitive-config source: mounted-env rotation_policy: restart-only @@ -388,7 +382,7 @@ secrets: required_test: secrets-contract:mongodb-uri-masked - name: APP_DATASOURCE_URL - # source: feature-secrets-config-source-contract 2026-05-22 — JDBC URL은 host/db 포함하므로 sensitive-config + # 출처: feature-secrets-config-source-contract 2026-05-22 — JDBC URL은 host/db 포함하므로 sensitive-config # (env-keys.yaml에서는 public-config 처리; 본 파일에서는 노출 통제 관점에서 sensitive로 재분류 — masking 기준 명시 목적) classification: sensitive-config source: mounted-env @@ -400,10 +394,10 @@ secrets: compatibility_impact: breaking required_test: secrets-contract:datasource-url-masked-in-actuator - # === Tier 1: public-config (reference only — full row in env-keys.yaml) === + # === 1등급: public-config (참조만 — 행 전체는 env-keys.yaml에 있다) === - name: APP_PROFILE - # source: feature-env-driven-runtime-configuration — public-config tier reference + # 출처: feature-env-driven-runtime-configuration — public-config 등급 참조 classification: public-config source: application-yml owner_branch: feature-env-driven-runtime-configuration @@ -411,7 +405,7 @@ secrets: reference: env-keys.yaml#APP_PROFILE - name: APP_NAME - # source: feature-env-driven-runtime-configuration — public-config tier reference + # 출처: feature-env-driven-runtime-configuration — public-config 등급 참조 classification: public-config source: application-yml owner_branch: feature-env-driven-runtime-configuration @@ -419,7 +413,7 @@ secrets: reference: env-keys.yaml#APP_NAME - name: SERVER_PORT - # source: feature-env-driven-runtime-configuration — Spring native, public-config tier reference + # 출처: feature-env-driven-runtime-configuration — Spring 자체 키, public-config 등급 참조 classification: public-config source: application-yml owner_branch: feature-env-driven-runtime-configuration @@ -427,7 +421,7 @@ secrets: reference: env-keys.yaml#SERVER_PORT - name: SPRING_PROFILES_ACTIVE - # source: feature-env-driven-runtime-configuration — Spring native, public-config tier reference + # 출처: feature-env-driven-runtime-configuration — Spring 자체 키, public-config 등급 참조 classification: public-config source: application-yml owner_branch: feature-env-driven-runtime-configuration @@ -435,7 +429,7 @@ secrets: reference: env-keys.yaml#SPRING_PROFILES_ACTIVE - name: OTEL_EXPORTER_OTLP_ENDPOINT - # source: feature-distributed-tracing-contract — public-config tier reference + # 출처: feature-distributed-tracing-contract — public-config 등급 참조 classification: public-config source: application-yml owner_branch: feature-distributed-tracing-contract