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

id	type	title	domain	repo	status	quality_dor	quality_dor_at	quality_dor_by	quality_dor_note	reviewed_at	reviewed_against_commit	owner	topic_slug	created	updated	state_hub_workstream_id
FEP-WP-0002	workplan	Validate the seed frontend pattern language	infotech	frontend-patterns	active	DoR-Ok	2026-09-24	codex	Self-review against work-item-dor; see readiness assessment below.	2026-09-24	c161369ad5	codex	canon	2026-09-23	2026-09-25	3350b7f2-375a-54e8-8f7c-3bf7c7c3af71

Validate the seed frontend pattern language

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. Schema reconciliation and source preparation began on 2026-09-24; full source investigation and the M1 evidence gate remain incomplete.

T01 and source extraction in T02 can proceed independently. T03 admission requires both. Per the 2026-09-25 optimization direction, a provisional synthetic T03 walkthrough may proceed with explicit evidence gaps while T02 continues; this does not relax canonical admission. Use research/plan/ResearchProtocol.md; track Q01–Q04 in the question ledger.

Reconcile the metadata contract

id: FEP-WP-0002-T01
status: done
priority: high
state_hub_task_id: "e59295dd-a087-5dbc-9bb2-230488c48e96"

Resolve relation spelling, force and pattern IDs, prerequisite target types, multi-scale representation and editorial status versus evidence maturity. Done when schema and template agree and a worked example resolves every reference.

Establish traceable source evidence

id: FEP-WP-0002-T02
status: progress
priority: high
state_hub_task_id: "0eb32b3e-07d6-5e16-a735-7d75d9dace83"

Complete the first source case and a contrasting local-first source review. Record source identity, URL, date/version, claim references, interpretations and counterexamples. Reconcile README maturity claims with the evidence.

Validate a connected seed corpus

id: FEP-WP-0002-T03
status: progress
priority: medium
state_hub_task_id: "54940b04-1d0f-5bff-98d4-be290eca8048"

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.

Readiness assessment

Self-reviewed by codex against State Hub policies/work-item-dor.md on 2026-09-24. Outcome: DoR-Ok for the plan structure; child tasks remain to be assessed before execution.

• Scope: metadata reconciliation, two contrasting source reviews, 6–10 draft patterns and VC-01/VC-02. Broad coverage, tooling implementation and real-repo validation are outside this cycle and belong to FEP-WP-0003/0004.
• Owner and repository: codex in frontend-patterns. No external intake; this follows the repository review and the user's research-program instruction.
• Dependencies: scaffold and templates are committed. No known blocker prevents T01 or source discovery. T03 depends on T01/T02; inaccessible sources must be reported and alternatives assessed rather than evidence invented.
• Execution boundary: documentation and read-only public-source research, with ordinary Git/State Hub synchronization. Deployments, purchases and third-party messaging are outside scope. This plan does not schedule background execution.
• Verification: schema/template agreement, traceable claims and references, two walkthrough reviews, explicit counterevidence and the M1 acceptance review.
• Done-condition: the phase acceptance section above; hypotheses may be rejected or deferred with reasons rather than falsely confirmed to close a task.

Source investigation tooling

FEP-WP-0005 established research/bench/README.md and scripts/research_bench.py. Use one isolated workspace per source excerpt, review original-source-grounded claims/candidates/relations/critique, and follow research/bench/Admission.md. The fixture run is synthetic and does not complete any task in this workplan. T02 still owns source acquisition/review; T03 owns cross-source synthesis and cases.

2026-09-24 execution evidence

T01 completed: canon/PatternSchema.md, canon/vocabulary.yaml and the pattern template agree on identities, scales, force keys, statuses, evidence and typed relations. research/examples/schema-contract.yaml exercises resolved references; make schema-test verifies it. Review: research/reviews/SchemaAndSourcePreparation.md.

T02 in progress: SRC-0001/SRC-0002 verified and indexed. Two original-passage workspaces and four-call preflight plans are prepared under research/bench/infospaces/. No live generation or complete source review is claimed. Selection of model/provider, source-grounded investigation, broader case review and counterexamples remain.

First source investigation — 2026-09-24

Attempted the two four-stage source investigations with Gemini 2.5 Flash through OpenRouter. Both stopped at the first call; a separate authentication probe returned HTTP 401. No provider-generated research artifacts exist. The existing workload credential route does not apply to a generic workstation client; a correct route or provider was requested from the user. Failed receipts are retained.

Manual authority-focused reviews are in research/cases/CarniatoGrandUnifyingArchitecture.md and research/cases/LocalFirstAuthority.md; synthesis/dispositions are in research/reviews/AuthorityPilot.md. Source catalog states are extracted, not fully reviewed. Added safe error status/model recording to the adapter and a regression check preventing raw sensitive diagnostic detail from entering receipts.

T02 remains progress: broader evidence and independent known uses are still needed. Live reruns specifically depend on an authorized working credential; manual research can continue. No failure of the research hypothesis is inferred from provider failure.

