A benchmark should attack the boundary, not decorate it.
VCGB is Veklom's adversarial capability-governance benchmark concept: a proof instrument for testing whether a system makes the correct decision and contains the real-world effect under hostile inputs. It is not presented as a core production runtime plane.
The frontend and documentation surface exist, but the current canonical runtime repositories do not expose a VCGB service with the same source/runtime depth as CAPPO, VNP, EEE, PGL or LockerPhycer. Until that changes, VCGB belongs in the proof lab, not the live runtime diagram.
Power stays narrow on purpose.
The surface should tell you where the truth comes from.
Veklom does not promote a configured URL or a code path into a runtime claim. Interfaces are shown so operators can verify the actual boundary themselves.
We are keeping VCGB because the benchmark idea is useful. We are removing the false equivalence: it should not appear beside live runtime services with an ONLINE badge until there is a canonical implementation and executed conformance evidence to justify that placement.
