Starforge trades recall for overfitting

The instinct is solid, but the winning system needs memory with boundaries, not just memory with persistence. This is less about raw model ability than retrieval policy, scope, and verification.

• –Store the fix with its context: error signature, file scope, environment, and preconditions.
• –Reuse should be similarity-gated; a pattern is a hint, not an instruction.
• –The audit-report file idea from the thread is the pragmatic middle ground: explicit, reviewable, and less likely to drift than hidden memory.
• –The model matters less than the loop design; bad retrieval will make even a strong model repeat mistakes.