docs(registries): 출처 줄의 꼬리표와 기록 절 이름을 원문으로 되돌린다

문제: 앞 커밋이 레지스트리 주석의 `# source:`를 `# 출처:`로 바꾸고, 출처 줄 안의 기록 절
이름(「In scope」「Decisionized Work Items」「decisions」「Exposure Policy」「AuthN/AuthZ
Decision Matrix」)까지 한국어로 옮겼다. 출처 줄은 기록 이름·날짜·절 이름으로 원문을
찾아가는 줄이라, 옮기면 그 기록에서 같은 이름을 찾을 수 없다. 또 metrics.yaml 주석 세 줄에
변환 실수로 `\"`(백슬래시가 붙은 따옴표)가 들어갔다.

고른 방법: 총괄 기준(2026-11-07)대로 나눈다.
- 원문으로 둔다: 출처 줄의 꼬리표 `source:`, 기록 이름·날짜·절 이름, 따옴표 인용.
- 한국어로 둔다: 같은 줄의 나머지 설명, 행마다의 이유·조건·주의 산문, 값 칸, 파일 머리 블록.
- `\"`는 `"`로 고친다.

위험·한계: 출처가 가리키는 `feature-*` 계약 기록 24개는 저장소 어디에도(이력 포함) 그 이름의
파일이 없다. `docs/design/`에 있는 것은 `five-adapter-runtime-remediation`과
`redis-production-capability` 둘이고, 파일 이름에 날짜와 `-design`이 붙어 있다. 이름은 고치지
않았다.

