Skip to content

Audit learnings file: accumulate fix patterns across runs #20

Closed

Description

@dominicnunez

Context

Inspired by GEA (Group-Evolving Agents) — agents that share collective experience to improve over time.

Problem

Willie currently remembers what NOT to flag (audit/exceptions.md) but forgets HOW it fixed things. Each run rediscovers the same fix patterns from scratch.

Proposal

Add audit/learnings.md — a file Willie reads alongside exceptions that accumulates successful fix patterns.

Examples:

  • "When you find unanchored regexes, anchor with $ at end of string"
  • "When fixing CSP headers, check both app-level (hooks.server.ts) and nginx config"
  • "Convex mutations that modify records should check existence first with ctx.db.get()"

How it works

  1. After the fix step, Willie appends any reusable pattern it discovered to audit/learnings.md
  2. The audit prompt reads learnings alongside exceptions
  3. Future runs apply known patterns faster and more consistently

Why this matters

  • Reduces iteration count (Willie applies known fixes immediately instead of rediscovering them)
  • Builds project-specific knowledge beyond just "don't flag this"
  • Lightweight alternative to full agent self-modification (GEA paper)

Relationship to existing issues

Activity

  1. dominicnunez commented on Feb 21, 2026

    @dominicnunez
    OwnerAuthor

    Closed as duplicate of #24 - RFC: Springfield Ultra

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpriority: mediumShould fixresearchExperimental ideas, needs investigation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions