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>
31 lines
1.3 KiB
Plaintext
31 lines
1.3 KiB
Plaintext
# PACKAGE_CATALOG javadoc — 이전 카탈로그와 트리의 크기
|
|
/**
|
|
* Every direct child package of the production root, and what it may depend on.
|
|
*
|
|
* <p>Closed, and compared for exact equality against what is on disk. The previous catalog listed
|
|
* thirteen packages and the tree held twenty-two: {@code audit}, {@code config}, {@code failure},
|
|
* {@code fileserver}, {@code h2}, {@code idempotency}, {@code lock}, {@code notification} and
|
|
* {@code outbox} were governed by nothing, so a new package — or a new edge out of one of them —
|
|
* was green by omission.
|
|
*
|
|
* <p>{@code api} is the innermost: it names nobody. Everything else may reach it, and the
|
|
* declared edges beyond that are what the module map actually claims.
|
|
|
|
# DAG 테스트가 기록한 사이클
|
|
|
|
@Test
|
|
@DisplayName("the declared edges form a DAG")
|
|
void theDeclaredEdgesFormADag() {
|
|
List<String> cycles = new java.util.ArrayList<>();
|
|
for (String start : PACKAGE_CATALOG.keySet()) {
|
|
if (reaches(start, start, new TreeSet<>())) {
|
|
cycles.add(start);
|
|
}
|
|
}
|
|
|
|
assertThat(cycles)
|
|
.as(
|
|
"transaction -> postgresql and postgresql -> transaction both existed, so neither could"
|
|
+ " be extracted or swapped without unpicking the other first")
|
|
.isEmpty();
|