frontend-patterns/research/README.md
tegwick d7b2ea49ce Inspect frontend recovery implementations and refine operation lifecycles
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-25 10:41:59 +02:00

34 lines
1.7 KiB
Markdown

# 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](plan/ResearchProgram.md) for phases and current work records.
2. Follow [ResearchProtocol](plan/ResearchProtocol.md) for evidence and promotion.
3. Select a question from [OpenQuestions](plan/OpenQuestions.md) and a bounded task.
4. Use [ValidationCases](plan/ValidationCases.md) 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](bench/README.md).
Its checked-in fixture verifies the pipeline and is excluded from research evidence.
Current contrast: [VC-01 server-validated editing](walkthroughs/VC01-TransactionalAdministration.md), [VC-02 offline editing](walkthroughs/VC02-OfflineFieldNotes.md), and [cross-case assessment](reviews/VC01-VC02-Comparison.md).
Latest implementation evidence: [frontend recovery](reviews/FrontendRecoveryImplementations.md) and [walkthrough correction review](reviews/RecoveryWalkthroughReview.md).