Files
clean-architecture-frontend…/docs/architecture/capability-consumer-experience.md
T
DongHyeonka b72cd7d4a7 test(fixtures): local-draft 샘플을 IndexedDB 소비자 fixture로 옮긴다
src/features/local-draft-feature는 기능이 아니라 IndexedDB recipe의
소비자다. 시험 5개와 recipe가 쓰고, 그래서 생성기에 NOT_A_FEATURE
예외가 있었다(S4 3.1절 S-3).

코드를 tests/fixtures/indexeddb-consumer/로 옮기고 import만 고쳤다.
NOT_A_FEATURE 표식은 이 폴더만 썼고 다운스트림 둘에도 없어 생성기에서
지웠다. 선언 없는 폴더는 밖으로 옮기라는 메시지로 실패한다. 매뉴얼
오류표, README, starter-experience, capability-consumer-experience,
patterns를 고쳤다.

위험: fixture는 기능 폴더 밖이라 기능 계층 규칙(dependency-cruiser)이
걸리지 않는다. recipe가 tests/ 아래 파일을 type import한다.

검증(desktop): test:contract, test:recipes, test:browser-capabilities,
test:unit 통과.
2026-11-08 13:51:55 +09:00

6.4 KiB

Capability consumer experience baseline

Correctness inside a reusable capability is not sufficient. The platform is also evaluated by how much of that correctness a normal feature developer must understand.

These measurements are baselines, not score targets. A lower line count is not automatically better if it hides business semantics or creates a universal repository abstraction.

Scenario A — reference REST feature

The existing reference feature is the executable REST consumer.

It covers list/detail/create behavior, mapping, typed operation inputs, application ports and an optimistic mutation path.

The feature-owned boundary and application source is these four files:

  • application/reference-feature-api.ts
  • contracts/reference-mapper.ts
  • adapters/reference-http-gateway.ts
  • adapters/create-reference-feature-input.ts

This document does not keep their line counts; a hand-typed count drifted from the code (review 14-07). Measure them with wc -l src/features/reference-feature/{application/reference-feature-api.ts,contracts/reference-mapper.ts,adapters/reference-http-gateway.ts,adapters/create-reference-feature-input.ts}.

The important boundary metric is not the raw total. It is what those files need to know about the platform.

Current result:

  • HTTP platform imports in the feature adapter layer: 2 files,
  • canonical import path used by both: src/adapters/http/index.ts,
  • direct imports of http-execution-v3.ts, retry scheduler, response reader, auth admission or effect-certainty internals: 0,
  • feature gateway owns transport failure projection: 0,
  • feature gateway chooses operation ID, route ID, exact input/value type and mapper: yes,
  • central installed files own feature-specific adapter/runtime wiring: no; feature-owned contributions are aggregated centrally.

The reusable HTTP capability now owns execution-outcome normalization through createFeatureHttpBinding. A feature may still implement a custom outbound adapter behind its application port when the reusable contract does not match its business requirement.

Scenario B — IndexedDB local draft

The executable consumer probe is:

tests/contract/consumer-experience/indexeddb-local-draft.test.ts

It runs and reads the one Local Draft implementation, the test fixture tests/fixtures/indexeddb-consumer (the template's former local-draft sample under src/features/, moved there because it is no product feature). An earlier isolated copy had drifted from it and was removed (09-12).

The consumer owns the Local Draft domain/application API and declares the slice of the repository it calls (LocalDraftRepository in tests/fixtures/indexeddb-consumer/adapters/local-draft-indexeddb-store.ts). The host hands in an IndexedDbRepositoryPort<LocalDraft, never> through the indexedDb capability; the port satisfies that slice structurally. The cross-capability composition contract lives at:

tests/contract/reusable-capability/feature-adapter-composition.test.ts

That test composes one HTTP-only contribution and the IndexedDB-only Local Draft contribution through the same generic catalog path.

The browser-level composition proof lives at:

tests/browser-capabilities/local-draft-composition.spec.ts

It runs against native browser IndexedDB. The test creates the platform createIndexedDbRuntime, exposes that runtime through the typed createIndexedDbRepositoryProvider, composes LOCAL_DRAFT_FEATURE_ADAPTER_CONTRIBUTION, then executes Local Draft save/find/remove through the feature API. The Local Draft feature still does not import the IndexedDB runtime or native browser API.

Measured on the Local Draft consumer, then under src/features/ (09-12):

Metric Result
feature LOC (all .ts files) 295
import statements leaving the feature (contracts/errors, contracts/result, application-api, feature-adapter-contribution) 7
native IndexedDB API references 0
src/adapters/storage/indexeddb/** imports 0
src/application/ports/browser-file-storage/** imports 0

The feature does not import the storage runtime or its port, so removing the browser file/storage runtime (test:browser-file-storage-removal) leaves it compiling.

The contract test rejects feature source that reaches for globalThis.indexedDB, IDBFactory, IDBDatabase, IDBTransaction, IDBObjectStore, the concrete IndexedDB adapter directory or the browser-file-storage port.

What this does and does not prove

The contract probe confirms that feature business code does not need native IndexedDB knowledge once an IndexedDbRepositoryPort has been composed. The browser-capability proof additionally confirms that the same feature contribution works when that port is backed by the repository's real createIndexedDbRuntime and native IndexedDB implementation.

It does not prove that composition of createIndexedDbRuntime is cheap. That constructor still owns substantial infrastructure policy:

  • dataset scope and storage policy,
  • physical store governance,
  • retention/idempotency stores,
  • schema migrations,
  • codec and query policy,
  • lifecycle authority,
  • durability, scheduling and observation.

That complexity belongs at the composition/platform boundary, not in the feature. The Local Draft vertical slice is now the second concrete consumer, and it confirms that the stable seam is the typed repository provider plus a feature-owned repository identity. It does not show that dataset scope, retention, migration, codec or lifecycle-authority configuration can be safely collapsed into one universal create...Repository<T> factory.

A convenience profile should therefore be introduced only after another IndexedDB-backed product feature repeats the same infrastructure policy, not merely because two features consume the same repository port.

Consumer-quality review checklist

For each new product feature, record:

  • feature-owned adapter LOC,
  • platform glue LOC,
  • files changed,
  • central catalog edits,
  • direct imports from capability-internal modules,
  • native browser/network API references,
  • duplicated failure/retry/lifecycle policy.

A healthy feature path should look like:

  1. domain type and invariant,
  2. use case,
  3. business port,
  4. feature-owned mapper/codec and policy,
  5. capability-specific binding,
  6. presentation controller/page.

The feature should not need the retry scheduler, abort ownership, effect-certainty machinery, IndexedDB transaction lifecycle, OPFS journal, reconnect coordinator or provider process model.