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/plan/OpenQuestions.md
View file

@ -92,3 +92,14 @@ Q05 routing follow-up: [experimental owner dispatch](../reviews/NestedOwnershipR
separates input delivery from return-focus policy. Successful cancellation and cleanup
matter alongside correct close targeting. The bounded mechanism comparison supports
this distinction; it does not establish a universal ownership model or close Q05.
## Q06 source, artifact and activation boundaries — 2026-09-26
[Pinned contrast](../reviews/FeatureDeploymentBoundaries.md) locates feature APIs
inside one application build and separately defined microfrontend release workflows.
Shared startup dependencies still couple runtime availability. Q06 now distinguishes
module imports, artifacts, activation bindings, runtime failures and team ownership;
separate repositories prove none of the latter guarantees by themselves.
[VC-06](../walkthroughs/VC06-MicrofrontendEstate.md) changes only release cadence to
show why source boundaries can remain while deployment units merge. Runtime version
skew/rollback and independent assessment remain open; Q06 is not closed.