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>
38 lines
1.6 KiB
Plaintext
38 lines
1.6 KiB
Plaintext
# 이 태스크를 실행하는 워크플로 둘, 그리고 그 방아쇠
|
|
# ci-quality-gates.yml
|
|
# on:
|
|
# pull_request:
|
|
# push:
|
|
# branches: ["main"]
|
|
# workflow_dispatch:
|
|
# 121: jpa-candidate-evidence:
|
|
# 142: :adapter:outbound:persistence-jpa:verifyJpaCandidateEvidence
|
|
# jpa-r2-evidence.yml
|
|
# on:
|
|
# workflow_dispatch:
|
|
# 17: jpa-r2-evidence:
|
|
# 45: :adapter:outbound:persistence-jpa:verifyJpaPrimaryFoundationEvidence
|
|
|
|
# 게이트는 매니페스트 태스크를 거쳐 활성 카드의 준비도 태스크에 의존한다
|
|
configuredActiveCards.each { String cardId, Object rawCard ->
|
|
Map<String, Object> card = rawCard as Map<String, Object>
|
|
if (cardId != 'jpa-primary-foundation') {
|
|
dependsOn jpaEvidenceTaskAtPath(card['readiness-task'] as String)
|
|
}
|
|
|
|
# 실제 태스크 그래프 (--dry-run 은 그래프의 모든 태스크를 SKIPPED 로 찍는다)
|
|
:adapter:outbound:persistence-jpa:postgresqlMigrationIntegrationTest SKIPPED
|
|
:adapter:outbound:persistence-jpa:generateJpaEvidenceManifests SKIPPED
|
|
:adapter:outbound:persistence-jpa:verifyJpaCandidateEvidence SKIPPED
|
|
|
|
# R2 집계 게이트가 매니페스트에서 이름으로 요구하는 카드 일곱
|
|
[
|
|
'jpa-observability-lifecycle',
|
|
'jpa-security-baseline',
|
|
'jpa-flyway-migration',
|
|
'jpa-transaction-runtime',
|
|
'jpa-aggregate-store',
|
|
'jpa-query-model',
|
|
'jpa-primary-foundation'
|
|
].each { String cardId ->
|