Preserve initial frontend pattern language research scaffold

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9

research/cases/CarniatoGrandUnifyingArchitecture.md

@@ -0,0 +1,79 @@
+# Case Study — The Grand Unifying Architecture of Frontend
+
+Status: initial research stub
+
+Source:
+Ryan Carniato, "The Grand Unifying Architecture of Frontend".
+
+## Why this source matters
+
+The article attempts to unify several modern frontend architectures beneath framework-specific terminology.
+
+Its most useful conceptual move is the decomposition:
+
+```text
+Navigation → Content → Affordance
+```
+
+with a characteristic movement:
+
+```text
+client → server → client
+```
+
+for server-authoritative applications.
+
+## Initial interpretation
+
+### Navigation
+
+Contains aspects of:
+
+- addressability,
+- routing,
+- user intent,
+- mutation initiation.
+
+### Content
+
+Contains aspects of:
+
+- authority,
+- server-side state,
+- projection.
+
+### Affordance
+
+Contains aspects of:
+
+- local interaction state,
+- speculative state,
+- immediate feedback.
+
+## Main qualification
+
+The model strongly fits server-authoritative web applications.
+
+It should not be promoted unchanged into the general canon because:
+
+- local-first systems may treat local data as primary,
+- replicated systems may have multiple authorities,
+- peer-to-peer systems may lack a distinguished server,
+- microfrontend concerns cut across this axis,
+- internal modularity is largely orthogonal to it.
+
+## Research tasks
+
+- extract concrete architecture examples from the article,
+- identify all implicit assumptions,
+- map each example to responsibility dimensions,
+- identify candidate patterns,
+- compare against:
+  - local-first,
+  - HTMX/hypermedia,
+  - SPA,
+  - server components,
+  - islands,
+  - LiveView-style persistent server interaction,
+- identify where the model is descriptive versus normative,
+- determine which concepts should enter the canon.