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

20
workplans/FEP-WP-0003-contrasting-schools.md
View file

@ -130,3 +130,23 @@ upstream message, pattern promotion or M2 completion. Resume feature/import vers
release-boundary and navigation evidence next; keep the router limitation as a live
T01 follow-up rather than requiring a production fork here. Sixteen hypotheses,
T02/T03 and the independent-human gate unchanged. No model calls.
## Feature organization versus independent activation — 2026-09-26
T01 progress: reviewed 17 files at pinned commits in feature-sliced/examples todo-app
and react-microfrontends root-config/navbar; SRC-0031–0035 include primary mechanism
docs. Partial feature interfaces coexist with one application build; separate build/
release definitions coexist with shared startup dependencies. No build, CI, cloud
deployment or rollback execution. FeatureDeploymentSources.json pins all file hashes.
Developed Independent Feature Boundary from the existing seed, bringing the corpus
to seventeen hypotheses. Vertical Feature Slice refined; provisional VC-06 traces
activation, version skew, partial load failure and rollback with a single-cadence
branch. T02 remains todo for its post-M1 gate; this is preparatory work, not M2 acceptance.
See research/reviews/FeatureDeploymentBoundaries.md.
Next T01 evidence: local compatible/incompatible feature versions against unchanged
host, failed load, activation rollback with fresh and already-running sessions, and
shared startup outage. No production workflows/credentials needed. Navigation checks
and broader router-lifecycle limits remain live; T03 and human-validation gate unchanged.
No model calls, deployment, canonical admission or proven generativity benefit.