frontend-patterns/research/cases/CarniatoGrandUnifyingArchitecture.md
tegwick 1f95f6389a Record first authority investigation and preserve failed live-run evidence
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-24 15:43:59 +02:00

25 lines
1.5 KiB
Markdown

# Carniato source review — authority and feedback
Status: extracted; initial manual review, 2026-09-24, codex (self-review).
Source: SRC-0001, Ryan Carniato, [original article](https://dev.to/playfulprogramming/the-grand-unifying-architecture-of-frontend-bhk).
Edition and date uncertainty: see the source catalog. No API-generated findings.
| Claim | Original locator | Source statement, paraphrased | Our interpretation |
| --- | --- | --- | --- |
| C01 | Core Responsibilities, Content, paragraph 1 | Content authority resides on the server. | Authority placement is an assumption of this model. |
| C02 | Core Responsibilities, Affordances, paragraph 1 | Interaction feedback should precede a server round trip. | Local feedback need not imply local authority. |
| C03 | Content: Reactive reads over the wire, final paragraph | The live graph must be reconstructible from durable state. | Projection state and durable authority should be distinguished. |
C03 was checked manually in the original; it is outside the bench excerpt.
## Limits and counterexample
The article's universal framing is broader than this review supports. Local-first
primary data challenges mandatory server authority; it does not refute separating
responsibilities. Framework implementation claims and examples were not executed.
## Disposition
Retain Server Authority and Immediate Feedback as candidates. Do not infer a
requires edge between them. Recurrence and failure behavior need further evidence.
Broader architecture comparisons remain open under FEP-WP-0002-T02/T03.