llm-connect execution — 2026-09-24

User clarified that live execution must use llm-connect. Replaced direct OpenRouter execution with the llm-connect service contract; no workstation credential required. Service model/usage/finish reason and safe failure receipts are retained. Carniato -03 completed four stages; Carniato -02 and local-first -02 were truncated and rejected. Review: research/reviews/LLMConnectPilot.md. No proposal admitted.

T02 remains progress and owns the next bounded steps: resolve local-first truncation with explicit research settings; tighten prompts and checks around unsourced known uses, recurrence and claim-vs-pattern relation targets; continue source evidence. These replace the earlier workstation-credential dependency. T03 remains todo.

Bounded pipeline refinement — 2026-09-25

T02: tightened prompts, added conservative evidence-ledger/relation screening and captured-failure regression checks. The historical Carniato proposal is blocked; checks never grant semantic admission. See research/reviews/ResearchPipelineRefinement.md. A fresh local-first -03 run through llm-connect with requested low reasoning and 6,000 completion tokens again truncated at claims (one service request, 6,525 total tokens). No further retry or pattern admission. T02 remains progress.

Next bounded action: establish effective service reasoning settings and token breakdown, or a documented research profile, before another live attempt. Then verify the revised prompts in a complete run and perform editorial review. Missing provider diagnostics remain an execution limitation, not a research conclusion.

Truncation diagnosed and bounded investigation completed — 2026-09-25

T02: live diagnostics confirmed reasoning_effort is dropped before the provider; rejected -05 output revealed pathological Markdown table padding, not reported reasoning token use. Switched to compact records. Local-first -06 completed four stages through llm-connect, passed structural screening, and yielded a reviewed negative finding: this packet does not justify a pattern. No pattern admission. Evidence: research/reviews/TruncationDiagnosis.md and LocalFirstAdmissionScreen.json.

The previous effective-settings diagnostic action is complete; no service deployment or credential change was needed. T02 remains progress for expanded source evidence: located persistence, synchronization, conflict and independent implementation passages. T03 remains todo for comparative walkthroughs and the connected seed corpus.

Evidence expansion and candidate synthesis — 2026-09-25

T02: indexed SRC-0003–0007 official Joplin/Obsidian documentation and expanded SRC-0002 reading. Two llm-connect investigations completed all four stages. Joplin structural screen passed; Obsidian claim-ID relations were blocked and editorially rejected. Merged the useful mechanisms into research/candidates/ConflictCopy.md with hypothesis maturity and two documented uses; no canonical admission. Full review and receipts: research/reviews/LocalFirstEvidenceExpansion.md.

T02 remains progress for precise durability, independent runtime validation and quality constraints. T03 remains todo; prepare the connected drafts and execute the planned restart/reconnect comparison after the source-evidence gate. Do not count multiple documentation pages from one application as independent implementations.

Application-driven optimization — 2026-09-25

Implemented conditional-v1 stage execution, pre-propagation structural gates, deterministic review handoff, explicit fingerprinted reuse and per-run call/cache/ structural-rejection metrics. Editorial corrections use a separate named record; unknown is not zero. Synthetic smoke/replay verify two versus zero new adapter calls. No new paid inference or broad source collection was needed.

T03 is now progress: research/walkthroughs/VC02-OfflineFieldNotes.md contains the first synthetic trace, single-writer branch, baseline comparison and self-review. Four connected research drafts remain hypotheses. Decision usefulness beyond baseline is unknown; no runtime validation, canonical admission or M1 completion claimed.

Targeted next tasks: T02 obtain storage atomicity and receiver retry/ancestry evidence; T03 define accessible conflict-review acceptance and execute the VC-01 contrast. See research/reviews/ResearchOptimization.md for checks, corrections and dispositions.

Transactional evidence and contrast — 2026-09-25

T02 remains progress: SRC-0008–0012 add Kubernetes/GitLab concurrent-write behavior, Stripe bounded retry identity and React Router projection/feedback evidence. One bounded Kubernetes investigation completed through llm-connect (two service calls, 2,849 reported tokens), with separate editorial review. API documentation is not proof of complete frontend uses. Four new hypothesis drafts bring the developed research set to eight; no canonical admission or M1 completion.

T03 remains progress: VC-01 now includes rejection, domain failure, unknown outcome, late refresh, keyboard/privacy requirements, a single-writer branch and baseline comparison. VC01-VC02-Comparison records shared concerns and differing acceptance boundaries. Usefulness beyond plain narrative remains unknown.

Next bounded actions under T02: inspect two actual frontend implementations for draft retention and unknown-outcome recovery at exact revisions. Under T03: obtain independent review of both cases and their baselines. Existing offline atomicity, receiver ancestry/retry and accessible reconciliation evidence gaps remain active. Evidence: research/reviews/TransactionalEvidenceExpansion.md.