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>
40 lines
1.9 KiB
Plaintext
40 lines
1.9 KiB
Plaintext
# 지침 문서가 적은 의존성
|
|
## Allowed
|
|
|
|
- `:application-core`, `:domain-core`, `:shared-contract` (Gradle matrix). Currently
|
|
only `:domain-core` + `com.github.f4b6a3:uuid-creator` are declared in
|
|
[build.gradle](build.gradle).
|
|
|
|
|
|
# 빌드 파일의 선언 블록
|
|
dependencies {
|
|
implementation project(':application-core')
|
|
|
|
testImplementation 'org.spockframework:spock-core:2.4-groovy-5.0'
|
|
}
|
|
|
|
# 뒤 문장이 든 두 이름을 각각 빌드 파일과 잠금 파일에서 찾는다
|
|
# 빌드 파일의 domain-core 언급(모든 표기) : 0
|
|
# 잠금 파일 줄 수 / uuid-creator·f4b6a3 : 154 / 0
|
|
# 그 잠금 파일이 덮는 configuration : annotationProcessor checkstyle compileClasspath mockitoAgent runtimeClasspath spotbugs spotbugsPlugins spotbugsSlf4j testAnnotationProcessor testCompileClasspath testRuntimeClasspath
|
|
# 프로덕션 클래스패스의 잠금 상태 : empty=compileClasspath,runtimeClasspath
|
|
336: lockAllConfigurations()
|
|
337: lockMode = LockMode.STRICT
|
|
|
|
# 그 라이브러리를 선언하는 곳
|
|
sample-portfolio/build.gradle:52: implementation 'com.github.f4b6a3:uuid-creator:6.1.1'
|
|
|
|
# 앞 문장의 셋과 강제되는 허용 목록
|
|
# 레지스트리 allowed_dependencies : ['domain-core', 'application-core']
|
|
# 문서가 든 셋 중 목록에 없는 것 : ['shared-contract']
|
|
# 그 목록이 강제되는 사슬
|
|
1419: Map<String, Set<String>> allowedProjectDependencies = registry.modules.collectEntries { module ->
|
|
}
|
|
|
|
Set<String> forbidden = actual - allowed
|
|
if (!forbidden.isEmpty()) {
|
|
throw new GradleException(
|
|
"Module ':${moduleName}' has forbidden project dependencies ${forbidden}. " +
|
|
"Allowed dependencies are ${allowed}. " +
|
|
577: dependsOn rootProject.tasks.named('verifyCleanArchitectureDependencies')
|