Kanban Closed Loop Supervisor

Kanban Closed-Loop Supervisor (projection)

This is a projection. See canonical_source above for the authoritative text.

Hermes binding of the harness-agnostic orchestrate pattern. The pattern (tier discipline, pull-context dispatch, structured-verdict parse, dynamic round cap, operator-decisions break the loop) is the invariant. This skill binds it to delegate_task + Kanban + webhook-wake.

This skill is a THIN OVERLAY over delegate_task's orchestrator role. It does NOT rebuild the dispatch mechanism. It encodes the doctrine.

Load the kanban-orchestrator skill too -- this skill extends it.

When to use

All three conditions should hold:

1. =3 parallel bounded items with clear ground states.

2. Synthesis needed.
3. A quality criterion must be satisfied (seam reviewer must emit GO).

Do NOT use when:

• 1-2 items: use delegate_task directly.
• Items sequential: use execute-plan.
• No quality gate: use kanban-orchestrator.

The three-tier model

Tier 1: you (in conversation)
  |
  +-- dispatch --> Tier 2: Orchestrator (role='orchestrator' in delegate_task)
                    |
                    +-- Worker 1 (leaf)
                    +-- Worker 2 (leaf)
                    +-- Worker N (leaf)
                    v
                   Reviewer -> OVERALL: GO / NO-GO <seams>
                    |
                    +-- GO: synthesize -> return to Tier 1
                    +-- NO-GO: re-dispatch (up to MAX_ROUNDS, then escalate)

Hermes binding

Enable nested orchestration in config.yaml:

delegation:
  max_spawn_depth: 2
  max_concurrent_children: 5
  orchestrator_enabled: true

Dispatch:

result = delegate_task(
    goal="[orchestrator brief]",
    context="[substrate pointers only]",
    role="orchestrator",   # REQUIRED
    toolsets=["terminal", "file", "web"],
)

Verdict contract

Reviewer final line must be exactly:

OVERALL: GO

or

OVERALL: NO-GO

Parse with scripts/verdict-parser.sh (in canonical location):

verdict=$(bash /path/to/verdict-parser.sh "$REVIEWER_OUTPUT")

Dynamic round cap

The supervisory agent IS the cap. Escalate to Tier 1 on: (a) Same-seam NO-GO twice (spec ambiguity) (b) Irreversible action needed (merge/push/publish -- always surface) (c) Iteration redefines intent rather than executes it

Default MAX_ROUNDS=2. Raise with operator when stakes are high.

Gate-decision topology

Merge/push/publish always surfaces to Tier 1. NO-GO the loop cannot resolve surfaces to Tier 1. Everything else: the orchestrator drives.

Full doctrine

See canonical_source for the complete skill including:

• Pull-context brief format
• Worktree isolation procedure
• Closed-loop variant (implementer -> reviewer loop)
• Authorization patterns table
• Anti-patterns
• Synthesis return shape
• Worked references