Guardrails ✦ 80outlineNot a production recipe — calibrate thresholds

Slop / low-quality patch detect

Who: Code review bots. Steps: Diff/patch state → Noul/Score slop signals → ask rewrite. Expected effect: Name the pattern back to agent.

1

Treat this as an outline — adapt state and questions to your data.

2

Implement in code — call System One / Jev; compose answers yourself.

3

Gate on confidence — act, confirm, or escalate before side effects.

Outline sketch

Prompt
# Slop / low-quality patch detect
State: relevant software state for this pattern.
Ask: Choice / Score / Noul questions that close the decision space.
Then: compose the route or action in code; escalate when confidence is low.

Needs access to: typesafe-sdk

Who it's for

Code review bots

Steps / how it's set up

Steps

  1. Diff/patch state.
  2. Noul/Score slop signals.
  3. ask rewrite.

Sources

Metrics and demo claims are author-reported or cookbook-reported unless you measure them yourself. Calibrate on your data.

Expected effect

Name the pattern back to agent

Unofficial outline for learning. Paraphrased from public docs and tutorials — not a production recipe. Review sources before you automate anything.