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

Preserve initial frontend pattern language research scaffold

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-24 07:55:34 +02:00
parent 017ad6ea17
commit 2a5dabdc85
43 changed files with 2030 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

28
research/plan/OpenQuestions.md Normal file
View file

@ -0,0 +1,28 @@
# Open Questions
## Core ontology
- Is `Authority → Projection → Affordance` a better primary axis than traditional "state management" terminology?
- Should `Mutation` represent intent, transport, state transition, or be split?
- Is `Reconciliation` independent enough to be a first-class responsibility?
- Should `Communication Window` become a canonical dimension?
## Pattern language
- What qualifies as a pattern rather than a technique?
- How much implementation detail belongs in canonical patterns?
- How do we represent patterns that only make sense at one scale?
- How should pattern relations be validated?
## Agentic use
- Which metadata is necessary for useful pattern retrieval?
- Should the pattern graph be exported as JSON/YAML/RDF?
- Can force matching be made quantitative without creating false precision?
- Can architecture review be expressed as unresolved-force detection?
## Evidence
- What makes a frontend pattern "established"?
- Should known uses be manually curated or automatically mined?
- How should contradictory source claims be represented?