DongHyeonkaandClaude Opus 5
5f10b791d3
Snapshot of the in-flight state that already existed, identically, in both this worktree and the main checkout before this session began: the initial HTTP Client platform implementation (previously untracked), the redis-lab removal, and the JPA / object-storage / notification integration work. Kept separate from this session's HTTP Client review response, which lands in the following commit, so the two bodies of work stay reviewable apart. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.2 KiB
1.2 KiB
app-bootstrap — application entry point & composition root
Registered identity
- Module ID:
app-bootstrap - Gradle path:
:app-bootstrap - Focused test (derived from Gradle path):
./gradlew :app-bootstrap:test --console=plain - Runtime baseline: Java 21; repository framework baseline: Spring Boot 4.0.0.
- Registry SSOT:
src/config/architecture/modules.json.
Package root: dev.caskeleton.bootstrap.
Responsibility
- Spring Boot entrypoint (
CaSkeletonApplication). - Runtime settings and logging bootstrap.
- Final cross-module wiring.
- Architecture tests that inspect all modules.
Allowed
- Runtime leaves whose dependency edge is explicitly allowed and whose
runtime_membershipsincludesapp-bootstrapinsrc/config/architecture/modules.json; do not duplicate the 19-leaf dependency list here. - Spring Boot startup/runtime dependencies.
- ArchUnit in tests.
Forbidden
- Concrete business policy.
- Controllers, use cases, repository adapters, or mappers authored directly under bootstrap.
- Settings classes that implement business logic.
Test
cd src
./gradlew :app-bootstrap:test
./gradlew verifyCleanArchitectureDependencies