frontend-patterns/SCOPE.md

# 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-25. The adapter
has deterministic integration tests, completed bounded live investigations through
llm-connect, and two synthetic architecture walkthroughs. Eight developed research
drafts remain hypotheses; none is canonically admitted. 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.