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>
15 lines
1.9 KiB
JSON
15 lines
1.9 KiB
JSON
{
|
|
"assetKey": "a10-f005-hyperloglog-merge",
|
|
"kind": "terminal",
|
|
"command": "set -e\nS=src/main/java/dev/caskeleton/adapter/outbound/cache/redis/sdk\necho \"### 여러 키를 읽어 하나에 쓰는 연산 일곱의 서명\"\nsed -n \"134,138p;151,155p;168,172p\" $S/api/operations/RedisSetOperations.java\nsed -n \"66,71p\" $S/api/operations/RedisBitmapOperations.java\nsed -n \"73,78p\" $S/api/operations/RedisGeoOperations.java\nsed -n \"33p;42,45p\" $S/api/operations/RedisHyperLogLogOperations.java\necho\necho \"### 정책 카탈로그의 위험 등급\"\nsed -n \"339,356p;562,566p;581,592p;614,618p\" src/main/resources/redis-sdk/redis-command-policy.yml | grep -v \"^$\"\necho\necho \"### R2 요청에 budget이 비어 있으면\"\nsed -n \"160,164p\" $S/lettuce/command/CommandPolicyGuard.java\necho\necho \"### 그래서 HyperLogLog 요청은 budget을 스스로 만든다\"\ngrep -n \"collectionBudget\" $S/lettuce/operations/HyperLogLogOperationRequests.java\nsed -n \"311,313p\" $S/lettuce/operations/RedisOperationContext.java\necho\necho \"### 같은 식을 쓰는 다른 두 메서드\"\ngrep -n \"Math.max(1L, requestBytes)\\|Math.max(1L, size)\" $S/lettuce/operations/RedisOperationContext.java\necho\necho \"### 그 설계를 적어 둔 곳\"\nsed -n \"6,14p\" $S/lettuce/operations/RedisOperationLimits.java\necho\necho \"### 같은 패키지에서 반대로 적어 둔 곳\"\nsed -n \"6,11p\" $S/api/command/OperationBudget.java",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template/src/adapter/outbound/cache-redis",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-02T12:53:03+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a10-f005-hyperloglog-merge.txt",
|
|
"svg": "evidence/rendered/a10-f005-hyperloglog-merge.svg",
|
|
"rawSha256": "eaf79cab1f65c297faf5c27ffbba903e707d384be8776921e34f84bd2c712d87",
|
|
"lines": 112,
|
|
"redaction": "none — 코드베이스 정적 검색"
|
|
}
|