frontend-patterns/workplans/FEP-WP-0008-use-driven-improvement.md

id	type	title	domain	repo	status	lane	owner	topic_slug	created	updated	state_hub_workstream_id
FEP-WP-0008	workplan	Close the ecosystem reuse and improvement loop	infotech	frontend-patterns	blocked	blue	codex	canon	2026-09-27	2026-10-19	9f719719-ed4e-5c57-a62f-855fe1876e17

Close the ecosystem reuse and improvement loop

User-requested 2026-09-27: make frontend-patterns reusable and valuable across the existing ecosystem, and turn observed use into improvement with only monthly human progress review and signoff for decisions changing the loop. Reviewed against frontend-patterns 88fee7c and local reuse-surface/activity-core/Glas/rein contracts. Operating design is the implementation contract.

Exactly three delivery actions. Implementation has started with the local discovery entry; background reporting is enabled; automatic pattern-editing execution is not enabled. Existing M1/M2/M3 evidence gates remain intact. Qualified reference consumption and use-driven research may proceed before those gates under the user's instruction. This is not a request for another up-front approval round.

Publish and connect the reusable reference

id: FEP-WP-0008-T01
status: wait
blocking_reason: "Needs hosted registration access and common-template integration into an actual eligible consumer with a pinned decision note. Qualified draft reference use does not require M1."
priority: high
lane: blue
state_hub_task_id: "453fc06b-be70-5913-a816-161cabe9a0a1"

One capability entry and index for capability.infotech.frontend-pattern-language, pointing to START.md, the versioned JSON/catalog and two core sequences. Keep the reference informational, hypotheses explicit, and consumer reliability unknown. Verify schema/index consistency, stable raw publication and hosted federation discovery. Use existing owner credential routing if registration requires access; never request or copy tokens in work records.

Before modifying current research profiles, separate old preview validation from live profile/classification state: read its pinned inputs from Git, validate current research separately. Add immutable version selection/current pointer and test that a later candidate/profile change neither rewrites nor breaks validation of the old release.

Integrate one short query/read/cite/record instruction through the common consumer template owner, first in one eligible real frontend repository. Select by actual task need, not an invented demo. Correctly retrieve a supported context and abstain on an unsupported one. Add a contrasting consumer when actual work supplies it.

Done: published/discoverable reference plus first real pinned decision note, and frozen release validation survives legitimate new research. Registry entry/index are prepared in this design session; hosted registration and consumer integration remain open.

Residual acceptance received from FEP-WP-0010 (2026-10-04): the verified local lookup/citation helper and consumer commands remove local reference-navigation preparation. T01 still owns hosted registration, common-template-owner integration into an actual eligible frontend task and its first pinned decision note. No fixture or audit of this repo supplies that receipt.

Capture evidence of use and outcomes

id: FEP-WP-0008-T02
status: wait
depends_on: [FEP-WP-0008-T01]
blocking_reason: "Local producer and collector contracts are implemented; needs an actual consumer-owned automatic closeout/index hook, authorized enrollment, real use plus linked outcome and delayed-artifact refresh. See docs/DependencyRequirements.md."
priority: high
lane: blue
state_hub_task_id: "49be8a8e-eaaf-5f1c-b4cd-f0c4dbac9823"

Implement the small receipt contract in templates/PatternUseReceipt.yaml as a versioned schema/validator, automatic consumer closeout hook and deterministic collector. Pin producer/source and reference revisions; record considered/selected IDs, constraints, changed decision, applied/adapted/rejected/no-match, reported/observed outcome and evidence. Empty IDs, delayed outcomes and unknowns are valid. Raw private content stays at source.

Use immutable events and explicit predecessor digests. Idempotent duplicate ingest, quarantined collisions, safe relative paths/allowlisted source access and no execution of feedback instructions. Keep fixture and real-use streams separate. Aggregate by originating use/context, not number of comments or model runs. Reuse registry telemetry only within its existing schema; it does not carry helpfulness evidence.

Done: at least one real use and linked outcome; positive, negative, mixed, unknown, rejected/no-match, delayed/corrected, duplicate and malformed paths tested as fixtures. No fabricated real outcome to close the task. Pending cases get one automated artifact refresh after 14 days and remain unknown after 30; no manual survey dependency.

