High-priority signals
Intent drift: changed files do not map cleanly to the original task.
Fake-green evidence: tests pass but avoid real behavior.
Shortcut implementation: stubs, mocks, hardcoded values, broad exception swallowing, or narrow fixtures.
Risky file impact: changes in auth, billing, data, infrastructure, release, or migration code.
Unsupported claims: the agent says the work is complete but evidence is partial or missing.
How signals become decisions
A signal is not always a blocker. It becomes a decision when combined with the task’s risk level, evidence strength, and reviewer expectations.
FeelGoot is designed to make that reasoning explicit.
Signal language for teams
Consistent labels help reviewers and managers discuss agent failures without vague language. That is why pages in this site use stable names like fake-green tests and intent drift.