DongHyeonkaandClaude Opus 5
75bed382c8
The originating repository's SVGs were drawn by hand and every one of them
put a title, a subtitle and an explanation band inside the canvas. This
repository forbids both, so they could not be carried over — the whole set
was rebuilt through the skill's pipeline instead.
Each diagram went through prepare, references, prompt, a VizSpec 1.1 citing
document line ranges, lint, and render. All 28 pass lint and produce the
same eight formats the existing keycloak project has. Sentences moved out of
the canvas into <desc> and the paragraph beside each figure; the drawings
carry names only.
Two lint rules did real work rather than formatting work:
edge-through-node caught arrows crossing an unrelated
node and implying an adjacency that
does not exist — four diagrams had to
be restructured, not just relaid out
evidence-outside-prepared-context caught a diagram citing another
section; its anchor moved from B-0 to
B-1 so all three sections it draws on
are inside the prepared context
lab-topology also had to change profile: its context offers a different
candidate set, and query-fanout with shard roles is what the section
actually shows — one entry point spreading to two Keycloak nodes.
The document now carries all 28 inline, one per claim that needed one, and
the section recording what was still missing is updated: the diagram gap is
closed, Studio records remain.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
21 lines
1.3 KiB
Markdown
21 lines
1.3 KiB
Markdown
# 주입이 걸렸는지 따로 확인한다
|
||
|
||
## Alternative text
|
||
|
||
주입 명령에서 대상 상태 확인을 거쳐 결과 관측으로 가는 경로. 상태 확인을 건너뛰면 두 가지 다른 상황이 같은 관측으로 보인다.
|
||
|
||
## Long description
|
||
|
||
이 실험대에서 아홉 번의 주입이 조용히 실패했다. conntrack 이 ESTABLISHED 연결을 통과시키고, kubectl delete --force 가 크래시가 아니며, PID 1 이 SIGKILL 을 무시하고, kube-router 가 iptables 체인을 다시 끼워 넣는다. 모두 아무 일도 없었다로 보였다. 그래서 주입 뒤에는 결과를 보기 전에 대상이 실제로 그 상태인지를 cluster_size, 워커 PID, conntrack 표, 패킷 카운터로 확인한다.
|
||
|
||
## Elements and evidence
|
||
|
||
- **주입 명령** (process): NetworkPolicy · tc · kill · iptables. Evidence: L109–L112.
|
||
- **대상 상태 확인** (process): 결과가 아니라 대상이 그 상태인지를 본다. Evidence: L128–L133.
|
||
- **결과 관측** (process): 여기만 보면 두 상황이 같아 보인다. Evidence: L128–L131.
|
||
|
||
## Relationships
|
||
|
||
- **주입 명령 → 대상 상태 확인:** 걸렸는가를 먼저 본다. Evidence: L128–L133.
|
||
- **대상 상태 확인 → 결과 관측:** 걸린 뒤에만 결과를 읽는다. Evidence: L128–L133.
|