Problem
The recent update to the Pre-Commit operational mandates introduced the colloquial term "AI slop" (e.g., "Anti-Slop Gate"). While meaningful to human engineers, cultural memes and colloquialisms decrease instruction clarity for foundation models. It is better to use precise, operational terminology to define the exact failure mode we are trying to prevent.
Goal
Refactor the phrasing in the operational mandates (AGENTS.md, AGENTS_STARTUP.md) to replace "Anti-Slop" with concrete instruction tuning terminology, such as "Contextual Completeness" or "Semantic Degradation", which map directly to the technical constraints of the Knowledge Base.
Execution
- Replace "Anti-Slop" with "Contextual Completeness" throughout
AGENTS.md.
- Update the Pre-Flight Check thought process to use objective terminology ("undocumented, context-less code" instead of "AI slop").
- Synchronize the phrasing changes in
AGENTS_STARTUP.md.
Problem
The recent update to the Pre-Commit operational mandates introduced the colloquial term "AI slop" (e.g., "Anti-Slop Gate"). While meaningful to human engineers, cultural memes and colloquialisms decrease instruction clarity for foundation models. It is better to use precise, operational terminology to define the exact failure mode we are trying to prevent.
Goal
Refactor the phrasing in the operational mandates (
AGENTS.md,AGENTS_STARTUP.md) to replace "Anti-Slop" with concrete instruction tuning terminology, such as "Contextual Completeness" or "Semantic Degradation", which map directly to the technical constraints of the Knowledge Base.Execution
AGENTS.md.AGENTS_STARTUP.md.