Skip to content

Evolution Registry

GE's structured self-improvement backlog. Every improvement, enhancement, and technical debt item lives here so nothing gets lost between sessions.

How It Works

Status lifecycle: pending --> in-progress --> completed

Directory Meaning
pending/ Identified but not started
in-progress/ Actively being worked on
completed/ Done and verified

Priority scale:

Priority Meaning
critical Actively causing harm or data loss — fix now
high Significant impact on quality or cost — fix this week
medium Noticeable improvement opportunity — next sprint
low Nice to have — when convenient

Categories:

Category Scope
learning-pipeline Struggle detector, wiki writer, knowledge extraction
agent-system Identity, executor, providers, classification
infrastructure K8s, Redis, networking, probes, deployments
orchestration Dolly, routing, hooks, completion scanner
wiki-brain Wiki structure, content, JIT injection
compliance Constitution, quality gates, trust policy
client-delivery Client projects, hosting, CI/CD
monitoring Grafana, Loki, health checks, alerting

requires_human field:

  • true = needs Dirk-Jan's decision or human judgment before work starts
  • false = agent can potentially implement autonomously

Entry Template

Every evolution entry must use this front matter:

---
title: "[descriptive title]"
id: EVO-{YYYY}-{MMDD}-{NNN}
status: pending
priority: critical | high | medium | low
category: [from category list above]
discovered: YYYY-MM-DD
discovered_during: "[what session/task surfaced this]"
affects: [list of agents, systems, or components]
estimated_complexity: simple | normal | complex
requires_human: true | false
completed_date: null
completed_by: null
---

# {Title}

## Problem
[What's wrong or suboptimal]

## Impact
[What this costs in tokens, time, quality, or reliability]

## Proposed Solution
[How to fix it — be specific enough that another session can pick this up]

## Acceptance Criteria
[How to verify the fix worked]

Adding New Entries

  1. Create a file in pending/ named EVO-{YYYY}-{MMDD}-{NNN}.md
  2. Use the template above
  3. Set requires_human: true if you're unsure about the approach
  4. Link from the relevant pitfall/contract/infrastructure page if applicable

Current Counts

See pending/, in-progress/, and completed/ directories for live counts.