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>
21 lines
911 B
Plaintext
21 lines
911 B
Plaintext
openjdk version "21.0.12" 2026-07-21
|
|
동적 대상 프로파일 하나에 두 플래그 조합 넷을 넣는다
|
|
|
|
------------------------------------------------------------------------------------------------
|
|
pinning=true stable=true
|
|
블로킹 : 통과
|
|
반응형 : 통과
|
|
pinning=false stable=false
|
|
블로킹 : 거부 — validated DNS pinning for dynamic targets, call-scoped validated DNS pinning
|
|
반응형 : 거부 — validated DNS pinning for dynamic targets
|
|
pinning=true stable=false
|
|
블로킹 : 거부 — validated DNS pinning for dynamic targets
|
|
반응형 : 거부 — validated DNS pinning for dynamic targets
|
|
pinning=false stable=true
|
|
블로킹 : 거부 — call-scoped validated DNS pinning
|
|
반응형 : 통과
|
|
|
|
출하된 반응형 전송 둘의 두 플래그
|
|
reactorNetty pinning=true stable=true
|
|
jettyHttp3Experimental pinning=false stable=false
|