소유자 결정(2026-11-07, design-docs repo-structure/README.md 3.4절)으로 템플릿 샘플을 지운다. 샘플이 맡던 시험 대상은 앞 커밋들이 옮겼다. 참조 기능과 예제 화면, 두 context, 그 시험, e2e 3개, 수동 접근성 기록 7개, 런타임 프로필 키, test:reference-feature(명령, 산출물, 게이트 참조), 커버리지 정책 행을 지웠다. removable-template-features 목록은 비우고 장치는 남겼다: test:sample-removal은 인자가 없으면 목록을 하나씩 지우고, 비면 SKIP을 출력하고 보고서에 건너뛴 사례를 남긴다. 기능 스위치 시험과 홈 시작 링크 스위치 시험은 시험 전용 fixture 기능으로 옮겼다. browser soak은 생성 기능을 넣은 빌드에서 돈다. 문서의 샘플 경로를 고쳤다. 날짜가 붙은 설계·리뷰 기록의 본문은 그대로 두었다. 레지스트리 기준선(update:registry-baseline, OWNER DongHyeonka), CI 계약 기준선과 workflow, 초기 JS 기록(194,354B, 17파일, 첫 기능 6,327B, 기능 539B, context 4B)을 다시 받았다. 위험: 레지스트리 행 삭제는 breaking이다. 샘플을 고쳐 쓰는 다운스트림은 수정/삭제 충돌을 만난다. 성능 lab의 기능 라우트 측정은 템플릿에 공개 기능 라우트가 없어 measured:false다. TEMPLATE_FIXTURE 출처는 플랫폼 코드에 남았다. 검증(desktop): check:types, lint, check:architecture, check:registries, check:ci, verify:documentation, test:unit, test:component, test:contract, test:integration, test:recipes, test:coverage(Risk coverage PASS 378/378, 문턱 68개), test:e2e 183, test:a11y, test:visual, test:storybook, test:browser-capabilities, test:feature-scaffold PASS(76 checks), test:sample-removal SKIP, build, check:bundle.
13 KiB
Frontend Application Foundation
This repository is not treated as a minimal React project template and it is not an independent general-purpose SDK. Its architectural role is:
Frontend Application Foundation = Starter / Composition Skeleton + Reusable Capability Platform
The starter side owns bootstrap, routing, providers, project conventions and
the create:feature command that writes a feature; it ships no sample feature. The capability side owns reusable technical
problems such as HTTP execution, Server State, authentication boundaries,
IndexedDB/OPFS, Cache Storage, realtime, browser RPC, transfer and diagnostics.
The cost of a sophisticated capability is acceptable only when product features do not have to understand that internal sophistication.
Hybrid architecture
src/ has nine top-level folders. The descriptions match the table in
the layer contract, which also names every import rule.
Platform code is horizontal:
src/bootstrap— the composition root: runtime configuration, concrete adapter construction and the React mountsrc/presentation— generic UI and the inbound adapter: routes, layouts, the design system, pages and providerssrc/adapters— reusable capability runtimes that implement application ports: HTTP, auth, storage, query cache, telemetry, workers and moresrc/application— generic use cases, ports, policies and view-modelssrc/contracts— shared vocabulary and registries read by several layers, the workers and the build and release scriptssrc/platform— product-neutral primitives any folder may use: budgets, execution context, resilience, the telemetry pipeline, error envelopes and release coherence
Ownership declarations group features into deployable units:
src/apps— deployable apps: eachapp-module.tsdeclares an app and its context budget;template-app.tsis the app this build producessrc/contexts— bounded contexts: eachcontext-module.tsdeclares its app, route root and feature budget
Product business code is vertical:
src/features— removable vertical slices (src/features/<id>/{domain,application,contracts,adapters,presentation}) and the installed-feature catalogs (src/features/*.ts)
Inside one feature:
features/<feature>/domainfeatures/<feature>/applicationfeatures/<feature>/contractsfeatures/<feature>/adaptersfeatures/<feature>/presentation
The dependency model is:
Domain / Use case
|
| owns
v
Business port
^
| implements / binds
|
Feature-owned adapter binding
|
| generic type + mapper/codec + policy
v
Reusable capability runtime
|
v
Browser / network / native API
A use case never imports a platform adapter. Generic binding happens in the feature adapter/composition seam.
Capability-specific typed bindings
Do not introduce one universal Repository<TKey, TValue> abstraction for HTTP,
storage, realtime and transfer. Their lifecycle and failure semantics differ.
A reusable capability boundary is composed from:
- generic input/output types,
- feature-owned mapper or codec,
- feature-selected policy,
- one capability-specific runtime.
The HTTP path is the first concrete example.
src/adapters/http/feature-http-binding.ts owns transport/outcome
normalization. A feature create:feature writes contributes only:
- operation ID,
- route ID,
- exact request input type,
- exact success value type,
- wire-to-domain mapper.
The feature gateway therefore does not reimplement timeout, cancellation, transport failure, authentication failure or contract-violation projection.
Storage, realtime and transfer may gain their own typed binders only after actual feature repetition demonstrates the need. They must not be forced through the HTTP abstraction.
Custom adapter escape hatch
A product feature uses a reusable capability when the capability preserves the business requirement.
If a platform contract would require changing or weakening the business model, the feature implements a custom outbound adapter behind the same application port. The architecture boundary remains stable; platform reuse is optional.
Feature installation
A feature owns its contract, runtime and adapter contributions.
Central installed catalogs are aggregation points only:
installed-product-manifest.ts: which product features are compiled/selectedinstalled-feature-contracts.ts: boot-time contract aggregation (routes, route runtime contracts, invalidation) from the feature declarationsinstalled-feature-adapters.ts: application-input loaders, one per active feature, run when the router enters the feature's routes (15-01)installed-contract-contributions.ts: declared contract packages and the registry the HTTP executor resolves against, filled as features loadinstalled-feature-runtime-registries.ts: loads every runtime half and composes the contract contributions, the FE-REG-API rows projected from them and the FE-REG-SCHEMA registry; the platform overview page calls it after it draws its title (1103/15-01), the boot never doesloaded-feature-runtimes.ts: the same registries as module constants (top- level await) for Node scripts, tests and registry governance; nothing undersrcmay import it (boot-does-not-load-every-feature-runtime)
Feature-specific composition belongs under the feature itself. Central catalogs must not grow feature-specific branching logic.
Adapter contributions declare the platform capabilities they consume through
needs. The generic contribution seam in
src/features/feature-adapter-contribution.ts derives the context from that
list, so an HTTP-only feature cannot reach IndexedDB and an IndexedDB-only
feature does not receive the HTTP executor. It also binds
featureId -> ApplicationFeatureInputs[featureId] at the contribution
definition site instead of recovering that relationship with a final catalog
cast.
A contribution becomes composable only through
defineFeatureAdapterContribution(). That factory adds the private
contribution brand required by composeFeatureAdapterInputs(); a raw object
with the same visible fields is rejected by TypeScript and checked again at
runtime. The negative type fixture
invalid-direct-feature-composition.ts is part of FE-GATE-003 so this
authority cannot be bypassed by calling the composer directly.
For IndexedDB-backed features, createIndexedDbRepositoryProvider() is the
composition helper that maps feature-owned repository identities to typed
IndexedDbRepositoryPort instances. It does not create a universal storage
repository or move dataset/migration/lifecycle policy into the feature.
The repository now has two executable contribution shapes:
- A feature
create:featurewrites:needs: ["http", "telemetry"] - The Local Draft consumer:
needs: ["indexedDb"]
Local Draft is a test fixture (tests/fixtures/indexeddb-consumer) used to
prove the second capability shape; it is not a feature of the product. Its
browser-capability test composes the feature over the real
createIndexedDbRuntime and native IndexedDB, proving that this seam is not
limited to an in-memory contract fixture.
The bootstrap does not build indexedDb: IndexedDB is an opt-in reference
runtime (productionComposition: false in
config/recipes/frontend-capability-recipes.json). The composition example is
recipes/frontend-capabilities/indexeddb-feature-capability.ts
(createLocalDraftIndexedDbCapability, exercised by
tests/recipes/indexeddb-feature-capability.test.ts). A product that installs a
feature with needs: ["indexedDb"] copies it and returns indexedDb from the
product-owned src/bootstrap/product-composition.ts. Until it does, the feature
capabilities in src/bootstrap/runtime-adapters.ts fail the app typecheck, and
composeFeatureAdapterInputs() rejects the composition with
feature <id> needs indexedDb, which the host did not provide.
The same file is where a product adds any other capability and the
credential provider for a product auth profile. The capability's type goes in
the product-owned src/features/product-capabilities.ts
(ProductFeaturePlatformCapabilities, which FeaturePlatformCapabilities
extends), so every typecheck program that sees a feature sees it
(tests/unit/product-extension-typecheck.test.ts). The composition root keeps the order: scope fence, ANONYMOUS
profile, product provider, session, scope fence again
(tests/unit/runtime-adapters-credential-order.test.ts). A product that owns
the session itself (a BFF whose session is an httpOnly cookie) returns its
session owner from composeProductSessionOwner in the same file. It is asked
first, before http exists, only when AUTH_MODE is external, and it comes
before the host's __CA_FRONTEND_AUTH_OWNER__; null leaves the session to
that global. Its context (src/bootstrap/product-session-owner-context.ts)
carries a fetch with one deadline over the whole exchange, the page for a
sign-in redirect, the page's session storage for that redirect only, and
readCookie. Product auth profiles, runtime-config keys and the keys'
FE-REG-ENV rows go in src/contracts/product-contracts.ts; each joins the
template's registry under the same checks
(tests/unit/product-composition-fixture.test.ts).
Presentation consumer surface
ApplicationProvider remains the composition root for presentation, but new
consumers should not navigate a root ApplicationApi service locator.
Use the narrow hooks in
src/presentation/providers/application-provider.tsx:
useApplicationSessionuseApplicationPreferencesuseApplicationDiagnosticsuseApplicationRuntimeuseApplicationRecoveryuseApplicationFeature
useApplication exists only as a deprecated compatibility escape hatch.
Canonical imports
New feature code should use capability public entry points rather than deep
runtime modules. For HTTP the canonical path is
src/adapters/http/index.ts.
Compatibility re-exports may exist during a migration window, but they must be marked as compatibility/deprecated paths and should not expand into an unbounded public barrel.
Policy ownership
Duplication is judged by ownership, not by syntax percentage.
Small local validators can remain duplicated when locality improves auditing.
Business or concurrency policy must have one owner. For example the reference
create mutation keeps definition ID, idempotency requirement, duplicate policy
and invalidation policy in one feature-owned definition and binds only
scope and execute per usage site.
Runtime decomposition rule
Large runtime files are not split by line count.
Extract a boundary when it has its own state machine, lifecycle owner, failure model or compensation/recovery responsibility. Candidate seams include:
- connection/open/upgrade lifecycle,
- transaction ownership,
- migration state machine,
- reconnect/backoff and heartbeat,
- subscription ownership,
- retry/deadline/cancellation ownership,
- settlement/reconciliation/cleanup.
A cohesive 2,000-line state machine can remain together. A 300-line file with multiple lifecycle owners is a better extraction candidate.
Current runtime boundary audit
The current large-runtime inventory was reviewed using that rule.
- IndexedDB remains large, but connection, transaction, migration, maintenance and failure translation already have separate owners/modules.
- resumable upload already separates runtime policy, checkpoint persistence, HTTP control-plane transport, part execution, cancellation and mutation locking.
- realtime already separates reconnect policy/coordinator, event codec/consumer and stream coordination.
- OPFS is separated into browser runtime, journal, byte-store, policy and worker protocol/runtime responsibilities.
- HTTP V3 still owned retry eligibility/backoff inside the execution state
machine, so that responsibility moved to
src/adapters/http/http-retry-lifecycle.ts.
No other runtime is split merely because of its line count.
Consumer quality metrics
Before adding another abstraction, implement or model multiple real feature uses and measure:
- feature-owned adapter LOC,
- repeated platform glue,
- number of platform-internal types exposed to the feature,
- central catalog edits,
- files changed for one normal query/command,
- whether native browser/network APIs leak into the feature.
The target feature-development path is:
- domain type and invariant,
- use case,
- port,
- transport/storage schema plus mapper/codec,
- capability binding,
- presentation controller/page.
A product feature should not need to know the retry scheduler, abort ownership, effect-certainty machinery, transaction leases, reconnect coordinator, OPFS journal or provider lifecycle.
The executable REST and IndexedDB consumer baselines are recorded in
capability-consumer-experience.md.
Contract placement and the global-vs-owner-local audit are recorded in
contract-ownership.md.
Verification paths
Product-development verification, capability verification and release assurance
are intentionally separate. See
docs/testing/taxonomy.md.
Host-level CI-runner tests belong to tests/system, not tests/unit.
Reusable capability consumer contracts belong to tests/contract.