DongHyeonkaandClaude Opus 5
95c0e680b5
The skill says drawings carry names and sentences go in <desc> and the paragraph beside the figure. I put sentences in node details and edge labels instead, and 27 of the 28 diagrams shipped with prose inside the canvas — "예측 다섯 개가 틀렸다", "아홉 번 조용히 실패했다", "막혀서 닿지 않는다". Only label and details render on the canvas; description does not. So every sentence moved to a noun phrase and the meaning stays in description, which was already carrying it. 막혀서 닿지 않는다 -> 차단 아홉 번 조용히 실패했다 -> 조용한 실패 9건 예측 다섯 개가 틀렸다 -> 틀린 예측 5건 로그아웃이 정리하지 않는다 -> 로그아웃 미정리 볼륨이 없으면 여기까지다 -> 볼륨 없음 Three node labels were sentences too and became names: 세션 스냅샷, 예측 선기록, 대조군 확보. What stays is what the rules protect — identifiers, commands and measured values: PRIMARY KEY (client_registration_id, principal_name), ValidationFailedException: 1 changesets check sum, nginx -t && nginx -s reload, SET LOCAL synchronous_commit TO OFF. Those are names of things, not prose about them. 294 canvas strings across 28 diagrams, none matching a sentence ending, average 11 characters. All 28 still lint clean and re-rendered. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 lines
442 B
Plaintext
13 lines
442 B
Plaintext
%% 캐시 온도가 결과를 가른다
|
|
%% question: volatile 에서 DB 를 세우면 로그인과 refresh 는 어떻게 되는가
|
|
flowchart TB
|
|
n0(["로그인 · refresh 요청"])
|
|
n1["CLIENT 조회"]
|
|
n2["CLIENT_SCOPE_CLIENT 조회"]
|
|
n3[("PostgreSQL")]
|
|
n0 -->|"클라이언트 확인"| n1
|
|
n1 -->|"스코프 재계산"| n2
|
|
n2 -->|"캐시 미스"| n3
|
|
classDef external stroke-dasharray: 6 4
|
|
class n0 external
|