Repository navigation
Conversation
This was referenced Aug 28, 2026
Pepps233
force-pushed
the
feat/evolved-skill-lifecycle-observations
branch
2 times, most recently
from
August 30, 2026 15:10
86c4247 to
b3c3d58
Compare
Pepps233
force-pushed
the
feat/evolved-skill-lifecycle-observations
branch
from
August 30, 2026 21:32
b3c3d58 to
3af7ecc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add append-only lifecycle observations and deterministic, exact-version reports for evolved skills so later helpful, harmful, neutral, and unknown outcomes can initiate a fresh candidate cycle without modifying active or historical harness revisions.
Reasoning
Skill content must remain immutable after activation, while later task outcomes still need to inform refinement and retirement. Lifecycle state therefore belongs in separate evolution storage and must retain the exact skill version, workspace, harness attribution, and top-level task lineage that produced each observation.
Outcome strength also cannot be inferred from availability or co-occurrence. The observer keeps invocation facts distinct, gives direct-user and deterministic outcomes more weight than self-assessment or inference, and emits only a mandatory Skill Curator handoff. Existing validation, retrieval evaluation, behavioral evaluation, and writer gates remain required before any content change or retirement.
Changes
Stack
Position: 10 of 12
Base: #149
Next: #151
Testing
cd packages/evolution && node ../../node_modules/vitest/dist/cli.js --run test/counter.test.ts test/skill-lifecycle.test.ts test/filesystem-store.test.tsnpm run check(blocked by the pre-existing model-catalog TypeScript failures also reported on feat(agent): evaluate evolved skill candidates #148; nopackages/evolutionerrors)This pull request is AI-generated by Diffex.