The client declares the assumptions that underpin correct operation, such as environmental conditions (lighting, connectivity, device capability), demographic coverage (dataset size or representativeness) and operational practices (human oversight or fallback), and declares exclusions from certification such as age groups the item is not intended for, unsupported contexts and excluded functions or methods. Both are recorded in the certification agreement and referenced on the certificate and schedule so that certification is transparent and repeatable.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.