Recorded case

AGENTJUDGE: acceptance follows evidence

A reviewer checks the task, the artifact version and each acceptance criterion.

Reviewed 15 October 2026 · scope: implemented

Recorded method and findings

Every criterion has a scope and a result: pass, fail, insufficient evidence or not applicable with a reason. The reviewer distinguishes something being described, implemented and observed at runtime. A specification proves intent; code proves an implementation exists; a runtime receipt proves only the measured behavior.

Recorded method and findings

A second model agreeing with the first is not enough. If both answers rely on the same unverified source, their agreement may be an echo. Deterministic failure, missing required evidence or a changed artifact prevents acceptance even when the worker sounds confident.

Practical checklist

Do not accept self-reported test success without a receipt. Lock the criterion before work and inspect attempts to weaken it. Track false acceptance and rejection on known cases before trusting a reviewer as a gate.

Sources & scope

Evidence-based agent review contract 2026-10-14
Swarm coordination implementation specification 2026-10-15

Keep exploring

AI orchestration: from a prompt to an accepted resultA practical design for delegation, evidence and recovery.Shared memory without shared mistakesKeep facts, hypotheses and permissions distinct across agent sessions.Engineering that can show its workTVIJO connects operators, bounded agent work and knowledge that can be checked and reused.AGENTORCH: the orchestrator has a concrete jobAGENTORCH names the orchestration role: plan, assign, observe, reconcile and accept.The task packet is the interfaceA good task describes a verifiable outcome rather than an invitation to improvise without limits.Measure cost per accepted resultSmall task benchmarks illustrate why task class and acceptance matter more than a cheap model label.Budgets and outages belong in the state machineA reliable operator view distinguishes working, waiting, failed, blocked and accounting uncertainty.Keep VECTORBASE, evaluate retrievalUse a private source-linked index to find evidence; do not treat search results as authority.SPIDER: evidence collection and useful progressThe first implementation reads an explicit project-evidence list and produces a dated operator digest without model calls.DSHREMBOT and tmux: one operator viewAuthenticated project commands, budget visibility and explicit schedule controls connect the operator to existing execution lanes.The AI worker–Hugging Face incident: learn from controlsThe incident reports support specific engineering lessons, not a controlled ranking of our system.What the supplied AI worker screenshot actually provesThe screenshot records a safeguard-triggered switch in one session; it does not explain the exact trigger. The observation is the supplied screenshot dated 15 October 2026.Training our own model: a gated research directionA proprietary model is an option to test after retrieval, prompts and routing have measurable limits.A bilingual knowledge product with visible limitsPublish useful explanations first, then expand languages when the evidence and workflow are ready.Free learning, custom projects and future challengesTurn evidence-backed engineering into clear offers and a useful developer community.Trust the sender, not a public checksumBind the complete message to an explicitly trusted authority.