Establish phased research program with evidence and validation gates

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9

workplans/FEP-WP-0002-seed-language-validation.md

@@ -4,17 +4,23 @@ type: workplan
 title: "Validate the seed frontend pattern language"
 domain: infotech
 repo: frontend-patterns
-status: proposed
+status: ready
 owner: codex
 topic_slug: canon
 created: "2026-09-23"
-updated: "2026-09-23"
+updated: "2026-09-24"
 state_hub_workstream_id: "3350b7f2-375a-54e8-8f7c-3bf7c7c3af71"
 ---
 
 # Validate the seed frontend pattern language
 
-Follow-up from `REVIEW.md` and FEP-WP-0001. This records future research.
+First executable cycle of `research/plan/ResearchProgram.md`, following `REVIEW.md`
+and FEP-WP-0001. Readiness review on 2026-09-24: scaffold is present, source and
+walkthrough templates exist, VC-01/VC-02 are defined, and deliverables below are
+bounded. No research execution or evidence gate is claimed complete.
+
+T01 and source extraction in T02 can proceed independently. T03 requires both.
+Use `research/plan/ResearchProtocol.md`; track Q01–Q04 in the question ledger.
 
 ## Reconcile the metadata contract
 
@@ -55,3 +61,12 @@ Author a small connected pattern set and exercise it in server-authoritative and
 local-first scenarios. Show forces, alternatives, ordering rationale, resulting
 contexts and failure modes. Record gaps, then define the minimum metadata
 validator and graph export needed by these examples.
+
+
+## Phase acceptance
+
+Produce 6–10 connected draft patterns, complete VC-01 and VC-02, and write
+`research/reviews/M1-SeedReview.md` with evidence for each M1 criterion. Include
+rejected or merged candidates and any source-access limitations. Retain hypothesis
+maturity where evidence is incomplete. Handoff broader investigations to FEP-WP-0003;
+metadata tooling and empirical evaluation are tracked in FEP-WP-0004.

workplans/FEP-WP-0003-contrasting-schools.md

@@ -0,0 +1,48 @@
+---
+id: FEP-WP-0003
+type: workplan
+title: "Challenge the language across architectural schools"
+domain: infotech
+repo: frontend-patterns
+status: proposed
+owner: codex
+topic_slug: canon
+created: "2026-09-24"
+updated: "2026-09-24"
+---
+
+# Challenge the language across architectural schools
+
+Part of `research/plan/ResearchProgram.md`. Phase prerequisite: FEP-WP-0002's evidence
+gate. This is planned follow-up, not an active background execution request.
+Individual task descriptions identify any work that can start earlier.
+
+## Compare the six research streams
+
+```task
+id: FEP-WP-0003-T01
+status: todo
+priority: high
+```
+
+Build a source coverage matrix for streams A–F in ResearchProgram.md. Complete a primary-source review for each stream, including disagreements and independent known uses. Q05 and Q06 guide the comparison; source counts alone do not establish coverage.
+
+## Complete contrasting architecture walkthroughs
+
+```task
+id: FEP-WP-0003-T02
+status: todo
+priority: high
+```
+
+After the M1 review, complete VC-03 through VC-06 using the walkthrough template. Mark coverage of VC-07 through VC-10 with evidence and gaps. Revise sequences and architecture decompositions where constraints break the current model.
+
+## Review pattern and ontology changes
+
+```task
+id: FEP-WP-0003-T03
+status: todo
+priority: medium
+```
+
+Record retain/merge/split/reject decisions, revised relations, quality constraints and counterexamples. Write research/reviews/M2-CoverageReview.md against the M2 gate; hand unresolved questions into live work records before closing.

workplans/FEP-WP-0004-reference-surface.md

@@ -0,0 +1,48 @@
+---
+id: FEP-WP-0004
+type: workplan
+title: "Evaluate retrieval and real repository applicability"
+domain: infotech
+repo: frontend-patterns
+status: proposed
+owner: codex
+topic_slug: canon
+created: "2026-09-24"
+updated: "2026-09-24"
+---
+
+# Evaluate retrieval and real repository applicability
+
+Part of `research/plan/ResearchProgram.md`. Phase prerequisite: FEP-WP-0003's evidence
+gate. This is planned follow-up, not an active background execution request.
+Individual task descriptions identify any work that can start earlier.
+
+## Validate metadata and export the graph
+
+```task
+id: FEP-WP-0004-T01
+status: todo
+priority: high
+```
+
+After the schema and seed examples pass M1, implement the smallest validator/exporter needed to check unique IDs, allowed values, relation targets and evidence references. Add meaningful invalid and valid fixtures; preserve prose and source provenance.
+
+## Evaluate held-out retrieval cases
+
+```task
+id: FEP-WP-0004-T02
+status: todo
+priority: medium
+```
+
+After M2, freeze a corpus revision and evaluate at least six unseen prompts following ValidationCases.md. Record expected alternatives, abstentions, unsupported claims and missed constraints; compare with manual navigation. Address Q07.
+
+## Test against real repository revisions
+
+```task
+id: FEP-WP-0004-T03
+status: todo
+priority: medium
+```
+
+Study at least two contrasting accessible repositories at recorded revisions. Separate observed implementation from inferred intent. Write research/reviews/M3-EmpiricalReview.md, publish limitations, and hand remaining findings into live work records.