coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Track pattern evidence and ongoing language learning

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-27 00:00:39 +02:00
parent f273a190f0
commit b8a03a3bee
16 changed files with 3223 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

19
research/plan/ResearchProgram.md
View file

@ -1,6 +1,6 @@
# Frontend Patterns Research Program
Status: planned · Program established: 2026-09-24
Status: ongoing · Program established: 2026-09-24
Start with [Research Protocol](ResearchProtocol.md), the
[executable research bench](../bench/README.md), then the
@ -388,3 +388,20 @@ Useful progress means improving one or more of:
- evidence quality,
- applicability across architectures,
- retrieval quality for humans and agents.
## 13. Continuous learning and transparent evolution
Milestones are finite review boundaries within an ongoing research program. Passing
a gate does not finish the language. Evidence can narrow, supersede or demote a
pattern; preserve those changes as part of the knowledge base.
[FEP-WP-0006](../../workplans/FEP-WP-0006-language-evolution.md) establishes the
[evidence baseline and evolution method](../evolution/README.md). Its generated
[report](../evolution/EvolutionReport.md) separates current maturity, support tiers,
coverage, usefulness and learning outcomes. Early rapid learning and later diminishing
returns are testable expectations, not a prescribed curve or catalog-size target.
Measure prospective comparable cycles, retain unknown historical effort, and record
corroboration separately from consequential revisions. Broaden contexts when they
expose new decisions; improve structure when ambiguity prevents use; seek independent
validation when mechanisms stabilize. Keep fresh evaluation tasks separate from
consumed development anchors, including the immutable language pilot.

16
research/plan/ResearchProtocol.md
View file

@ -64,3 +64,19 @@ support or reject the current hypothesis; record remaining uncertainty. Do not
stretch source claims to meet a pattern-count target. Preserve superseded conclusions
through Git history and link the replacement. Reopen a conclusion when new evidence
invalidates a stated assumption.
## Evolution record at cycle close
Register a bounded question with the [learning-cycle template](../../templates/LearningCycle.md)
before execution. Follow the [evolution method](../evolution/README.md): append the
outcome (including corroboration or inconclusive results), record effort or explicit
unknowns, update affected evidence profiles, and run `make evolution-report
evolution-check evolution-test`. Capture a snapshot at the review boundary after
candidate changes are committed. Preserve superseded conclusions and failed trials.
Research milestones close bounded work; the language keeps learning. Compare returns
only across prospective cycles with comparable stream/protocol/question scope and
effort accounting. Review at least three such cycles before discussing a trend; that
review is not proof of a plateau. Do not pool historical assertion or citation counts
as discoveries. Human validation, independent recurrence and demonstrated usefulness
remain separate obligations from metadata correctness.