The graph learns from use, Hebbian style: edges that keep firing together cross the LTP threshold and get a +0.15 bonus; paths that keep disappointing cross LTD and lose the same. The interesting constants are the guardrails — HOMEOSTATIC_CEILING (5.0) stops a hot path from monopolizing every future query, WEIGHT_FLOOR (0.05) keeps an edge from decaying into deletion, and CAS_RETRY_LIMIT makes weight updates safe under concurrency. Open question I keep revisiting: whether LTP/LTD thresholds should adapt per-repo instead of being global.
#ideasL11-L23Jul 6, 04:06 PM