coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Draft CAND-0018 Capability Contract Boundary from a screened AI-chat lead

Browse source 
history/260927-ComplexWebAppUiComponents_chatgpt.txt is a pasted AI-chat
transcript on UI-integration architecture. It fails this repo's primary-source
bar (unauthored, unverifiable broken citation markers), so it is screened as
a leads-only document, not cataloged as a source, and never cited as evidence.

Instead read the two real specs it pointed to: MDN Custom Elements (SRC-0046)
and webpack Module Federation (SRC-0047). Neither defines a semantic UI
capability contract (inputs/events/commands/slots) as a first-class concept;
that gap motivates the new draft hypothesis, distinct from the existing
Independent Feature Boundary (release cadence) and Vertical Feature Slice
(source grouping) candidates.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 290719@bnt-lap001
Assistant-Session: 55cbe504-1bfe-4932-b761-29016523c87b
This commit is contained in:
tegwick 2026-09-27 23:29:10 +02:00
parent fad8abdc2c
commit eaa1608771
7 changed files with 657 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -362,3 +362,20 @@ a returns review, and the workplan's rule against manufacturing cycles to reach
that count still applies. A stale-navigation reproduction, if pursued, needs
actual execution and is out of scope for the static-source protocol used here.
T02/T03/T04 unchanged; the local authored navigation fixture remains paused.
## Capability Contract Boundary drafted from a screened lead — 2026-09-27
T01: `history/260927-ComplexWebAppUiComponents_chatgpt.txt`, a pasted AI-chat
transcript on UI-integration architecture, was screened as a non-primary lead,
not a source — it is unauthored and carries unverifiable citation markers, so
it is not assigned a SRC ID and is not cited as evidence anywhere. Read the two
real specs it pointed to instead: MDN Custom Elements (SRC-0046) and webpack
Module Federation (SRC-0047). See [review](../research/reviews/CapabilityContractSources.md).
Drafted [Capability Contract Boundary](../research/candidates/CapabilityContractBoundary.md)
(CAND-0018): declaring a UI capability's semantic surface (inputs/events/commands/
slots) separately from whichever runtime-isolation mechanism carries it. Distinct
from Independent Feature Boundary (release cadence) and Vertical Feature Slice
(source grouping). Eighteen hypotheses now exist; no known use of an explicit
capability contract located, no application/runtime evidence, no canonical
admission or M1/M2 change.