Today
Portfolios
Veda
Review
Knowledge
Capabilities & Security
DEEP INSPECTION · WHAT VEDA CAN TECHNICALLY TOUCH · NO SECRETS SHOWN
VEDA · CAPABILITY INSPECTOR
A plain map of what Veda can technically reach — no machine-room theatre, and never a secret shown.
DISTINCT FROM PERMISSIONS
This is technical availability. What you’ve authorized lives in Permissions.
NO LIVE STATE CONNECTED
The map is real; each connection reads not connected until reported.
CAPABILITY MAP
{{ c.name }}
{{ c.stateLabel }}
{{ c.action }}
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
LAST VERIFIEDnot recorded
FEATURE MADE STALE
The Website acceptance status can’t be verified. On Website / Commerce it keeps 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, no data was exposed. Connect the source to restore the check.
VEDA HEARD
“what can Veda actually reach?”
confirm first
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.