Establish ecosystem reuse and monthly-supervised improvement loop
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e241-8285-7a63-8c0c-51c9cb824dc3
This commit is contained in:
parent
88fee7c567
commit
0da4701bd0
10 changed files with 572 additions and 1 deletions
|
|
@ -8,7 +8,7 @@ status: proposed
|
|||
owner: codex
|
||||
topic_slug: canon
|
||||
created: "2026-09-24"
|
||||
updated: "2026-09-24"
|
||||
updated: "2026-09-27"
|
||||
state_hub_workstream_id: "831bbc30-30c0-5df3-a315-5355cd3b8ee5"
|
||||
---
|
||||
|
||||
|
|
@ -50,3 +50,12 @@ state_hub_task_id: "ab66848b-1045-54dd-9711-52c5560faafa"
|
|||
```
|
||||
|
||||
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.
|
||||
|
||||
## User-directed early reuse loop — 2026-09-27
|
||||
|
||||
WP-0008 owns an early qualified-reference pilot and consumer outcome instrumentation,
|
||||
authorized by the user's request for autonomous ecosystem improvement. It may proceed
|
||||
before M1/M2. It is distinct from this workplan's canonical export and held-out M3
|
||||
claims; it does not rename consumed feedback into unseen evaluation cases. This plan
|
||||
remains proposed with its original task gates. Routine reuse must not await those
|
||||
claims or require a human survey; preserve evidence provenance and honest unknowns.
|
||||
|
|
|
|||
140
workplans/FEP-WP-0008-use-driven-improvement.md
Normal file
140
workplans/FEP-WP-0008-use-driven-improvement.md
Normal file
|
|
@ -0,0 +1,140 @@
|
|||
---
|
||||
id: FEP-WP-0008
|
||||
type: workplan
|
||||
title: "Close the ecosystem reuse and improvement loop"
|
||||
domain: infotech
|
||||
repo: frontend-patterns
|
||||
status: active
|
||||
lane: blue
|
||||
owner: codex
|
||||
topic_slug: canon
|
||||
created: "2026-09-27"
|
||||
updated: "2026-09-27"
|
||||
---
|
||||
|
||||
# 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](../docs/ReuseAndImprovementLoop.md) is the implementation contract.
|
||||
|
||||
Exactly three delivery actions. Implementation has started with the local discovery entry; background
|
||||
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
|
||||
|
||||
```task
|
||||
id: FEP-WP-0008-T01
|
||||
status: progress
|
||||
priority: high
|
||||
lane: blue
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## Capture evidence of use and outcomes
|
||||
|
||||
```task
|
||||
id: FEP-WP-0008-T02
|
||||
status: todo
|
||||
priority: high
|
||||
lane: blue
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
## Run bounded improvements and monthly review autonomously
|
||||
|
||||
```task
|
||||
id: FEP-WP-0008-T03
|
||||
status: todo
|
||||
priority: high
|
||||
lane: blue
|
||||
```
|
||||
|
||||
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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue