Capabilities & Security
WHAT VEDA CAN TECHNICALLY TOUCH
ENTERED FROM Trust Center · Build Floor
VEDA · CAPABILITY INSPECTOR
A plain map of what Veda can technically reach — no machine-room theatre, and never a secret shown.
This is technical availability — which capability actually works and what it can touch. What you’ve authorized lives in Permissions.
NO LIVE CAPABILITY STATE CONNECTED
The map below is real; each connection reads not connected until a live source reports it.
CAPABILITY MAP
{{ c.name }}
{{ c.action }}
{{ c.stateLabel }}
CAN TOUCH{{ c.canTouch }}
DEPENDS ON{{ c.dependency }}
LAST VERIFIEDnot recorded
IF REVOKED{{ c.ifRevoked }}
ALTERNATE — NOT CURRENT · A NEEDED CAPABILITY IS UNAVAILABLE, SO A NAMED FEATURE IS STALE. NO BREACH, ATTACK, SECRET, OR RECOVERY IS INVENTED — JUST AN UNCONNECTED DEPENDENCY.
Live site acceptance check
TLS · placeholder-copy · uptime probes
UNAVAILABLE
DEPENDS ONa connected website source
DEPENDENCY STATEnot connected
FEATURE MADE STALE
The Website acceptance status can’t be verified. On Website / Commerce it will keep reading “no live site acceptance source connected” — not a failure, just an unconnected capability.
Everything else is unaffected: drafts stay private, nothing outward was attempted, and no data was exposed. Connect the source to restore the check.
VEDA HEARD
“what can Veda actually reach?”
confirm first
Today
Portfolios
Veda
Review
Knowledge
Trust — capabilities
This is what Veda can technically reach — separate from what you’ve authorized in Permissions.
With no live state connected, every capability reads “not connected” — never a comforting green.
Secrets and credentials are never shown here — only the action class and what it can touch.