38 lines
1.3 KiB
Markdown
38 lines
1.3 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 as of 2026-09-23. No application runtime, dependency manifest,
|
||
|
|
build pipeline or automated test suite is present. See `REVIEW.md` for findings
|
||
|
|
and `workplans/` for tracked 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.
|