Files
document-haness/docs/clean-architecture-backend-template/final/evidence/raw/269-messaging-core-api-reachability.txt
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

65 lines
4.0 KiB
Plaintext

# revision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
# search root: src, excluding src/messaging/messaging-core-api
# tool: git grep -n -w <Type> -- src ':!src/messaging/messaging-core-api'
## A. public types with ZERO references outside the owning leaf (production AND test)
MessageHandler exit=1
BatchMessageHandler exit=1
BatchMessageDelivery exit=1
ManualMessageHandler exit=1
PauseResumeController exit=1
ProcessingGuarantee exit=1
DelayedMessagePublisher exit=1
CapabilityRegistry exit=1
WireSafeText exit=1
## B. exception subclasses with ZERO references outside the owning leaf
MessageAuthenticationException exit=1
MessageBrokerUnavailableException exit=1
MessageConsumerException exit=1
MessageDeadLetterException exit=1
MessageHandlerTimeoutException exit=1
MessageHeaderRejectedException exit=1
MessagePublishAmbiguousException exit=1
MessagePublishRejectedException exit=1
MessageRedriveException exit=1
MessageRetryExhaustedException exit=1
MessageRoutingException exit=1
MessageSettlementUnknownException exit=1
# exit=1 means git grep found no match. exit=0 means at least one match.
## C. DeliveryContext: test-only outside the leaf
src/messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaContractHarness.java:7:import dev.caskeleton.messaging.api.delivery.DeliveryContext;
src/messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaContractHarness.java:216: new DeliveryContext(Instant.parse("2026-08-10T09:15:30Z"), false, "order-projection"));
src/messaging/messaging-policy/src/test/java/dev/caskeleton/messaging/policy/DeadLetterOrchestratorTest.java:12:import dev.caskeleton.messaging.api.delivery.DeliveryContext;
src/messaging/messaging-policy/src/test/java/dev/caskeleton/messaging/policy/DeadLetterOrchestratorTest.java:226: new DeliveryContext(Instant.parse("2026-08-10T09:15:35Z"), false, "order-projection"));
exit=0
## D. the three competing handler contracts
src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/delivery/BatchMessageHandler.java:15:public interface BatchMessageHandler<T> {
src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/delivery/MessageHandler.java:14:public interface MessageHandler<T> {
src/messaging/messaging-core-api/src/main/java/dev/caskeleton/messaging/api/settlement/ManualMessageHandler.java:15:public interface ManualMessageHandler<T> {
src/messaging/messaging-reliability-api/src/main/java/dev/caskeleton/messaging/reliability/IdempotentMessageHandler.java:21:public interface IdempotentMessageHandler<T> {
--- what the only wired delivery processor actually accepts ---
40: private final Function<MessageEnvelope<EncodedMessage>, HandleResult> handler;
47: Function<MessageEnvelope<EncodedMessage>, HandleResult> handler,
## E. batch metadata is built, the batch delivery it describes is never assembled
src/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaBatchConsumerRegistrar.java:104: return new BatchDeliveryMetadata(
src/messaging/messaging-rabbit/src/main/java/dev/caskeleton/messaging/rabbit/RabbitBatchConsumerRegistrar.java:139: new BatchDeliveryMetadata(
--- javadoc claiming a handoff ---
src/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaBatchConsumerRegistrar.java:118: * @param metadata the batch-wide metadata handed to the handler
src/messaging/messaging-rabbit/src/main/java/dev/caskeleton/messaging/rabbit/RabbitBatchConsumerRegistrar.java:153: * @param metadata the batch-wide metadata handed to the handler
--- any construction of BatchMessageDelivery anywhere ---
exit=1
## F. leaf has no framework dependency (12.2 sibling comparison is not applicable)
spring annotations in leaf: exit=1
non-java imports in leaf main:
(empty above means: JDK plus own package only)
build.gradle dependencies block:
apply plugin: 'java-library'
dependencies {
}