VCGB

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.

Current classification
Specification
SPEC

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.

Architectural role
Adversarial benchmark / conformance instrument
Owns
01The benchmark vocabulary for evaluating ALLOW / DENY and effect-boundary correctness.
02Adversarial scenarios that can be applied to a capability-governance implementation.
03A place to publish repeatable conformance criteria without turning the benchmark into execution authority.
Boundary

Power stays narrow on purpose.

VCGB is not a production execution service and does not sit in the consequence path.
A benchmark page is not proof that every scenario has been executed against the current deployment.
CAPPO, LockerPhycer, VLink, VNP and EEE each keep their own runtime/proof responsibilities.
Interfaces

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.

Current classification
Benchmark / specification surface
Execution authority
None
Runtime status
Do not represent as a live service until a canonical runtime exists
Best home
Conformance + adversarial proof tooling
Claim boundary

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.