guild-create-specialist

You can create domain-specific agents by running a gated 7-step workflow that enforces boundary checks and evaluation gates before live registration. This incubation process ensures new specialists pass boundary scans and paired evals in shadow-mode before deployment.

A gated workflow for minting specialists is a 7-step process—Interview, Draft, Boundary scan, Proposed boundary edits, Gate boundary edits, Gate new specialist, and Register. It ensures traceable governance by enforcing evaluation gates and boundary checks before a new agent goes live.

You prevent trigger overlaps by performing adjacent-boundary analysis during the specialist creation workflow. This analysis ensures new triggers do not overlap with existing specialists and verifies that boundary clauses are properly in place before gating.

Yes, the workflow generates incubation artifacts under agents/proposed/ and skills/specialists/proposed-<role>-*/ directories. These proposed artifacts are specifically generated for review, testing, and eventual live deployment after passing all evaluation gates.

If a new specialist fails the boundary or evaluation gates, the workflow tracks the handoff and provides a structured handoff payload on rejection. It maintains auditable extraction signals and reflections in the guild metadata to justify the new role's creation or rejection.

Yes, minting a new specialist requires paired evals with shadow-mode before live registration. The workflow enforces gate checks via evolution-evaluation to ensure the agent meets all governance and boundary requirements before going live.