문제: 설계서·계획서·납품 패키지·증거·학습 문서와 ADR이 기록이라는 표시 없이 지금 문서처럼 읽힌다. 상태 칸이 설계서 72개 중 40개, 계획서는 거의 없고, 있어도 Approved·확정·Accepted.처럼 값이 제각각이며 영어다. 고른 방법: docs/design, docs/history, docs/adr, docs/notification/adr의 .md 246개 맨 위에 같은 모양의 머리 블록을 단다. 칸은 상태·작성일· 요약(한국어 한 문장)·현재 정본, 대체됐으면 대체됨이다. 블록은 표시 줄 두 개로 감싸서 빼면 원문 바이트가 그대로 돌아온다(246개 모두 대조함). - 종류는 폴더가 정하고 둘째 줄에 적는다(plans/evidence는 증거). - 상태는 원래 상태 줄을 고정 어휘로 바꾼 값이다. 상태 줄이 없는 설계서와 체크 상자가 다 표시되지 않은 계획서는 「확인 안 함」. capability-status.md 제거 표로 지운 것이 확인된 설계서 다섯은 「폐기」, 2026-07-20 하네스 설계·계획과 production capability platform 설계는 「대체됨」이다. - 현재 정본은 구조 정리로 옮겨질 수 있는 src/messaging·src/grpc 대신 docs/ 쪽 문서나 옮기지 않는 leaf README를 가리킨다. docs/README.md에 「문서 수명과 언어」「기록 문서의 머리 블록」「문서와 코드를 같은 변경에서 고친다」를 더하고, 파생 서비스 안내에 머리 블록 충돌 가능성을 적었다. 버린 대안: H1 제목 아래에 블록을 두는 안은 보기에는 낫지만 빼는 규칙이 파일마다 달라져 원문 복원이 기계적이지 않다. 「종류」 칸을 따로 두는 안은 폴더와 같은 정보를 두 번 쓰게 한다. 위험·한계: 「확인 안 함」 설계서 38개, 계획서 51개는 지금 유효한지 아무도 판정하지 않았다. 요약은 제목·목표 줄을 보고 쓴 것이라 본문을 끝까지 읽지 않았다. 납품 패키지 셋의 MANIFEST.sha256는 이제 맞지 않는다 (납품 당시 바이트의 해시이고, 블록을 빼면 다시 맞는다). 리뷰 폴더에는 아직 머리 블록을 달지 않았다. 검증: 머리 블록을 뺀 내용과 HEAD 원본 246개 일치, check-work-docs.py rc=0, --links docs·README.md·CLAUDE.md·AGENTS.md 깨진 링크 0.
6.5 KiB
기록 · 증거 본문은 쓴 때의 원문이다. 지금 동작은 「현재 정본」을 읽는다.
- 상태: 보관
- 작성일: 2026-07-28
- 요약: Object Storage 작업 Batch B의 체크포인트 기록이다.
- 현재 정본:
src/adapter/outbound/objectstorage/README.md
Object Storage Batch B Checkpoint
- Date: 2026-07-28
- Branch:
codex/objectstorage-production-capability - Worktree:
/home/donghyeon/workspace/clean-architecture-backend-template-objectstorage - Evidence grade: repository-local non-skipping unit/contract/application-context tests
- Advanced cards: local managed single upload R1, local managed download R1
- R2 or production-provider readiness advanced: no
Implemented scope
- Added deterministic data/control namespaces, opaque reference/handle codecs, canonical request fingerprints, frozen binding/policy revisions, and bounded operation epochs.
- Added six strict canonical JSON control-record families with fixed field order, outer SHA-256 envelopes, schema/size checks, corruption rejection, and checked-in golden digests.
- Added provider-neutral publication, scan, reference, direct-session, multipart, and pending-effect state transitions with same-operation replay and conflicting-intent rejection.
- Added a provider contract and
filesystem-local-devimplementation with bounded streaming, immutable exclusive create, SHA-256 verification, exact inspect/version, full/range transfer, conditional retirement, create resolution, restrictive permissions, and path/symlink confinement. - Added single-process exact-version control CAS and restart/corruption/fault characterization.
Logical control keys use
.recordphysical leaves locally so object-store-valid prefix/leaf key pairs cannot collide as filesystem file/directory paths. - Added constructor-bound
app.object-storagesettings and compile-before-construction provider/destination/route/policy binding. The capability is disabled by default andfilesystem-local-devis rejected forprod/production. - Added disabled, unselected, invalid, selected-success, selected-construction-failure, close, legacy-only, and namespace-separated dual-run composition tests.
- Added semantic routing evidence for publish, replay without producer invocation, inspect, full transfer, absent reference, and exact retained route lookup.
- Added the exact nine-card readiness registry. Only local managed single upload/download are R1; direct, multipart, quarantine, retention, and production reconciliation remain R0.
TDD and defect evidence
Planned RED checks failed for the intentionally absent codec/kernel/provider/settings/readiness types before each implementation. Additional tests found and drove these corrections:
- Local control keys may legally have both a leaf and a child in object storage, while a filesystem
cannot have both
referenceandreference/lifecycle; local physical.recordmapping fixed the collision without changing logical keys. ObjectInspectionPort.inspectinitially threw for an absent known-route reference; it now returnsOptional.empty()while incomplete/corrupt evidence still fails closed.- The application purity test initially scanned its own test output after a full
check; it now derives the production class root from a production contract type. - The general B7 ArchUnit rule initially classified objectstorage provider-internal SPI/control
return values as public adapter responses. The existing negative fixture remains active, while a
dedicated non-empty rule now checks the actual objectstorage
*Adaptersemantic boundaries.
No skipped Docker or external-service test is used as Batch B readiness evidence.
GREEN verification
All commands ran from src/ unless noted and completed with BUILD SUCCESSFUL after the documented
RED/fix cycles:
./gradlew :adapter:outbound:objectstorage:verifyDependencyLocks --console=plain
./gradlew :adapter:outbound:objectstorage:test \
--tests '*ObjectNamespaceCodecTest' \
--tests '*ObjectRequestFingerprintCodecTest' \
--tests '*ObjectOperationEpochTest' --console=plain
./gradlew :adapter:outbound:objectstorage:test \
--tests '*ObjectControlRecordCodecTest' \
--tests '*ObjectOperationStateMachineTest' \
--tests '*ObjectOperationKernelTest' --console=plain
./gradlew :adapter:outbound:objectstorage:test \
--tests '*ObjectStorageProviderContract' \
--tests '*LocalDevObjectStorageProviderTest' \
--tests '*LocalDevObjectStorageRecoveryTest' --console=plain
./gradlew :adapter:outbound:objectstorage:test \
--tests '*ObjectStorageBindingCompilerTest' \
--tests '*ObjectStorageCapabilityConfigTest' \
--tests '*RoutingObjectStorageAdapterTest' --console=plain
./gradlew :adapter:outbound:objectstorage:test \
--tests '*ObjectStorageReadinessRegistryTest' --console=plain
./gradlew :sample-portfolio:test --console=plain
./gradlew :application-core:check \
:adapter:outbound:objectstorage:check --console=plain
./gradlew :app-bootstrap:test --tests '*CleanArchitectureTest' --console=plain
./gradlew verifyCleanArchitectureDependencies --console=plain
The final combined application/objectstorage checkpoint completed in 23 seconds. The focused Clean Architecture suite and dependency verification also passed.
documentation update
The canonical vault required by repository policy,
/home/donghyeon/workspace/ai-tool/ do not exist in this environment. Therefore the required
not be created or updated. No similarly named non-canonical clone was used. This exact access block
is recorded in the plan/design status and at this Batch B boundary.
Remaining gates and risks
filesystem-local-devhas no multi-node linearizability or power-loss durability evidence and is forbidden in production profiles.- The canonical S3/MinIO provider contribution, async bounded transport, provider qualification, response-loss fault tests, and protected AWS evidence are not implemented.
- Direct grants, multipart, quarantine/scan, retention/legal hold, privileged purge, reapers, and production reconciliation remain R0.
- The sample Poster workflow still uses the deprecated whole-
byte[]port and transaction-coupled legacy choreography. It is explicitly activated only in sample local/test configuration. - External API/broker consumers and deployed legacy data remain uninspected, so Gate A still blocks destructive migration or legacy removal.