Refiner decisions and routing
Understand model-owned relevance, no-action outcomes, and smallest-layer routing.
Refiner decisions and routing
The Refiner model decides whether evidence is meaningful, whether recovery still reveals a reusable defect, what layer owns the problem, and whether a small change can help materially different future tasks.
Possible outcomes
| Outcome | Meaning |
|---|---|
no_action | Evidence is weak, isolated, resolved, or not reusable. |
| Memory | A durable owner-scoped fact or preference. |
| Prompt | A broad execution behavior adjustment. |
| Skill or Agent | A reusable workflow or role change. |
| Runtime or product | A capability defect outside Harness content. |
| Taskset | Controlled measurement is needed. |
| Training | A model-policy limitation may exist, subject to separate gates. |
Deterministic host code enforces authorization, bounds, identity, schemas, safe paths, application, rollback, and approvals. It does not force a route from keywords, tool names, error strings, or a fixed number of occurrences.
Next: Critique and validation.