Skip to content

feat(agent): define evolved skill memory handling - #151

Merged
Pepps233 merged 3 commits into
feat/evolved-skill-lifecycle-observationsfrom
feat/evolved-skill-memory-relationship
Aug 31, 2026
Merged

Pepps233 merged 3 commits into
feat/evolved-skill-lifecycle-observationsfrom
feat/evolved-skill-memory-relationship

Conversation

@Pepps233

@Pepps233 Pepps233 commented Aug 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Define and enforce the relationship between evolved skills and EVOLVE.md so reusable procedural workflows move into skills while complementary behavioral constraints remain in memory, and any later removal or replacement of procedural memory requires an explicit proposal.

Reasoning

Ordered setup, tool, debugging, recovery, and verification routines should be retrieved as skills instead of consuming every prompt. Broad behavioral constraints can remain useful alongside those procedures, so activation cannot infer that related memory is safe to delete.

The Skill Curator now receives explicit separation and relationship semantics. The writer then reloads the immutable source candidates, verifies the relationship digest accepted by deterministic validation, and binds the resulting disposition into the mutation batch. Complementary and independent guidance remains unchanged, fallback or superseded guidance records that an explicit memory proposal is required, and conflicting or fully redundant guidance cannot reach activation.

Changes

  • Direct procedural workflows to skills while keeping broad always-on constraints in evolution memory.
  • Prohibit generated memory pointers that merely instruct the model to use a skill.
  • Define complementary, independent, fallback, superseding, redundant, and conflicting relationship semantics for skill curation.
  • Reload immutable source candidates before writing and verify their memory-relationship provenance against deterministic validation.
  • Bind exact relationship classifications and proposal IDs into skill mutation batches.
  • Preserve EVOLVE.md during skill activation and require a separate explicit proposal before fallback or superseded procedural memory can change.
  • Reject conflicting or redundant guidance before an activation batch can be built.

Stack

Position: 11 of 12
Base: #150
Next: #152

  1. feat(coding-agent): activate versioned evolved skills #134
  2. feat(agent): preserve target-neutral reflection evidence #136
  3. feat(agent): curate and checkpoint skill candidates #137
  4. feat(agent): persist and process skill candidate registry #138
  5. feat(agent): synthesize outcome-aware skill drafts #139
  6. feat(agent): validate evolved skill drafts #140
  7. feat(agent): measure procedural information loss #147
  8. feat(agent): evaluate evolved skill candidates #148
  9. feat(agent): activate evolved skill candidates #149
  10. feat(agent): observe evolved skill lifecycle outcomes #150
  11. feat(agent): define evolved skill memory handling #151 (this PR)
  12. feat(coding-agent): add evolved skill operator controls #152

Testing

  • cd packages/evolution && node ../../node_modules/vitest/dist/cli.js --run test/skill-curator.test.ts test/skill-writer.test.ts test/filesystem-store.test.ts test/skill-candidate-registry.test.ts test/skill-evaluator.test.ts test/skill-draft-validator.test.ts
  • npm run check (blocked by the pre-existing model-catalog TypeScript failures also reported on feat(agent): observe evolved skill lifecycle outcomes #150; no packages/evolution errors)

This pull request is AI-generated by Diffex.

@Pepps233
Pepps233 force-pushed the feat/evolved-skill-memory-relationship branch from c73beff to f3de832 Compare August 30, 2026 21:32
@Pepps233
Pepps233 merged commit 154d01e into main Aug 31, 2026
0 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant