📖About

Establish three-way UAT acceptor routing in the build pipeline, by the TYPE of self-* work:

• SELF-HEALING UAT -> Hermione (autonomous fix initiatives; re-trigger the failed process; existing pattern).
• SELF-IMPROVEMENT UAT -> Prometheus, Head of Quality Management (RSI / improvement initiatives).
• SELF-EXPANSION UAT -> Leo, Head of Strategy (new services / capabilities, e.g. Blueprint).

The UAT acceptor router must classify an initiative as healing / improvement / expansion (by origin/tag) and route acceptance to the right agent. Each acceptor runs a first-pass acceptance check against the initiative success criteria: pass -> close (uat:pass), fail -> rework or block at the autonomous cap. Supersede the interim Leo-only blueprint acceptor branch added under CAROL-INI-2125 with this general model, and give Prometheus a self-improvement UAT droid mirroring Hermione (self-healing) and Obi-Wan/Leo (self-expansion).

⚖️Decisions

• Self-healing UAT is owned by Hermione (ninad)
• Self-improvement UAT is owned by Prometheus (ninad)
• Self-expansion UAT is owned by Leo (ninad)
• [status-router] planned -> closed | event=operator_put | PUT /api/initiatives (operator)

✅Success criteria

• UAT router classifies each initiative as self-healing, self-improvement, or self-expansion (must_have)
• Self-healing (autonomous fix) initiatives route to Hermione for UAT acceptance (must_have)
• Self-improvement (RSI) initiatives route to Prometheus for UAT acceptance (must_have)
• Self-expansion (new service/capability, e.g. Blueprint) initiatives route to Leo for UAT acceptance (must_have)
• Each acceptor has a UAT droid that re-tests against success criteria: pass=close, fail=rework/block at cap (must_have)
• The interim Leo-only blueprint acceptor branch (CAROL-INI-2125) is superseded by this general model (must_have)