DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
56 lines
2.4 KiB
Markdown
56 lines
2.4 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: grpc-codegen-c01
|
|
title: 손으로 적은 요구 목록은 갱신이 멈추는 쪽이다
|
|
topic: state-machines-and-ownership
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:grpc-codegen-c01
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: grpc-codegen-c01
|
|
file: ../../../final/evidence/rendered/grpc-codegen-c01.svg
|
|
- key: grpc-codegen-c01-diagram
|
|
file: ../../../final/assets/diagrams/grpc-codegen-c01.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/grpc-codegen-c01.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/grpc/grpc-codegen.md#L104 이다.
|
|
module: grpc-codegen
|
|
---
|
|
|
|
# 손으로 적은 요구 목록은 갱신이 멈추는 쪽이다
|
|
|
|
`GrpcConsumerFixture.fromJavaSource`가 릴리스된 소비자의 자바 소스에서 요구 사항 셋을 기계적으로 유도한다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
`GrpcConsumerFixture.fromJavaSource` 가 릴리스된 소비자의 자바 소스에서 요구 사항 셋을 기계적으로 유도한다.
|
|
|
|
> "a hand-written requirement list is a second copy of what the client already says and the copy is the one that stops being updated."
|
|
|
|
## 소비자 소스에서 유도하는 셋
|
|
|
|
:::evidence key="grpc-codegen-c01-diagram" alt="소비자 자바 소스에서 생성 패키지와 서비스 경로와 메서드 경로 세 상자로 화살표가 나가고 화살표마다 유도 규칙이 붙은 구조" caption="소비자 소스에서 유도하는 셋" zoom="false"
|
|
:::
|
|
|
|
```text
|
|
생성 자바 패키지 = fixture 클래스가 import 하는 패키지 중 접미가 맞는 것
|
|
서비스 = <Name>Grpc import → <proto package>.<Name>
|
|
메서드 = stub.<name>( 호출 → <service>/<UpperCamelName>
|
|
```
|
|
|
|
## GrpcConsumerFixture 참조 위치
|
|
|
|
:::evidence key="grpc-codegen-c01" alt="코드베이스에서 GrpcConsumerFixture 를 검색한 출력 26줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="GrpcConsumerFixture 코드베이스 검색 — 26줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
## 근사라는 것과 보고를 합치지 않는다는 것
|
|
|
|
그것이 컴파일의 근사라는 것과, 근사인 이유(ADR-GRPC-002)를 함께 적는다. `breaksAgainst` 는 세 종류를 따로 보고한다 — 서비스 경로, 메서드 경로, 자바 패키지. 하나의 개수로 합치지 않는다.
|
|
|
|
<!-- body:end -->
|