Files
document-haness/docs/clean-architecture-backend-template/tech-log-studio/state-machines-and-ownership/concept/concept-adapter-outbound-objectstorage-c05.md
T
DongHyeonkaandClaude Opus 5 b2963105a8 docs(keycloak-session-store): import the session-storage lab as a new project
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>
2026-09-04 22:51:59 +09:00

50 lines
2.5 KiB
Markdown

---
kind: CONCEPT
slug: adapter-outbound-objectstorage-c05
title: revision은 건너뛰지도 되돌아가지도 못한다
topic: state-machines-and-ownership
project: clean-architecture-backend-template
status: 게시 전
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
rootTreeNode: concept:adapter-outbound-objectstorage-c05
evidenceCapturedOn: 2026-09-01
assets:
- key: adapter-outbound-objectstorage-c05
file: ../../../final/evidence/rendered/adapter-outbound-objectstorage-c05.svg
- key: adapter-outbound-objectstorage-c05-diagram
file: ../../../final/assets/diagrams/adapter-outbound-objectstorage-c05.svg
evidence:
- ../../../final/evidence/raw/adapter-outbound-objectstorage-c05.txt
source:
- 원본 분석 절은 analysis/09-adapter-outbound-objectstorage.md#L244 이다.
module: adapter-outbound-objectstorage
---
# revision은 건너뛰지도 되돌아가지도 못한다
`ObjectOperationStateMachine`이 publication·scan·reference·direct-grant·multipart 다섯 계열의 전이를 각각 switch로 적고, terminal 처리가 계열마다 명시적이다.
## 본문
<!-- body:start -->
`ObjectOperationStateMachine`이 publication·scan·reference·direct-grant·multipart 다섯 계열의 전이를 각각 switch로 적는다. terminal 처리가 계열마다 명시적이다.
## 어디서든 들어가고 나올 수 없는 분기
:::evidence key="adapter-outbound-objectstorage-c05-diagram" alt="정상 사슬의 어느 단계에서 EXPIRED 와 ABORTED 와 FAILED 와 CORRUPT 네 상자로 화살표가 나가고 네 상자가 모두 빗금으로 표시된 구조" caption="어디서든 들어가고 나올 수 없는 분기" zoom="false"
:::
뒤 둘은 **branch 전이**(EXPIRED/ABORTED/FAILED/CORRUPT)를 별도로 허용해, 정상 사슬 어디서든 실패로 빠질 수 있되 terminal에서는 나올 수 없게 한다.
## ObjectOperationStateMachine 참조 위치
:::evidence key="adapter-outbound-objectstorage-c05" alt="코드베이스에서 ObjectOperationStateMachine 를 검색한 출력 16줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ObjectOperationStateMachine 코드베이스 검색 — 16줄 · exit 0" zoom="true"
:::
## revision을 건너뛰거나 되돌릴 수 없다
`requireNextRevision(current, next)``next == current + 1`을 강제한다. `ObjectOperationStateMachineTest`가 셋을 이름으로 고정한다: `publicationFollowsScanFreeAndScanRequiredPaths`, `terminalOutOfOrderAndStaleRevisionTransitionsFailClosed`, `independentStateFamiliesDoNotImplyEachOther`.
<!-- body:end -->