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

6
research/plan/ValidationCases.md
View file

@ -1,6 +1,6 @@
# Validation cases
Status: synthetic briefs · VC-01 and VC-02 have drafts/self-reviews; VC-03 has a provisional exploratory draft; other cases remain planned.
Status: synthetic briefs · VC-01 and VC-02 have drafts/self-reviews; VC-03 and VC-06 have provisional exploratory drafts; other cases remain planned.
[VC-01 draft](../walkthroughs/VC01-TransactionalAdministration.md) and [VC-02 draft](../walkthroughs/VC02-OfflineFieldNotes.md) are reasoning exercises,
not runtime validation or M1 acceptance.
@ -52,3 +52,7 @@ Keep development examples separate from the held-out set.
2026-09-26: [provisional VC-03](../walkthroughs/VC03-ContentPublication.md) explores
navigation/rendering before M1 completion. It does not satisfy the M2 case gate.
2026-09-26: [provisional VC-06](../walkthroughs/VC06-MicrofrontendEstate.md) contrasts
independent activation with one coordinated release cadence. Source inspection does
not complete its runtime/independent-review obligations or the M2 gate.