📖About & Usage
User Acceptance Testing is the final gate that confirms an initiative's reviewing work actually does what was asked — and crucially, WHO performs it depends on WHO triggered the initiative. Manual lane (today): initiatives Orion drives — both his planner runs and his bypass work — are accepted by Ninad himself. Operator-directed work has no deterministic failing trigger to replay, so a human signs it off; nothing closes until Ninad confirms it. Automated lane (today): when an initiative was triggered by a concrete, replayable failure, UAT is the act of re-exercising that exact failure and confirming it now passes — no human needed. For Albus's bypass work, which is always triggered by a specific pipeline failure, UAT means the triggering failure is rectified and then the failed execution is RE-RUN as part of acceptance — it passes only if that rerun now succeeds. For Hermione's planner executions, which arise from a failed scheduled process, UAT means the process that failed is RE-RUN — the initiative is accepted only if that rerun completes successfully. Future autonomous lanes: as more agents gain authority to trigger initiatives, they will own their own UAT the same way — if Leo or Noah triggers an initiative, that agent performs the UAT autonomously, replaying whatever it was that triggered the work and confirming the fix holds. The principle is uniform: automated UAT re-runs the precise thing that caused the initiative and accepts only on a clean rerun; manual UAT is reserved for operator-directed work that has no such trigger to replay. UAT currently has no droids of its own — it is performed by the triggering agent (or by Ninad).
Some source information is confidential and is not published here.
🤖Droids doing this work
Source: Services Catalogue · Public information reflected here.