frontend-patterns/SCOPE.md
tegwick fc8a7dbb49 Set up source-grounded frontend research workflows with infospace-bench
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-24 09:47:22 +02:00

38 lines
1.5 KiB
Markdown

# SCOPE
## Purpose
Develop a framework-independent frontend architecture pattern language for human
and agent reference, following the preliminary direction in `INTENT.md`.
## In scope
- `canon/`: responsibilities, forces, scales, relations and the pattern schema.
- `patterns/`: patterns with context, evidence, trade-offs and failure modes.
- `research/`: sources, interpretations, candidate concepts and counterexamples.
- `sequences/` and `architectures/`: decisions and configurations through patterns.
- `technologies/`: descriptive mappings to implementation options.
- `templates/`: authoring structures and future metadata validation.
## Out of scope
- Building or operating a frontend application or framework.
- Ranking frameworks or prescribing a universal architecture.
- Treating candidate lists or unsourced interpretations as established evidence.
## Current state
Research scaffold with an infospace-bench adapter as of 2026-09-24. The adapter
has deterministic integration tests and a synthetic pilot; live source investigation
is pending. No frontend application runtime exists. See `research/bench/README.md`,
`REVIEW.md` (the initial review) and `workplans/` for follow-up work.
## Registration
- Repository: `frontend-patterns`
- Category: `research`
- Domain / topic: `infotech / canon`
- Workplan prefix: `FEP-WP`
The topic groups this research with semantic coordination work; it does not imply
that the proposed language is an adopted fleet standard.