Icons are meaning, so they belong to the system, not to a page (D58, rule L-icons). One meaning, one icon, everywhere. A field takes its icon from what its key means, else from the record it links to, else from its type; an action from its label, else from its verb. The build writes them into a page's description and the checker holds every page to this list; a meaning it doesn't cover stops the build until an icon is proposed and approved. Seeded from the job list. Proposed marks picks waiting for review. Read from system/model/icons.json, drawn in the menus' size and weight.
Vendor orders, resolved
Every field (filter, sort, group and column menus) and every action (the record, the bulk bar, menus) on the built vendor orders page, with the reason it has its icon.