frontend-patterns/research/catalog/SourceCatalog.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

2.8 KiB

Source Catalog

Identified primary sources

ID Source and edition State Prepared input
SRC-0001 Ryan Carniato, The Grand Unifying Architecture of Frontend; web edition accessed 2026-09-24; displayed Sep 22, year unverified extracted; initial manual review; live run failed Authority and feedback packet
SRC-0002 Martin Kleppmann, Adam Wiggins, Peter van Hardenberg, Mark McGranaghan, Local-first software; April 2019 web essay; DOI 10.1145/3359591.3359737; accessed 2026-09-24 extracted; initial manual review; live run failed Local authority packet

Queued does not mean reviewed. Bibliography and hashes live in each workspace's source artifact and manifest. Preparation review records selection, provenance limits and remaining work. Claim IDs will resolve inside completed source reviews; preparation packets do not establish a pattern.

Source families to investigate

Family Representative sources Research purpose
Pattern languages Christopher Alexander, Hillside/PLoP literature Pattern form, relations, generative sequences
GUI architecture Martin Fowler, MVC/MVP/Presentation Model Presentation/domain/state separation
Unidirectional state Flux, Redux, Elm State transition and dependency direction
Hypermedia REST, HTML forms, HTMX Navigation, mutation, server projection
Rendering web.dev, framework docs, Patterns.dev CSR/SSR/SSG/hydration/islands/streaming
Local-first Ink & Switch and related work Local authority, sync, conflict handling
Distributed state CRDT/event sourcing/sync literature Reconciliation and replication
Modularity Feature-Sliced Design Feature boundaries and dependency rules
Organizational architecture Microfrontend literature Independent ownership/deployment
Quality WCAG, progressive enhancement, web performance Cross-cutting architectural forces

Catalog policy

Each source should eventually capture:

  • source identity,
  • date/version,
  • scope,
  • vocabulary used,
  • candidate patterns,
  • dominant forces,
  • assumptions,
  • contradictions,
  • known implementations,
  • evidence quality.

2026-09-24: initial authority-focused reviews are recorded as extracted. They have not passed a full-source or independent review gate. Live calls failed before any artifact generation. See AuthorityPilot for findings, execution evidence and limitations.