coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
frontend-patterns/research
History
tegwick ad6f8fa600 Ground conflict-copy candidate in Joplin and Obsidian evidence 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-25 02:04:30 +02:00
..
bench Ground conflict-copy candidate in Joplin and Obsidian evidence 2026-09-25 02:04:30 +02:00
candidates Ground conflict-copy candidate in Joplin and Obsidian evidence 2026-09-25 02:04:30 +02:00
cases Ground conflict-copy candidate in Joplin and Obsidian evidence 2026-09-25 02:04:30 +02:00
catalog Ground conflict-copy candidate in Joplin and Obsidian evidence 2026-09-25 02:04:30 +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 Record first authority investigation and preserve failed live-run evidence 2026-09-24 15:43:59 +02:00
reviews Ground conflict-copy candidate in Joplin and Obsidian evidence 2026-09-25 02:04:30 +02:00
README.md Set up source-grounded frontend research workflows with infospace-bench 2026-09-24 09:47:22 +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.