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>
37 lines
2.1 KiB
Plaintext
37 lines
2.1 KiB
Plaintext
# 클래스 산출물이 소스보다 새로운가 : yes
|
||
java.version = 21.0.12
|
||
|
||
[계약이 말하는 두 갈래]
|
||
normalize("0190bd6e-7c3e-7abc-8def-0123456789ab") -> "0190bd6e-7c3e-7abc-8def-0123456789ab"
|
||
normalize("0190BD6E-7C3E-7ABC-8DEF-0123456789AB") -> "0190bd6e-7c3e-7abc-8def-0123456789ab"
|
||
normalize("not-a-uuid") -> IllegalArgumentException: Invalid UUID string: not-a-uuid
|
||
normalize("0190bd6e7c3e7abc8def0123456789ab") -> IllegalArgumentException: Invalid UUID string: 0190bd6e7c3e7abc8def0123456789ab
|
||
|
||
[정규형에서 한 글자를 지운다]
|
||
normalize("0190bd6e-7c3e-7abc-8def-123456789ab") -> "0190bd6e-7c3e-7abc-8def-0123456789ab"
|
||
원본과 같은가 : true
|
||
normalize("0190bd6e-7c3e-7abc-8def-0123456789a") -> "0190bd6e-7c3e-7abc-8def-00123456789a"
|
||
원본과 같은가 : false
|
||
normalize("0190bd6e-7c3e-7abc-8def-012345678ab") -> "0190bd6e-7c3e-7abc-8def-0012345678ab"
|
||
원본과 같은가 : false
|
||
normalize("0190bd6e7c3e-7abc-8def-0123456789ab") -> IllegalArgumentException: Invalid UUID string: 0190bd6e7c3e-7abc-8def-0123456789ab
|
||
원본과 같은가 : false
|
||
|
||
[길이가 36이어도 대시 위치가 다르면 같은 경로로 떨어진다]
|
||
normalize("0000001-00001-0001-0001-000000000001") -> "00000001-0001-0001-0001-000000000001"
|
||
|
||
[그룹이 규정 자릿수를 넘으면 상위 비트를 버린다]
|
||
normalize("100000001-1-1-1-1") -> "00000001-0001-0001-0001-000000000001"
|
||
normalize("1-1-1-1-1000000000001") -> "00000001-0001-0001-0001-000000000001"
|
||
|
||
[십육진이 아닌 것도 통과한다]
|
||
normalize("+1-1-1-1-1") -> "00000001-0001-0001-0001-000000000001"
|
||
normalize("١-1-1-1-1") -> "00000001-0001-0001-0001-000000000001"
|
||
|
||
[서로 다른 입력이 같은 식별자가 된다]
|
||
00000001-0001-0001-0001-000000000001 <- "1-1-1-1-1", "01-01-01-01-01", "+1-1-1-1-1", "00000001-0001-0001-0001-000000000001"
|
||
00000001-0001-0001-0001-000000000002 <- "1-1-1-1-2"
|
||
|
||
[같은 파서를 쓰는 형제 메서드]
|
||
toUuid("1-1-1-1-1") = 00000001-0001-0001-0001-000000000001
|