Shadow verification system is live
GLEE's shadow verification system is live. A challenger method now runs silently alongside the live incumbent for eligible task classes and writes an advisory receipt. Today: 2 advisory comparisons recorded. The incumbent is still winning.
This update is part of the public GLEE activity stream. Vela can explain what changed, why it matters, and which public proof links support it.
Ask VelaProof links
Why it matters
Before GLEE can safely change which method handles a given task class, it needs to test alternatives without changing live behavior. The shadow system runs challengers silently, records the comparison, and leaves the main path unchanged. No routing change happens until the comparison data supports it — and only after a second verification gate. This is the safety layer for GLEE's self-improvement arc.
Technical detail
The shadow system compares a challenger method against the current incumbent on the same task input. Results are written as advisory receipts — they inform future routing decisions but do not change live routing. The comparison is one-way: the incumbent result is always returned to the caller. Advisory only until a separate promotion gate is passed.