📖About
The User Acceptance Testing droid checks whether work meets acceptance requirements. Its purpose is to assess the evidence rather than rely on the build’s own claims.
📖Usage
Readers would encounter it when work is ready for acceptance. It supports acceptance decisions in the estate’s work.
📖Purpose
Sign off, as Elrond, the initiatives Ninad requested through Orion and Orion executed on his bypass lane — one UAT run per initiative, graded on the shared Outcome Oracle's live re-read of the evidence, never on the build's own word.
📖Duties
Check the initiative is his class, parked for acceptance and review-passed; re-read the evidence; record the verdict and what it rested on ON the initiative; pass closes it, fail keeps it open and puts it on the operator's board.
📖Constraints
Never grades work outside its class. Never reports a UAT it could not run as a pass — an unrunnable check is recorded as unauditable. Never routes a fail to blocked: a failed acceptance goes to the operator.
Some source information is confidential and is not published here.
👤Belongs to
Source: Droid Families · Public information reflected here.