frontend-patterns/workplans/FEP-WP-0007-language-v01-preview.md

---
id: FEP-WP-0007
type: workplan
title: "Package a useful language 0.1 research preview"
domain: infotech
repo: frontend-patterns
status: finished
owner: codex
topic_slug: canon
created: "2026-09-27"
updated: "2026-09-27"
state_hub_workstream_id: "1682a82f-3c70-530f-a444-78752deb0ff6"
---

# Package a useful language 0.1 research preview

Proposed from the user-requested [workplan audit](../history/2026-09-27T021659+0200-workplans-v01-readiness.md).
This is a finite packaging and editorial review plan, not a declaration of release or
an evidence-gate replacement. Existing M1/M2/M3 and canonical-admission criteria remain
unchanged. The published corpus may contain hypotheses with stable CAND identities;
publication version 0.1 is separate from PatternSchema 0.1 and evidence maturity.

## Reconcile the release subset and milestone assessments

```task
id: FEP-WP-0007-T01
status: done
priority: high
state_hub_task_id: "3417824a-1416-58d0-841b-7ec0ccbb7021"
```

Work with WP-0002 T02/T03 and WP-0003 T03 to produce explicit pass/revise/defer reviews
of source readiness, the connected core and ontology. Start with the eight existing
transactional/local-first recovery drafts; retain other candidates as qualified
extensions. Decide whether Conflict Copy and Explicit Reconciliation need separate
retrieval, with reasons. Record the subset in a release manifest; do not move drafts
into patterns/ or assign FEP IDs without their admission review.

Done when each core record has context, forces, proposed solution, alternatives,
consequences, evidence and gaps checked, and the milestone review distinguishes
editorial readiness from unmet empirical gates. Do not claim human validation from
model review. Keep source assessment ownership in WP-0002, ontology in WP-0003.

## Publish the human reference paths

```task
id: FEP-WP-0007-T02
status: done
priority: high
state_hub_task_id: "e71c2f74-dbea-5ab0-ae8c-4b247ec0f38f"
```

After T01, create a concise starting guide, two decision sequences grounded in VC-01/02,
and at least one evidence-qualified implementation mapping for each core case. Index
all seventeen candidates without presenting unreviewed seed names as developed records.
Document compatible configurations, rejected alternatives and unsupported needs.
Reuse and link existing source/candidate records; avoid divergent duplicate contracts.

Done when a reader can move from either supported problem to a small configuration,
its implementation options and its failure/evidence limits without reading the research
history. Provisional VC-03/06 remain clearly labeled extensions; no complete coverage
claim for the remaining cases. No standalone frontend application required.

## Validate candidate reference export and development navigation

```task
id: FEP-WP-0007-T03
status: done
priority: medium
state_hub_task_id: "94010e3e-eddf-56c7-996a-fc70d7c56e38"
```

After T01/T02, export the smallest useful candidate-reference representation: stable
CAND identities, families/scales, provisional classification, proposed typed relations,
rationale and evidence locators or explicit unknowns. Validate identities, endpoints,
allowed vocabulary and references. Test invalid references and malformed records.
This candidate surface is separate from WP-0004 T01's M1-gated canonical graph.

Record at least six disclosed development queries across the two supported contexts,
including incompatible constraints, missing context and an unsupported need. Verify
reference paths, alternatives and abstention boundaries; fix misleading claims before
release. These are development checks, not the M2-gated held-out M3 evaluation or
independent human usefulness proof. Use llm-connect for any live inference; model
execution is optional if deterministic/manual checks answer the reference question.

## Review and record the 0.1 preview

```task
id: FEP-WP-0007-T04
status: done
priority: high
state_hub_task_id: "a554e327-972b-580b-8dec-151d7a38bda6"
```

After T01–T03, write a release review and notes, pin the corpus revision and publish
the evidence profile, supported contexts and known limits. Check the human entry
points, exports and applicable test targets. Record reviewer role; zero unsupported
maturity/production/usefulness claims is required. Define how later versions record
corrections and counterexamples. Do not use catalog size as acceptance.

Only mark the preview ready when the review passes its bounded contract. No tag or
release claim from this proposed plan alone. Existing research work stays open unless
its own criteria are met; before finishing this workplan, hand residual release issues
to explicit live tasks with origin references. The empirical owners remain WP-0002
T03, WP-0003 T01/T02/T03, WP-0004 T01/T02/T03 and WP-0006 T03.

## Completion — 2026-09-27

The [release review](../reference/0.1/ReleaseReview.md) passes the bounded preview
contract. START.md, both core sequences, mechanism mappings, the seventeen-record
catalog and pinned candidate export are complete. Eight disclosed development cases
include incompatible constraints, missing context and unsupported needs. No live
inference, independent human review, canonical admission or M1/M2/M3 pass is claimed.

Validation: 44 tests passed (9 preview, 2 schema, 33 bench/admission); synthetic
bench plan, export freshness, evolution and classification checks passed. Changed
Markdown relative file links and whitespace checked. Existing empirical obligations
remain in the manifest's live task references. WP-0003 T04 receives storage/receiver
validation with explicit origin FEP-WP-0002-T02. No additional packaging residual
was identified; ongoing research ownership remains unchanged.