# SolidJS frontend for Console v2

**Captured:** 2026-05-07
**Driver:** Phase 7 — CP-A foundations rejection memory (Law 14)

## Decision
REJECTED

## Why rejected

Console v2 ships React + TypeScript and stays on it. SolidJS was specced in Spec A (`recoil/pipeline/BUILD_SPEC_CONSOLE_V2.md`, 4755 lines) for fine-grained reactivity. React + hooks + the `useEventStream` SSE pattern already achieves the same UX at JT's operator scale — a single human reviewing shots, with a tree of <500 nodes and a handful of live SSE channels. There is no measured render bottleneck.

Switching to SolidJS would be a 4755-line architecture rebuild dressed up as a "reactivity upgrade": every component, every hook, every test harness, every type definition gets touched. The ecosystem support and JT's own familiarity favor React; the embedded-claude-terminal build (ADRs 0006–0010), the proposal tray, and the ttyd embed are all React-native. ADR-0011 locks Hybrid A as canonical.

Revisit only when React's render performance becomes a measured bottleneck on a real production scenario, not a synthetic benchmark.

## Cited by
- ADR-0011: Console v2 Hybrid A canonical
- BUILD_SPEC §3, §7 (Phase 7 — CP-A rejection memory)

## Status
- [x] Substantive rejection (Law 14 — anti-pattern memory)