Residual acceptance received from FEP-WP-0010 (2026-10-04): the local producer now fills verified release pins and writes a new schema-v1 JSON/YAML event with an exact index digest; its synthetic event passes activity-core's actual validator. T02 retains the consumer-owned automatic closeout invocation/index commit, authorized enrollment, real use plus linked inspectable outcome, and delayed-artifact refresh. Collector validation is not outcome truth or a producer-origin verification claim. Existing collection remains with activity-core; no second collector or fictional use was added.

Run bounded improvements and monthly review autonomously

id: FEP-WP-0008-T03
status: wait
depends_on: [FEP-WP-0008-T02, GLAS-WP-0012, HFACT-WP-0001, ACTIVITY-WP-0032-T05, ACTIVITY-WP-0041-T03]
blocking_reason: "Reporting cadence is verified. Needs real consumer outcomes, admitted budget-enforced improvement execution and authenticated publication/rollback proof."
priority: high
lane: blue
state_hub_task_id: "f823587c-727d-515a-974d-401719420ce5"

Implement deterministic signal grouping/priorities and one bounded weekly investigation, using existing learning cycles, llm-connect and a separate model review context. Connect activity-core scheduling to a verified rein/Glas profile with scoped repository grants; prove an executing worker, not just generated tasks. Enforce aggregate time/call/token budgets before enabling. No unrestricted legacy fallback or self-expanding permissions.

Publish reversible qualified corrections only after source/reproduction checks, regression and abstention cases, model review and reference validation. Preserve prior versions and verify published readback. Keep low evidence/inconclusive outcomes rather than force an edit. Canonical/maturity/schema policy decisions wait in the monthly packet; human validation remains an evidence label, not a routine workflow prerequisite.

Daily intake, Tuesday weekly cycle, monthly first-day report and limits are specified in the operating design. The first review packet is due 2026-10-01 even if activation remains incomplete. Include outcome denominators, unknowns, meaningful changed decisions, costs, failures and at most three policy decisions with no-response defaults. Human attention target is one 20-minute monthly review; no routine case approval or feedback entry.

Done: one real unassisted scheduled end-to-end cycle and an automatically produced monthly packet; duplicate delivery, restart, rejected review, denied mutation, provider failure and rollback have recorded proofs. Prove no-data runs skip model calls and a blocked worker still yields visible health. Where no content change is warranted, corroboration is a valid real result; exercise publication/rollback separately with labeled fixtures. Existing owner runtime readiness/access dependencies must be tracked here with exact handoff references if discovered; do not ask the user to manually run each cycle.

Acceptance and ownership

Deliver a closed chain: discover → consume → observe → investigate → verify → publish → revisit. A plan, registry entry, generated tasks or a cron file alone is insufficient. Zero external consumer evidence is the starting baseline, not a measured success rate.

WP-0002 keeps seed/admission and independent-human evidence; WP-0003 keeps architectural research and recovery assumptions; WP-0004 keeps later held-out/canonical evaluations; WP-0006 keeps the learning ledger/comparability protocol. This plan owns instrumentation and operational closure. Feedback-led questions take priority over another unsolicited source-expansion cycle, except corrections needed to keep existing reference truthful.

Before finishing, hand unresolved operating issues to live records with origin: residual and origin_ref: FEP-WP-0008; preserve empirical owners above.

Design establishment — 2026-09-27

State Hub decision a4d295ae-eeaf-4492-bfe0-feac6815a7b8 records the operating design under the user mandate, not runtime activation or independent human validation. Local capability entry passes reuse-surface validation; reference, evolution and classification checks pass, and changed Markdown links/whitespace were checked. The receipt template is a draft contract; its executable schema/collector belong to T02.

Activity-core setup — 2026-09-27

Domain-owned daily/weekly/monthly definitions and the empty consumer roster are prepared. ACTIVITY-WP-0040 owns the tested read-only collector, worker overlay and projected definitions. See runtime status. Definitions remain disabled pending the estate deployment path and live sink verification. GLAS-WP-0012 / HFACT-WP-0001 own the unverified execution profile; no fallback is enabled. T02/T03 remain in progress: prepared schedules and reports do not satisfy the real-consumer, admitted execution or publication acceptance criteria.

Reporting activated — 2026-09-27

