coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Distinguish feature organization from independent release boundaries

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-26 23:06:16 +02:00
parent 29ccad7002
commit b8eec87f08
14 changed files with 460 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

10
research/candidates/VerticalFeatureSlice.md
View file

@ -38,3 +38,13 @@ Evidence locators: [breadth review](../reviews/PatternBreadthExpansion.md).
All relations are research proposals; no canonical identity or admitted graph edges.
The next test is planned, not executed. Known uses of the complete proposed contract
have not been verified in this investigation.
## Pinned source-layout contrast — 2026-09-26
[Boundary review](../reviews/FeatureDeploymentBoundaries.md) D01–D03 locates public
feature entry points, UI/model separation and page composition in a pinned FSD todo
example, alongside one application build script. The shared entity/API layer means
feature grouping does not imply a private persistence adapter. This is a partial
static use, not a release or import-enforcement test. Compare
[Independent Feature Boundary](IndependentFeatureBoundary.md): release cadence adds
activation/version contracts that source grouping alone does not provide.