EDA Bridge Standard: one way for an AI to drive every PCB tool

The standard every Adom EDA bridge follows so one AI can drive Altium, KiCad, Fusion 360 and any future PCB tool the same way: the shared verb names in tiers (core, native, checks, app, platform), the board model JSON every <prefix>_routing_state returns (mm, KiCad copper layer names, revision guard), the reply and refusal conventions, and how far each bridge covers it. Altium bridge is the reference for the board model and checks; any bridge can propose verbs (tools/proposed/<thread>.json). Use when building or extending an EDA bridge, adding a verb to kicad/fusion/altium bridges, porting a check between bridges, comparing what each bridge can do, or reading a board model from any bridge. Trigger words: eda bridge standard, bridge parity, same verbs every eda tool, board model json, routing_state schema, port altium verb to kicad, what can the kicad bridge not do, standard verb names.