The founder approved the scoped direct deployment exception (decision e5dd02cb-b5b2-45c8-a600-748ea2ffd31b). Three report sinks passed manual production checks; all three Temporal schedules are active, with no drift; the daily one-shot scheduled smoke completed and posted report c5446c0a-125b-4703-b964-006aaef46241. First natural cadence observations remain pending. Evidence. ACTIVITY-WP-0041 is the live follow-up for eliminating deployment exceptions through GitOps adoption and standing bounded release authority. The reference still has zero enrolled consumers, and no pattern-editing executor is enabled. T01/T02/T03 stay in progress against their original end-to-end acceptance.

Deployment exception follow-up implemented — 2026-09-27

ACTIVITY-WP-0041-T01 is complete: tested CI publication, pinned frontend projection, registry digest deployment and readback. RPF-WP-0048-T01 adopted nine runtime resources into scoped ArgoCD. All deployments are ready, all three definitions remain enabled, and the post-release scheduled smoke passed. See release evidence.

Healthy observation runs from 2026-09-27T13:38:21Z for at least 24 hours. Automated sync remains off; authenticated receipt/identity and failed-health rollback proof remain in ACTIVITY-WP-0041-T03. Digest-aware registry retention is tracked by RPF-WP-0048-T03; current baseline tags are protected. Reporting is operational; consumer enrollment and admitted pattern-editing execution remain unfinished.

Closeout audit — 2026-09-27

Local frozen-publication prerequisite in T01 is complete: release registry, explicit version selection and Git-pinned corpus/package reads isolate old exports from legitimate current-research edits. Regression tests exercise current research changing independently, stale live profiles and altered published artifacts.

Workplan blocked; T01/T02/T03 wait on their end-to-end dependencies. T01 needs hosted discovery and common-template-owner integration into an actual eligible frontend task, including its first pinned decision note. T02 needs the producer closeout hook and real use plus linked outcome; activity-core owns the existing executable event validator and deterministic collector. The roster is still empty. Do not invent a demo consumer or copy its fixtures into the real stream. Reopen these tasks when an eligible actual consumer and the template integration are available.

T03 needs an admitted, budget-enforced pattern-edit executor (GLAS-WP-0012 / HFACT-WP-0001), authenticated standing release/rollback proof (ACTIVITY-WP-0041 T03), and a real unassisted cycle with monthly packet. Reporting and collection are already operational; their three schedules remain enabled. The first monthly packet remains due October 1; missing consumer/executor evidence must be reported as such. This audit does not disable schedules or conflate the reporting worker with mutation authority. Existing owner work records retain all dependencies; no replacement workplan is opened.

Dependency and cadence recheck — 2026-09-28

T01/T02/T03 remain wait and workplan blocked. Consumer roster is still empty; ACTIVITY-WP-0041 T02/T03 and GLAS-WP-0012 remain blocked in their owner files. No real-use receipt, admitted executor or standing release authority is inferred.

The State Hub intake query before 09:00 UTC returned only September 27 smoke/manual receipts, latest a552969b-59ac-4dc9-a4f8-b58856c129ab at 14:07:04Z. It did not supply the expected September 28 00:00Z natural daily run. This is missing cadence evidence, not a diagnosed scheduler outage. T03 retains cadence/sink verification with activity-core; no schedule was changed and no new task or workplan opened. Recheck evidence. October 1's monthly packet remains due even with no consumers or executor.

Reporting failure diagnosed and candidate prepared — 2026-09-28

T03: the missing receipt is a real required-context failure, not a missed schedule. The grant-aware worker promotion at activity-core 428f2d7 removed the frontend resolver. Prepared and published a scoped overlay preserving all other Python source and repository-grant identity. It restores registration and adds bounded monthly owner-snapshot health/decisions plus measured effort/unknown counts. 58 focused tests, 17 GitOps tests, server dry-run and registry readback pass. Evidence and exact digest.

The existing release runbook's 24-hour healthy interval is invalidated by the failure; no routine release identity exists. Exact attended repair approval is pending. Candidate publication and a future-clock October fixture are not production repair or actual monthly completion. All three schedules remain enabled and unchanged.

T01/T02: raw capability publication passes, hosted registration returns 404, and the routed OpenBao registration credential is unavailable to the operator session. Prepared a short consumer instruction; scanned local relevant workplan titles but found no ready/active external task to enroll. Blocked candidates and finished examples are not invented adoption evidence. Readiness record. Workplan remains blocked; no new task/workplan, consumer enrollment, secret disclosure or pattern-editing authority was introduced.

