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

5
research/README.md
View file

@ -60,3 +60,8 @@ A partial guard loses input; a complete remedy remains open. Original results re
Latest bounded mechanism test: [ownership routing](reviews/NestedOwnershipRouting.md)
meets 24/24 routed assertions versus 20/24 unmodified controls, with explicit scope
limits. No delay or readiness wait; no production fork or canonical promotion.
Latest breadth evidence: [feature versus deployment boundaries](reviews/FeatureDeploymentBoundaries.md)
compares pinned example sources and adds [provisional VC-06](walkthroughs/VC06-MicrofrontendEstate.md).
Independent Feature Boundary develops an existing seed; current corpus has seventeen
hypotheses and four synthetic walkthroughs. No deployment independence was runtime-verified.