All checks were successful
check agents / check (push) Successful in 10s
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>
1.1 KiB
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. |
|
Run the critique phase in these steps, in order.
- Call
alz-scope.get_scopeagain and store it asscope-authoritative: the critic measures coverage against the scope server, not against the copy the planner used. - Call
alz-evidence.get_call_logandalz-evidence.get_guard_hitsfor the run. Store them ascall-logandguard-hits. - Call
delegate(sub_agent="dsc_08_critic", task=..., input_refs=[]). The critic always receives every record in the run; you cannot choose its inputs. - 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).