feature · r2-30-evaluator-critic
M
5 tags · 8 out · 8 in · 3 artifacts · 1 gaps · 1 corpus docs
How should evaluation stay separate from execution — actor proposes, critic scores, human decides on high-stakes paths — without self-approval or unbounded retry?
This topic was frozen in the corporate agentic OS research corpus (wave 10) to answer architecture and measurement questions that sit under the locked loop (observe→understand→predict→intervene→resolve→verify→learn). Stage-1 criticality: M. Research/Spec/Platform readiness: R5/S4/P1.
Graph edges for this feature — technologies, category lens, companies, DM.
features/r2-30-evaluator-critic/README.md
feature missing document-management.md
T30 — Evaluator / Critic Agent Design · ok
features/r2-30-evaluator-critic/README.md
Research path: features/r2-30-evaluator-critic