The user subsequently approved the exact attended worker repair; State Hub decision abdea390-1039-4da1-b129-33aad00b4396. Promotion and post-rollout proof are now authorized; this is not standing authority or approval to restore the older grant-unaware image.

Scoped worker repair verified — 2026-09-28

The approved repair is deployed: activity-core 4bd07a4, platform pin 986b002, exact candidate digest afd8a7af…. ArgoCD root and child selectively synchronized the Application pin and worker Deployment only. Live hashes preserve all other Python source and the typed grant identity. Daily/weekly/monthly scheduled smokes completed with validated State Hub receipts and zero model calls/spawned tasks. Live evidence.

All three recurring schedules remain enabled; temporary smoke schedules are gone. The monthly sink now includes dated owner-snapshot health, bounded decision/default fields and monthly measured effort with unknown counts. Today's monthly smoke covers August; the future-clock October fixture covers September. The actual October 1 packet and subsequent natural cadence are still required, owned with ACTIVITY-WP-0040 T02. Healthy pod status did not prevent the missing-resolver regression; old observation claims are invalidated. Standing authority remains ACTIVITY-WP-0041/RPF-WP-0048 work.

T03 remains wait for real unassisted improvement, admitted executor, automatic publication/rollback and natural monthly evidence. T01/T02 remain wait for hosted registration access and actual eligible consumer integration/outcomes. No new tasks or workplans, no manufactured use, and no new pattern-execution grant.

Natural reporting reconciled — 2026-10-04

ACTIVITY-WP-0040 finished its reporting scope on October 3. This repo verified all seven retained natural-run sink receipts against State Hub and checked the workflow UUIDv5 → durable run → sink run identity. Five daily runs (September 29–October 3), the September 29 weekly run and October 1 monthly report have validated outputs, zero spawned tasks and zero model calls. Evidence pins the owner's evidence revision/digest and preserves the actual monthly receipt. No workflow was triggered or deployment changed.

This supersedes earlier natural-cadence and October 1 waiting notes. Older Temporal histories are unavailable; only October 3's daily workflow has a directly retained COMPLETED result. The joined schedule/run/sink records establish older report delivery without inventing historical workflow status. The monthly packet covers September and its health section is a September 28 owner snapshot, not live health. The current monthly input is refreshed for future reports; the old receipt is intact.

The consumer roster remains empty: eligible-task coverage is unknown and no real use or verified outcome is established. T01's stale M1 dependency is removed to match this plan's qualified-use mandate; hosted registration and actual consumer integration still block it. T03's stale pre-scheduling blocker is replaced by its remaining execution/publication acceptance, including ACTIVITY-WP-0041-T03. All three tasks remain wait and this workplan remains blocked. No evidence gate, policy, budget, authority or parked research workplan is changed.

Gap-work consumer discovery — 2026-10-04

The user requested implementation of the assessed gaps. A bounded State Hub scan joined 49 todo and 2 progress tasks to active/ready workplans and matched frontend, interaction, editor/navigation/offline/component/designbook/keyboard/accessibility text outside FEP. No candidate met that index filter. Discovery receipt records method and limits: this is not proof that no eligible consumer exists anywhere. No external task was reopened or invented, and no synthetic event was enrolled. T01/T02 retain actual source-verified task selection and common-template integration. WP-0009's authorized fresh replication advances independent-validation preparation; it does not replace the consumer decision/outcome acceptance in this plan.

Blocked-task review — 2026-10-04

Dependency requirements establish exact owner returns and local evidence gates for every remaining task. All unfinished tasks stay wait; this plan is blocked because no currently available implementation can meet its remaining acceptance. Completed deliverables remain done with their recorded limits. Cross-repo source/synthetic proofs and finished editorial reviews are not the missing runtime admission, actual consumer or human evidence.

Dependency recheck — 2026-10-19

All owner dependencies (GLAS-WP-0012, HFACT-WP-0001, ACTIVITY-WP-0032/0041, RPF-WP-0048, SAND-WP-0014, SECRETS-WP-0009) are still blocked in State Hub. A repeated bounded consumer scan over 44 active/ready non-FEP workplans found six keyword hits and no eligible frontend consumer. Hosted registration was not retried without the routed credential. Evidence. T01/T02/T03 remain wait; workplan remains blocked.