Files
Jonathan Boniface 416c66ced4
All checks were successful
check agents / check (push) Successful in 10s
Add CP1 Discovery agents in both patterns
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight
individual declarative agents (individual-agents/), with their KAB workflow
exports. Shared check, render and import scripts, the alz-discovery-sample
MCP server, the crucible-kab-dev deploy profile, deployment docs, platform
issue reports and the source material. Agent steps time out at 20 minutes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 18:25:57 +00:00

1.1 KiB

name, description, metadata
name description metadata
discovery-critique Validate a discovery run's coverage and integrity through the critic and return the verdict. Use when the request's phase is critique.
agent.tools agent.tags
workspace_put workspace_get workspace_list delegate discovery assurance

Run the critique phase in these steps, in order.

  1. Call alz-scope.get_scope again and store it as scope-authoritative: the critic measures coverage against the scope server, not against the copy the planner used.
  2. Call alz-evidence.get_call_log and alz-evidence.get_guard_hits for the run. Store them as call-log and guard-hits.
  3. Call delegate(sub_agent="dsc_08_critic", task=..., input_refs=[]). The critic always receives every record in the run; you cannot choose its inputs.
  4. Do not change, argue with or soften the critic's verdict.

Reply with the phase outcome:

  • summary: the critic's verdict and its main reasons, in a sentence or two.
  • issues: every reason the critic gave for a fail.
  • next_phase: null. verdict: as the critic gave it (post_process recomputes it).