wendy-aaa-interop
Installation
SKILL.md
Wendy AAA Interop
The AAA contract defines who is trusted for what across the control-plane services (wendy-auth, Wendy Cloud, pki-core, wendy-proxy) and the cryptographic invariants that hold even when one of them is compromised. It exists because Wendy serves critical-infrastructure partners: a breach of the SaaS control plane must never translate into the ability to act on a customer's fleet (§1).
Responsibility Split
| Service | Owns | Does NOT own |
|---|---|---|
| wendy-auth | Authentication; the identity graph (tenant + user + group(s)); IdP federation; issuance of identity assertions (tokens/SETs) | Authorization decisions; certificates; entitlements |
| Wendy Cloud | Authorization (group→role→entitlement mapping) + org-native lifecycle + orchestration | Authentication of humans; minting any private key or certificate |
| pki-core | Certificate issuance/revocation; enforcement of the platform + per-tenant policy ceiling; the cryptographic root of tenant isolation | Deciding who a principal is (defers to wendy-auth) or what they may do (defers to cloud), except as bounded by policy caps |
| wendy-proxy | Pure enforcement: fronting the image registries, deriving tenant scope from the device cert, enforcing a live per-device image assignment | Any issuance; any authorization decision of its own |
(§1)