coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
frontend-patterns/research
History
tegwick 96d11431dc Expand transactional editing evidence and compare authority cases 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-25 10:32:13 +02:00
..
bench Expand transactional editing evidence and compare authority cases 2026-09-25 10:32:13 +02:00
candidates Expand transactional editing evidence and compare authority cases 2026-09-25 10:32:13 +02:00
cases Ground conflict-copy candidate in Joplin and Obsidian evidence 2026-09-25 02:04:30 +02:00
catalog Expand transactional editing evidence and compare authority cases 2026-09-25 10:32:13 +02:00
compendium Preserve initial frontend pattern language research scaffold 2026-09-24 07:55:34 +02:00
concepts Preserve initial frontend pattern language research scaffold 2026-09-24 07:55:34 +02:00
examples Reconcile pattern metadata and prepare contrasting primary-source inputs 2026-09-24 15:23:06 +02:00
plan Expand transactional editing evidence and compare authority cases 2026-09-25 10:32:13 +02:00
reviews Expand transactional editing evidence and compare authority cases 2026-09-25 10:32:13 +02:00
walkthroughs Expand transactional editing evidence and compare authority cases 2026-09-25 10:32:13 +02:00
README.md Expand transactional editing evidence and compare authority cases 2026-09-25 10:32:13 +02:00

README.md

Research

Research material supports the canon but is kept separate from canonical patterns.

The structure follows the C3 research deliverable model where useful:

  • catalog/ — normalized inventories and indices.
  • compendium/ — explanatory synthesis of established knowledge.
  • concepts/ — emerging models and hypotheses.

Additional directories:

  • cases/ — focused analysis of articles, systems or architectural schools.
  • plan/ — research program, methods and open questions.

Research material may be provisional.

Promotion into the canon should happen only after the concept has been reconciled with competing models and tested against multiple frontend architectures.

Start a research session

  1. Read ResearchProgram for phases and current work records.
  2. Follow ResearchProtocol for evidence and promotion.
  3. Select a question from OpenQuestions and a bounded task.
  4. Use ValidationCases and the templates in templates/.
  5. Update catalogs and question outcomes, then commit and sync the workplan status.

Execute bounded source investigations with the research bench. Its checked-in fixture verifies the pipeline and is excluded from research evidence.

Current contrast: VC-01 server-validated editing, VC-02 offline editing, and cross-case assessment.