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

11
research/catalog/PatternCandidateCatalog.md
View file

@ -130,3 +130,14 @@ for Failure Boundary and Focus Return. Seven of eight immediate-run assertions m
a separate 100 ms nested-settling condition met eight. Removed-trigger default behavior
is a negative control, and immediate nested dismissal remains unresolved. Sixteen
hypotheses retained, no admission or full-pattern recurrence claim.
## Source/build/release distinction — 2026-09-26
[Independent Feature Boundary](../candidates/IndependentFeatureBoundary.md) develops
the existing seed around separate release/activation contracts (composition/execution,
L1/L4). Seventeen developed hypotheses now exist; none admitted. Pinned example
sources support partial mechanisms, not verified production release independence.
[Vertical Feature Slice](../candidates/VerticalFeatureSlice.md) gains a source-layout
example and a contrast with deployment. [Evidence](../reviews/FeatureDeploymentBoundaries.md)
and [provisional VC-06](../walkthroughs/VC06-MicrofrontendEstate.md) distinguish module,
artifact, activation, runtime-failure and organizational boundaries.

15
research/catalog/SourceCatalog.md
View file

@ -133,3 +133,18 @@ compares unchanged packages with an explicitly modified in-memory Escape mechani
The routed results are evidence for our proposed design, not observations of shipped
vendor behavior. Current raw control also reproduces production wrong-owner dismissal
in the new controlled fixture. Prior receipts remain unchanged.
## Feature organization and release contrast — 2026-09-26
| ID | Source | Revision / evidence scope |
| --- | --- | --- |
| SRC-0031 | [FSD todo example](https://github.com/feature-sliced/examples/tree/3050d1080506823df79c77457b96b47a835f87c8/todo-app) | 3050d1080506823df79c77457b96b47a835f87c8; feature interfaces and application build |
| SRC-0032 | [React microfrontends root-config](https://github.com/react-microfrontends/root-config/tree/b5414dcf7b4ecda95f11ada3821e30d2acfd9e4e) | b5414dcf7b4ecda95f11ada3821e30d2acfd9e4e; composition and workflow |
| SRC-0033 | [React microfrontends navbar](https://github.com/react-microfrontends/navbar/tree/55ff88e74714d12d3e3447250e34a2b7742e91f6) | 55ff88e74714d12d3e3447250e34a2b7742e91f6; lifecycle and workflow, same family as SRC-0032 |
| SRC-0034 | [single-spa recommended setup](https://single-spa.js.org/docs/recommended-setup/) | Living 6.x documentation; runtime binding and deployment contracts |
| SRC-0035 | [webpack Module Federation](https://webpack.js.org/concepts/module-federation/) | Living documentation; separately built containers and shared dependencies |
Accessed 2026-09-26. [17-file hash manifest](../reviews/FeatureDeploymentSources.json)
and [claims D01–D09](../reviews/FeatureDeploymentBoundaries.md). Static example-source
inspection, no builds or deployments run. Documentation revisions unknown; examples
and docs do not establish independent recurrence of a complete release contract.