검증: 여덟 파일을 `yaml.safe_load`로 읽은 데이터가 앞 커밋과 같다(주석만 바뀜).
`python3 scripts/check-docs.py` rc=0.
This commit is contained in:
DongHyeonka
2026-11-07 17:49:10 +09:00
parent 05e2145d22
commit ad859ca3a6
7 changed files with 299 additions and 299 deletions
+11 -11
View File
@@ -19,8 +19,8 @@
capabilities:
# 출처: feature-repository-access-permission-contract — 판정 기준 "Required capability: READ_REPOSITORY"
# 출처: feature-application-port-usecase-contract — "read-only query use case는 readOnly 와 READ_REPOSITORY capability만 선언 가능"
# 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만 선언 가능"
- name: READ_REPOSITORY
scope: use_case_method
enforcement: archunit
@@ -32,8 +32,8 @@ capabilities:
compatibility_impact: breaking
required_test: architecture-enforcement:read-repository-capability
# 출처: feature-repository-access-permission-contract — 판정 기준 "Required capability: WRITE_REPOSITORY"
# 출처: feature-application-port-usecase-contract — "write use case는 transactionMode, idempotency, repositoryAccess를 명시해야 함"
# source: feature-repository-access-permission-contract — 판정 기준 "Required capability: WRITE_REPOSITORY"
# source: feature-application-port-usecase-contract — "write use case는 transactionMode, idempotency, repositoryAccess를 명시해야 함"
- name: WRITE_REPOSITORY
scope: use_case_method
enforcement: archunit
@@ -45,7 +45,7 @@ capabilities:
compatibility_impact: breaking
required_test: architecture-enforcement:write-repository-capability
# 출처: feature-repository-access-permission-contract — decisions 2026-05-22
# source: 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
@@ -58,7 +58,7 @@ capabilities:
compatibility_impact: breaking
required_test: architecture-enforcement:sensitive-read-capability
# 출처: feature-repository-access-permission-contract — decisions 2026-05-22
# source: 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
@@ -71,9 +71,9 @@ capabilities:
compatibility_impact: breaking
required_test: architecture-enforcement:bulk-write-capability
# 출처: feature-repository-access-permission-contract — decisions 2026-05-22
# source: 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
# source: 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
# 출처: feature-repository-access-permission-contract — decisions 2026-05-22
# source: 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가 없으면 실패"
# source: feature-application-port-usecase-contract — "outbound adapter 호출 use case에 EXTERNAL_OUTBOUND_ALLOWED가 없으면 실패"
- name: EXTERNAL_OUTBOUND_ALLOWED
scope: use_case_method
enforcement: archunit
@@ -99,7 +99,7 @@ capabilities:
compatibility_impact: breaking
required_test: architecture-enforcement:external-outbound-capability
# 출처: feature-repository-access-permission-contract — decisions 2026-05-22
# source: 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
File diff suppressed because it is too large Load Diff
+55 -55
View File
@@ -38,7 +38,7 @@ errors:
# AUTH (feature-security-operational-baseline / Decision Matrix)
# ============================================================
# 출처: feature-security-operational-baseline L82 — "token 누락 | 401 | AUTH_TOKEN_MISSING | AUTH"
# source: 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
# 출처: feature-security-operational-baseline L83 — "token malformed (parse fail) | 401 | AUTH_TOKEN_MALFORMED | AUTH"
# source: 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
# 출처: feature-security-operational-baseline L84 — "token expired (clock skew tolerance 60s 초과) | 401 | AUTH_TOKEN_EXPIRED | AUTH"
# source: 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
# 출처: feature-security-operational-baseline L85 — "invalid signature | 401 | AUTH_TOKEN_INVALID_SIGNATURE | AUTH"
# source: 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
# 출처: feature-security-operational-baseline L86 — "issuer mismatch | 401 | AUTH_ISSUER_MISMATCH | AUTH"
# source: 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
# 출처: feature-security-operational-baseline L87 — "audience mismatch | 401 | AUTH_AUDIENCE_MISMATCH | AUTH"
# source: 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
# 출처: feature-security-operational-baseline L88 — "unknown kid (JWKS 미캐시) | 401 + Retry-After 5s | AUTH_KID_UNKNOWN | AUTH"
# source: 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
# 출처: feature-security-operational-baseline L89 — "JWKS endpoint outage ... | AUTH_JWKS_UNAVAILABLE | TRANSIENT_DEPENDENCY"
# source: 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
# 출처: feature-security-operational-baseline L90 — "claim mapping failure ... | 401 | AUTH_CLAIM_MAPPING_FAILED | AUTH"
# source: 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)
# ============================================================
# 출처: feature-security-operational-baseline L91 — "valid token + 권한 부족 | 403 | AUTHZ_INSUFFICIENT_PERMISSION | AUTHZ"
# source: 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
# 출처: feature-security-operational-baseline L92 — "valid token + tenant cross-access | 403 | AUTHZ_TENANT_MISMATCH | AUTHZ"
# source: 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)
# ============================================================
# 출처: feature-security-operational-baseline L93 — "public path misconfiguration ... | 500 + P1 alert | INTERNAL_AUTH_MISCONFIGURATION | INTERNAL"
# source: 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
# 출처: feature-container-runtime-contract L113 — "JVM OutOfMemoryError → ExitOnOutOfMemoryError로 137 exit, log에 error.code=JVM_OOM 명시"
# source: feature-container-runtime-contract L113 — "JVM OutOfMemoryError → ExitOnOutOfMemoryError로 137 exit, log에 error.code=JVM_OOM 명시"
- code: JVM_OOM
category: INTERNAL
http_status: 500
@@ -220,7 +220,7 @@ errors:
# DB / 영속성 (feature-persistence-failure-baseline / SQLState Matrix)
# ============================================================
# 출처: feature-persistence-failure-baseline L85 — "08* | all | TRANSIENT_DEPENDENCY | DB_UNAVAILABLE | true"
# source: 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
# 출처: feature-persistence-failure-baseline L86 — "40001 | Postgres/MySQL | CONFLICT | DB_SERIALIZATION_FAILURE | true"
# source: 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
# 출처: feature-persistence-failure-baseline L87 — "40P01 | Postgres | CONFLICT | DB_DEADLOCK | true (backoff)"
# source: 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
# 출처: feature-persistence-failure-baseline L88 — "23502 | Postgres | DATA_INTEGRITY | DB_NULL_VIOLATION | false"
# source: 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
# 출처: feature-persistence-failure-baseline L89 — "23503 | Postgres | DATA_INTEGRITY | DB_FK_VIOLATION | false"
# source: 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
# 출처: feature-persistence-failure-baseline L90 — "23505 | Postgres | CONFLICT | DB_UNIQUE_VIOLATION | false (business mapping)"
# source: 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
# 출처: feature-persistence-failure-baseline L91 — "23514 | Postgres | DATA_INTEGRITY | DB_CHECK_VIOLATION | false"
# source: 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
# 출처: feature-persistence-failure-baseline L92 — "25P03 | Postgres | TRANSIENT_DEPENDENCY | DB_IDLE_IN_TX_TIMEOUT | true"
# source: 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
# 출처: feature-persistence-failure-baseline L93 — "57014 | Postgres | TRANSIENT_DEPENDENCY | DB_QUERY_CANCELED | false"
# source: 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
# 출처: review-followup P15 (S2-lead-4) — JPA OPTIMISTIC_CONFLICT (flush·commit 때 @Version 검사 실패)
# source: 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
# 출처: review-followup P15 (S2-lead-4) — JPA COMPLETION_UNKNOWN (40003 / commit 단계 연결 끊김)
# source: 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)
# ============================================================
# 출처: feature-rate-limit-idempotency-contract — rate limit 응답·로그 기준 / Retry-After 헤더 기준 (scope L29, L33)
# source: 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
# 출처: docs/web/http-contract.md §2 (2026-11-01 소유자 결정, 리뷰 02-01 대안 A) — 결과 불명. 같은 Idempotency-Key로 Retry-After 뒤 재전송. 새 키 금지.
# source: 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
# 출처: feature-rate-limit-idempotency-contract L72 — "fingerprint mismatch (same key + different body) = 422 IDEMPOTENT_REQUEST_MISMATCH"
# source: 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
# 출처: review-followup P15 (X2-P2-2a) — IdempotencyExecutor가 동작 전에 닫힌 채 거절한다(fail-closed)
# source: 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
# 출처: 재리뷰 2026-11-03 README 4절 결정, RR-02-03 — action이 돈 뒤 complete 단계에서 저장소가 응답하지 않음.
# source: 재리뷰 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
# 출처: review-followup P15 (X2-P2-2a) — replay가 외부 효과가 일어났는지 정할 수 없다
# source: review-followup P15 (X2-P2-2a) — replay가 외부 효과가 일어났는지 정할 수 없다
- code: IDEMPOTENCY_RECOVERY_REQUIRED
category: DATA_INTEGRITY
http_status: 500
@@ -455,7 +455,7 @@ errors:
# 파일 / 자원 (feature-file-resource-handling-contract)
# ============================================================
# 출처: feature-file-resource-handling-contract L69 — "spring.servlet.multipart.max-file-size 10MB ... Spring 단의 enforcement가 실패 시 envelope 응답 보장" / 테스트 계약 "oversized upload가 generic 500으로 처리되면 실패"
# source: feature-file-resource-handling-contract L69 — "spring.servlet.multipart.max-file-size 10MB ... Spring 단의 enforcement가 실패 시 envelope 응답 보장" / 테스트 계약 "oversized upload가 generic 500으로 처리되면 실패"
# ============================================================
# API 계약의 전송 표준 코드 (feature-api-contract-baseline)
# ============================================================
@@ -464,7 +464,7 @@ errors:
# 그대로 옮긴 것이다. D11 상태 대응 일관성 테스트(소유: 이 branch, 생산자)가 코드의 레지스트리 http_status와
# enum httpStatus()가 어긋나면 빌드를 실패시킨다.
# 출처: feature-api-contract-baseline.md D12 — "405 Method Not Allowed + Allow header 의무"
# source: feature-api-contract-baseline.md D12 — "405 Method Not Allowed + Allow header 의무"
- code: METHOD_NOT_ALLOWED
category: VALIDATION
http_status: 405
@@ -477,7 +477,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:api-contract-status-mapping
# 출처: feature-api-contract-baseline.md D9 — "406 Not Acceptable = 응답 표현 협상 실패"
# source: feature-api-contract-baseline.md D9 — "406 Not Acceptable = 응답 표현 협상 실패"
- code: NOT_ACCEPTABLE
category: VALIDATION
http_status: 406
@@ -490,7 +490,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:api-contract-status-mapping
# 출처: feature-api-contract-baseline.md D15 — "If-Match mismatch 시 412 Precondition Failed"
# source: feature-api-contract-baseline.md D15 — "If-Match mismatch 시 412 Precondition Failed"
- code: PRECONDITION_FAILED
category: CONFLICT
http_status: 412
@@ -503,7 +503,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:api-contract-status-mapping
# 출처: feature-api-contract-baseline.md D8 — "request size limit 실패 분류 (413)"
# source: feature-api-contract-baseline.md D8 — "request size limit 실패 분류 (413)"
- code: PAYLOAD_TOO_LARGE
category: VALIDATION
http_status: 413
@@ -516,7 +516,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:api-contract-status-mapping
# 출처: feature-api-contract-baseline.md D8 형제 — "URI 길이 실패 분류 (414)"
# source: feature-api-contract-baseline.md D8 형제 — "URI 길이 실패 분류 (414)"
# 참고: 강제는 Tomcat·gateway가 한다(Spring dispatch 전에 거절). 이 행과 코드는 상태 대응 일관성을 위해
# 있다. 끝에서 끝까지의 414 계약 테스트는 `planned`다 (gateway/Tomcat maxHttpHeaderSize 8KB 경계).
- code: URI_TOO_LONG
@@ -531,7 +531,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:api-contract-status-mapping
# 출처: feature-api-contract-baseline.md D9 — "415 Unsupported Media Type = 요청 본문 format 미지원"
# source: feature-api-contract-baseline.md D9 — "415 Unsupported Media Type = 요청 본문 format 미지원"
- code: UNSUPPORTED_MEDIA_TYPE
category: VALIDATION
http_status: 415
@@ -548,7 +548,7 @@ errors:
# Tenant (feature-tenant-context-policy)
# ============================================================
# 출처: feature-tenant-context-policy L71 — "tenant 미지원 모드에서 X-Tenant-Id 헤더 수신 시 400 TENANT_NOT_SUPPORTED (filter 단계)"
# source: feature-tenant-context-policy L71 — "tenant 미지원 모드에서 X-Tenant-Id 헤더 수신 시 400 TENANT_NOT_SUPPORTED (filter 단계)"
# ============================================================
# Validation / Business rule (feature-business-rule-validation-contract)
# ============================================================
@@ -558,17 +558,17 @@ errors:
# (feature-operational-error-observability-foundation L110). 실제 도메인별 code는
# Phase D(도메인 feature 적용) 시 본 registry에 추가.
# 출처: feature-operational-error-observability-foundation L110 — "code: VALIDATION_EMAIL_FORMAT, // registry-registered code" (validation 필드 오류 JSON 모양 예)
# source: feature-operational-error-observability-foundation L110 — "code: VALIDATION_EMAIL_FORMAT, // registry-registered code" (validation 필드 오류 JSON 모양 예)
# ============================================================
# 캐시 (feature-cache-consistency-contract)
# ============================================================
# 출처: 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로 처리되면 실패"
# 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로 처리되면 실패"
# ============================================================
# 외부 HTTP 호출 (feature-outbound-http-client-baseline)
# ============================================================
# 출처: 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로 분류되어야 함"
# 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로 분류되어야 함"
- code: DEPENDENCY_TIMEOUT
category: TRANSIENT_DEPENDENCY
http_status: 504
@@ -581,7 +581,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:outbound-http
# 출처: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류" + L70 connect=2s timeout
# source: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류" + L70 connect=2s timeout
- code: DEPENDENCY_CONNECT_FAILED
category: TRANSIENT_DEPENDENCY
http_status: 503
@@ -594,7 +594,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:outbound-http
# 출처: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류"
# source: feature-outbound-http-client-baseline — scope "timeout/connect/DNS failure 분류"
- code: DEPENDENCY_DNS_FAILED
category: TRANSIENT_DEPENDENCY
http_status: 503
@@ -607,7 +607,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:outbound-http
# 출처: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류" / 테스트 "401/403은 credential/scope/config 문제로 분류되어야 함"
# source: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류" / 테스트 "401/403은 credential/scope/config 문제로 분류되어야 함"
- code: DEPENDENCY_4XX_CLIENT
category: PERMANENT_DEPENDENCY
http_status: 502
@@ -620,7 +620,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:outbound-http
# 출처: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류"
# source: feature-outbound-http-client-baseline — scope "upstream 4xx/5xx 분류"
- code: DEPENDENCY_5XX_SERVER
category: TRANSIENT_DEPENDENCY
http_status: 502
@@ -633,7 +633,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:outbound-http
# 출처: feature-outbound-http-client-baseline L69 — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용" + Decisionized "circuit breaker | Resilience4j optional env"
# source: 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
@@ -650,7 +650,7 @@ errors:
# Outbox (feature-domain-event-outbox-contract)
# ============================================================
# 출처: feature-domain-event-outbox-contract L67 — "outbox row status enum = PENDING / IN_FLIGHT / PUBLISHED / FAILED / DEAD" + scope "publish 실패 분류" / 판정 "publish 실패가 retry/DLQ/log/runbook 기준 없이 삼켜지면 실패"
# source: 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
@@ -663,7 +663,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:outbox-publish
# 출처: feature-domain-event-outbox-contract L67 — outbox status enum "DEAD" / Outbox Defaults "DLQ | background-job branch owner"
# source: 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
@@ -680,7 +680,7 @@ errors:
# 백그라운드 작업 / 비동기 (feature-background-job-async-contract)
# ============================================================
# 출처: feature-background-job-async-contract — Decisionized "saturation | bounded executor + rejection log" / L72 "saturation policy default = AbortPolicy" / 테스트 "executor rejection이 structured log 없이 발생하면 실패"
# source: 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
@@ -693,7 +693,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:async-saturation
# 출처: 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
# 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
- code: JOB_TIMEOUT
category: TRANSIENT_DEPENDENCY
http_status: 500
@@ -706,7 +706,7 @@ errors:
compatibility_impact: none
required_test: contract-verification:async-timeout
# 출처: feature-background-job-async-contract L69 — "DLQ after exhausted attempts" + Decisionized "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted | ... | infinite retry"
# source: 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
@@ -723,7 +723,7 @@ errors:
# 분산 lock (feature-distributed-lock-contract)
# ============================================================
# 출처: feature-distributed-lock-contract D7 — "lock 획득 실패/timeout 의 error code =
# source: 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 — 락 보유자가 임계 구역을 빠져나오면
@@ -747,7 +747,7 @@ errors:
# Migration / 기동 (feature-migration-startup-contract)
# ============================================================
# 출처: feature-migration-startup-contract L71 — "startup exit code 표준 = ... migration 실패=70 ..." + Decisionized "startup failure log | structured log with startup.phase, error.code, error.category"
# source: 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
@@ -760,12 +760,12 @@ errors:
compatibility_impact: none
required_test: adapter-contract:adapter-disabled-runtime-call
# 출처: feature-migration-startup-contract L71 — "startup exit code 표준 = ... profile mismatch=71" / 테스트 "prod profile에서 local-only 설정이 켜지면 실패"
# source: feature-migration-startup-contract L71 — "startup exit code 표준 = ... profile mismatch=71" / 테스트 "prod profile에서 local-only 설정이 켜지면 실패"
# ============================================================
# 관리 포트 / Actuator (feature-management-actuator-security-contract)
# ============================================================
# 출처: feature-management-actuator-security-contract — 노출 정책 "env/configprops | forbidden" "heapdump/threaddump | forbidden unless break-glass runbook" "shutdown | forbidden" / 테스트 "prod에서 env/configprops endpoint가 노출되면 실패"
# source: feature-management-actuator-security-contract — Exposure Policy "env/configprops | forbidden" "heapdump/threaddump | forbidden unless break-glass runbook" "shutdown | forbidden" / 테스트 "prod에서 env/configprops endpoint가 노출되면 실패"
- code: ACTUATOR_FORBIDDEN
category: AUTHZ
http_status: 403
+13 -13
View File
@@ -9,7 +9,7 @@
# - envelope_meta_field: camelCase (envelope이 정본)
headers:
# 출처: feature-operational-error-observability-foundation.md L97
# source: 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
# 출처: feature-api-contract-baseline.md L77 / feature-rate-limit-idempotency-contract.md L66-67
# source: 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
# 출처: feature-rate-limit-idempotency-contract.md L85 / foundation L85
# source: 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
# 출처: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준)
# source: 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
# 출처: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준)
# source: 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
# 출처: feature-rate-limit-idempotency-contract.md scope L26 (rate limit response/log 기준)
# source: 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
# 출처: feature-api-compatibility-deprecation-contract.md L87
# source: 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
# 출처: feature-api-compatibility-deprecation-contract.md L87
# source: 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
# 출처: feature-distributed-tracing-contract.md L64, L85
# source: 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
# 출처: feature-distributed-tracing-contract.md L66, L85
# source: 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
# 출처: feature-operational-error-observability-foundation.md L100
# source: 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,7 +161,7 @@ headers:
compatibility_impact: none
required_test: contract-verification:envelope-headers
# 출처: feature-security-operational-baseline.md L66
# source: feature-security-operational-baseline.md L66
# "JWT Resource Server를 baseline security model로 둠" (Authorization 헤더의 Bearer 토큰)
- name: Authorization
direction: inbound
@@ -175,7 +175,7 @@ headers:
compatibility_impact: none
required_test: contract-verification:jwt-resource-server
# 출처: feature-security-operational-baseline.md L83-90 (AuthN/AuthZ 판정 표)
# source: feature-security-operational-baseline.md L83-90 (AuthN/AuthZ Decision Matrix)
# 401 응답 시 WWW-Authenticate (Bearer realm/error) — Spring Security JWT Resource Server의 표준 challenge 헤더
- name: WWW-Authenticate
direction: outbound
+19 -19
View File
@@ -9,7 +9,7 @@
# - foundation L93-102 표 "MDC Key Standard (final)"의 key들이 핵심 정본이다
mdc_keys:
# 출처: feature-operational-error-observability-foundation.md L97
# source: 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
# 출처: feature-operational-error-observability-foundation.md L98
# source: 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
# 출처: feature-operational-error-observability-foundation.md L99
# source: 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
# 출처: feature-operational-error-observability-foundation.md L100
# source: 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
# 출처: feature-operational-error-observability-foundation.md L101 + feature-tenant-context-policy.md L70
# source: 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
# 출처: feature-operational-error-observability-foundation.md L102
# source: feature-operational-error-observability-foundation.md L102
# "user_principal | security context (pseudonymized only) | log only, headers forbidden"
- key: user_principal
type: string
@@ -104,7 +104,7 @@ mdc_keys:
# ── 로그 종류별 확장 (log-management-contract L101-109 "Log Type별 필수 필드") ──
# 출처: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms"
# source: 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
@@ -119,7 +119,7 @@ mdc_keys:
compatibility_impact: none
required_test: contract-verification:log-fields
# 출처: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms"
# source: 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,7 +133,7 @@ mdc_keys:
compatibility_impact: none
required_test: contract-verification:log-fields
# 출처: feature-log-management-contract.md L105 "request | request_id, trace_id, method, uri_template, status, duration_ms"
# source: 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
@@ -148,7 +148,7 @@ mdc_keys:
compatibility_impact: none
required_test: contract-verification:log-fields
# 출처: feature-log-management-contract.md L105-106 "request | ... duration_ms" / "dependency | ... duration_ms"
# source: feature-log-management-contract.md L105-106 "request | ... duration_ms" / "dependency | ... duration_ms"
- key: duration_ms
type: numeric
source: application_set
@@ -162,7 +162,7 @@ mdc_keys:
compatibility_impact: none
required_test: contract-verification:log-fields
# 출처: feature-log-management-contract.md L106 "dependency | dependency_name, dependency_type, duration_ms, outcome, error_code"
# source: 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
@@ -177,7 +177,7 @@ mdc_keys:
compatibility_impact: none
required_test: contract-verification:log-fields
# 출처: feature-log-management-contract.md L106 "dependency | dependency_name, dependency_type, ..."
# source: 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
# 출처: feature-log-management-contract.md L106 + metrics L91 "outcome (resilience4j) | 5 (SUCCESS/FAILURE/CIRCUIT_OPEN/TIMEOUT/REJECTED)"
# source: 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,7 +205,7 @@ mdc_keys:
compatibility_impact: none
required_test: contract-verification:log-fields
# 출처: feature-log-management-contract.md L106 "dependency | ... error_code (실패 시)"
# source: feature-log-management-contract.md L106 "dependency | ... error_code (실패 시)"
# 참고: metrics L89 "error_code | 100 — error registry row 상한과 정합" — 값 개수가 정해져 있다
- key: error_code
type: string
@@ -220,7 +220,7 @@ mdc_keys:
compatibility_impact: none
required_test: contract-verification:log-fields
# 출처: feature-log-management-contract.md L107
# source: 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
# 출처: feature-log-management-contract.md L107 "security | ... source_ip (anonymized — last octet zeroed)"
# source: 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
# 출처: feature-log-management-contract.md L108 "audit | actor, action, target, before_hash, after_hash, occurred_at"
# source: 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
# 출처: feature-log-management-contract.md L108 "audit | actor, action, target, ..."
# source: 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
# 출처: feature-log-management-contract.md L108 "audit | actor, action, target, ..."
# source: feature-log-management-contract.md L108 "audit | actor, action, target, ..."
- key: target
type: string
source: application_set
+35 -35
View File
@@ -16,7 +16,7 @@
metrics:
# === HTTP 서버 (inbound) ===
# 출처: feature-metrics-alerting-contract — Metric/Alert Defaults
# source: 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
@@ -42,7 +42,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-metrics-alerting-contract — P1/P2/P3 정량 기준 (HTTP latency p99)
# source: 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
@@ -66,9 +66,9 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === HTTP client (outbound 의존 대상) ===
# 출처: feature-metrics-alerting-contract — Metric/Alert Defaults
# source: feature-metrics-alerting-contract — Metric/Alert Defaults
# "dependency metric | dependency.client.requests with dependency.name/type/outcome | endpoint with secret tag"
# 출처: feature-outbound-http-client-baseline — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용"
# source: feature-outbound-http-client-baseline — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용"
- name: dependency.client.requests
type: timer
unit: seconds
@@ -92,9 +92,9 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-outbound-http-client-baseline — 결정
# source: feature-outbound-http-client-baseline — decisions
# "retry/circuit breaker 기본 라이브러리는 Resilience4j"
# 출처: feature-metrics-alerting-contract — "retry/CB minimum: resilience4j.retry.calls{outcome}"
# source: feature-metrics-alerting-contract — "retry/CB minimum: resilience4j.retry.calls{outcome}"
- name: resilience4j.retry.calls
type: counter
unit: total
@@ -113,7 +113,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.state"
# source: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.state"
- name: resilience4j.circuitbreaker.state
type: gauge
unit: total
@@ -133,7 +133,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.calls{outcome}"
# source: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.calls{outcome}"
- name: resilience4j.circuitbreaker.calls
type: timer
unit: seconds
@@ -153,9 +153,9 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === DB connection pool ===
# 출처: feature-persistence-failure-baseline — Hikari Alert Threshold
# source: feature-persistence-failure-baseline — Hikari Alert Threshold
# "pool wait p99 > 100ms 5분 지속 → P2 / pool exhaustion (active = max) > 1분 → P1"
# 출처: feature-metrics-alerting-contract — "hikaricp.connections.acquire{outcome='timeout'} p99 > 100ms"
# source: feature-metrics-alerting-contract — "hikaricp.connections.acquire{outcome='timeout'} p99 > 100ms"
- name: hikaricp.connections.acquire
type: timer
unit: seconds
@@ -175,7 +175,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-persistence-failure-baseline — 범위 안 "Hikari metric 노출 기준" + Hikari Alert Threshold
# source: feature-persistence-failure-baseline — In scope "Hikari metric 노출 기준" + Hikari Alert Threshold
- name: hikaricp.connections.usage
type: timer
unit: seconds
@@ -191,7 +191,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-persistence-failure-baseline — 범위 안 "Hikari metric 노출 기준"
# source: feature-persistence-failure-baseline — In scope "Hikari metric 노출 기준"
- name: hikaricp.connections.active
type: gauge
unit: total
@@ -207,7 +207,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-metrics-alerting-contract — Histogram Buckets/Percentile "DB query: same"
# source: feature-metrics-alerting-contract — Histogram Buckets/Percentile "DB query: same"
- name: db.query.duration
type: timer
unit: seconds
@@ -228,7 +228,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === 백그라운드 작업 / 비동기 executor ===
# 출처: feature-background-job-async-contract — Decisionized Work Items "saturation policy"
# source: feature-background-job-async-contract — Decisionized Work Items "saturation policy"
# "AbortPolicy default (core=10, max=50, queue=200)"
- name: executor.saturation
type: gauge
@@ -246,7 +246,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-background-job-async-contract — 결정한 작업 항목 "saturation | bounded executor + rejection log"
# source: feature-background-job-async-contract — Decisionized Work Items "saturation | bounded executor + rejection log"
- name: executor.rejected.total
type: counter
unit: total
@@ -265,7 +265,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-background-job-async-contract — 결정한 작업 항목 "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted"
# source: feature-background-job-async-contract — Decisionized Work Items "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted"
- name: job.retry.total
type: counter
unit: total
@@ -284,7 +284,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-background-job-async-contract — "DLQ after exhausted attempts"
# source: feature-background-job-async-contract — "DLQ after exhausted attempts"
- name: job.dlq.total
type: counter
unit: total
@@ -301,7 +301,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === Distributed lock ===
# 출처: feature-distributed-lock-contract D7 — "metric lock.acquisition (tag: outcome =
# source: 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.
@@ -321,7 +321,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-distributed-lock-contract §Edge / D5 (SI-LOCK-C5) — "lease 만료 후 unlock →
# source: feature-distributed-lock-contract §Edge / D5 (SI-LOCK-C5) — "lease 만료 후 unlock →
# ConcurrentModificationException — 삼킴 금지, 로그+metric 후 정상 흐름 복귀". lease가 이미 만료된 뒤의
# 해제를 센다(보유자가 close()를 부르기 전에 다른 인스턴스가 JdbcLock 행을 회수함). 0이 아닌 비율이
# 이어지면 lease TTL이 실제 임계 구역 시간보다 짧다는 뜻이다 — APP/lease TTL을 늘리거나 보호하는 일을
@@ -340,7 +340,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === Outbox 발행기 ===
# 출처: feature-domain-event-outbox-contract — Outbox Defaults
# source: 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
@@ -363,7 +363,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-domain-event-outbox-contract — 행 상태 enum PENDING/IN_FLIGHT/PUBLISHED/FAILED/DEAD
# source: feature-domain-event-outbox-contract — 행 상태 enum PENDING/IN_FLIGHT/PUBLISHED/FAILED/DEAD
- name: outbox.publisher.lag
type: gauge
unit: seconds
@@ -380,7 +380,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-domain-event-outbox-contract — row status enum + Outbox Defaults attemptCount
# source: 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
@@ -401,7 +401,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: re-review 2026-11-03 RR-05-03 — 지금의 거절과 답이 없는 발행은 끝없이 재시도된다. 이 둘은
# source: 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
@@ -431,7 +431,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === 캐시 ===
# 출처: feature-cache-consistency-contract — Decisionized Work Items "cache pattern | cache-aside default"
# source: feature-cache-consistency-contract — Decisionized Work Items "cache pattern | cache-aside default"
- name: cache.gets.total
type: counter
unit: total
@@ -450,7 +450,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-cache-consistency-contract — "invalidation = after-commit only", "invalidation 실패가 조용히 무시되면 실패"
# source: feature-cache-consistency-contract — "invalidation = after-commit only", "invalidation 실패가 조용히 무시되면 실패"
- name: cache.invalidations.total
type: counter
unit: total
@@ -469,7 +469,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: redis-production-capability — 크기가 정해진 캐시 전용 L1 (선택)
# source: redis-production-capability — 크기가 정해진 캐시 전용 L1 (선택)
- name: cache.local.requests.total
type: counter
unit: total
@@ -488,7 +488,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: redis-production-capability — 로컬 stale 나이 상한
# source: redis-production-capability — 로컬 stale 나이 상한
- name: cache.local.entry.age.seconds
type: timer
unit: seconds
@@ -504,7 +504,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: redis-production-capability — 크기가 정해진 무효화와 세대 대조(reconciliation)
# source: redis-production-capability — 크기가 정해진 무효화와 세대 대조(reconciliation)
- name: cache.local.maintenance.total
type: counter
unit: total
@@ -538,7 +538,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === Redis 연결 lane ===
# 출처: review 2026-11-03 RR-04-02 — 캐시의 조건부 쓰기는 자기 lane(CACHE_SCRIPT)을 받았다. 캐시 채우기가
# source: 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으로 등록한다.
@@ -659,7 +659,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === 로그 appender ===
# 출처: feature-log-management-contract — Sampling Policy (final)
# source: 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
@@ -680,7 +680,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === 분산 추적 ===
# 출처: feature-distributed-tracing-contract — decisions
# source: 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
@@ -699,7 +699,7 @@ metrics:
required_test: contract-verification:metrics-cardinality
# === JVM 기본 ===
# 출처: feature-metrics-alerting-contract — In scope "JVM/process metric"
# source: feature-metrics-alerting-contract — In scope "JVM/process metric"
- name: jvm.memory.used
type: gauge
unit: bytes
@@ -718,7 +718,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-metrics-alerting-contract — 범위 안 \"JVM/process metric\"
# source: feature-metrics-alerting-contract — In scope "JVM/process metric"
- name: jvm.gc.pause
type: timer
unit: seconds
@@ -736,7 +736,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-metrics-alerting-contract — 범위 안 \"JVM/process metric\"
# source: feature-metrics-alerting-contract — In scope "JVM/process metric"
- name: jvm.threads.live
type: gauge
unit: total
@@ -750,7 +750,7 @@ metrics:
compatibility_impact: additive
required_test: contract-verification:metrics-cardinality
# 출처: feature-metrics-alerting-contract — 범위 안 \"JVM/process metric\" (process uptime)
# source: feature-metrics-alerting-contract — In scope "JVM/process metric" (process uptime)
- name: process.uptime
type: gauge
unit: seconds
+13 -13
View File
@@ -26,7 +26,7 @@ secrets:
# === 3등급: secret (진짜 비밀 — password/private-key/HMAC-salt) ===
- name: APP_DATASOURCE_PASSWORD
# 출처: feature-secrets-config-source-contract 2026-05-22
# source: feature-secrets-config-source-contract 2026-05-22
# "DB credential은 dual-bind 60s" + "__LOCAL_DEV_FAKE_DB_PASSWORD" 예시
classification: secret
source: secret-manager
@@ -42,7 +42,7 @@ secrets:
required_test: secrets-contract:db-password-no-leak-in-actuator
- name: SPRING_MAIL_PASSWORD
# 출처: notification/fileserver techlead review H2 — Spring Mail이 직접 읽는 자격 증명이라 APP_* 별칭을 두지
# source: notification/fileserver techlead review H2 — Spring Mail이 직접 읽는 자격 증명이라 APP_* 별칭을 두지
# 않고 일부러 SPRING_* 이름을 유지한다.
classification: secret
source: secret-manager
@@ -56,7 +56,7 @@ secrets:
required_test: secrets-contract:smtp-password-no-leak
- name: APP_CACHE_REDIS_PASSWORD
# 출처: feature-secrets-config-source-contract 2026-05-22
# source: feature-secrets-config-source-contract 2026-05-22
# 3등급 분류 "secret" + feature-integration-adapter-templates "Redis | disabled optional module"
# (Redis를 켜고 인증을 쓰면 secret으로 분류)
classification: secret
@@ -206,7 +206,7 @@ secrets:
required_test: secrets-contract:lease-redis-key-hmac-no-leak
- name: APP_PRIVACY_PSEUDONYMIZATION_SALT
# 출처: feature-data-retention-privacy-contract 2026-05-22
# source: 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"
@@ -328,7 +328,7 @@ secrets:
required_test: secrets-contract:notification-callback-fingerprint-hmac-no-leak
- name: APP_NOTIFICATION_SLACK_WEBHOOK_URL
# 출처: feature-integration-adapter-templates 2026-05-22
# source: 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
@@ -342,7 +342,7 @@ secrets:
required_test: secrets-contract:slack-webhook-no-leak
- name: APP_SECURITY_GOOGLE_OAUTH_CLIENT_ID
# 출처: feature-secrets-config-source-contract 2026-05-22
# source: feature-secrets-config-source-contract 2026-05-22
# "sensitive-config" 등급 (id이지만 노출 제한)
# + feature-integration-adapter-templates "Google Email | disabled optional module"
classification: sensitive-config
@@ -356,7 +356,7 @@ secrets:
required_test: secrets-contract:google-oauth-client-id-masked
- name: APP_DATASOURCE_USERNAME
# 출처: feature-secrets-config-source-contract 2026-05-22 — "sensitive-config" 등급
# source: feature-secrets-config-source-contract 2026-05-22 — "sensitive-config" 등급
# (DB user는 password와 함께 노출되면 위험하므로 sensitive-config)
classification: sensitive-config
source: mounted-env
@@ -382,7 +382,7 @@ secrets:
required_test: secrets-contract:mongodb-uri-masked
- name: APP_DATASOURCE_URL
# 출처: feature-secrets-config-source-contract 2026-05-22 — JDBC URL은 host/db 포함하므로 sensitive-config
# source: 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
@@ -397,7 +397,7 @@ secrets:
# === 1등급: public-config (참조만 — 행 전체는 env-keys.yaml에 있다) ===
- name: APP_PROFILE
# 출처: feature-env-driven-runtime-configuration — public-config 등급 참조
# source: feature-env-driven-runtime-configuration — public-config 등급 참조
classification: public-config
source: application-yml
owner_branch: feature-env-driven-runtime-configuration
@@ -405,7 +405,7 @@ secrets:
reference: env-keys.yaml#APP_PROFILE
- name: APP_NAME
# 출처: feature-env-driven-runtime-configuration — public-config 등급 참조
# source: feature-env-driven-runtime-configuration — public-config 등급 참조
classification: public-config
source: application-yml
owner_branch: feature-env-driven-runtime-configuration
@@ -413,7 +413,7 @@ secrets:
reference: env-keys.yaml#APP_NAME
- name: SERVER_PORT
# 출처: feature-env-driven-runtime-configuration — Spring 자체 키, public-config 등급 참조
# source: feature-env-driven-runtime-configuration — Spring 자체 키, public-config 등급 참조
classification: public-config
source: application-yml
owner_branch: feature-env-driven-runtime-configuration
@@ -421,7 +421,7 @@ secrets:
reference: env-keys.yaml#SERVER_PORT
- name: SPRING_PROFILES_ACTIVE
# 출처: feature-env-driven-runtime-configuration — Spring 자체 키, public-config 등급 참조
# source: feature-env-driven-runtime-configuration — Spring 자체 키, public-config 등급 참조
classification: public-config
source: application-yml
owner_branch: feature-env-driven-runtime-configuration
@@ -429,7 +429,7 @@ secrets:
reference: env-keys.yaml#SPRING_PROFILES_ACTIVE
- name: OTEL_EXPORTER_OTLP_ENDPOINT
# 출처: feature-distributed-tracing-contract — public-config 등급 참조
# source: feature-distributed-tracing-contract — public-config 등급 참조
classification: public-config
source: application-yml
owner_branch: feature-distributed-tracing-contract