Where gaming or entertainment tax software is developed or modified in house, a documented process (with a named owner) covers: review and documented approval of requests by IT supervisors; a written implementation plan; documented development and testing; records of approvals, testing, results, user acceptance, date in service, programmer and reason; physical and logical segregation of development and test from production; segregation of duties so developers and testers cannot promote code (a system administrator may not develop or test code for production); secured repositories for code history; and end-user documentation.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.