A credential proves who you are; the service you call decides what that identity may do.
That one line is the whole model, and it is enforced by structure rather than promise.
What the IDP promises
Section titled “What the IDP promises”- That a credential was issued by VClaw to a verified human or a claimed agent key.
- That it says who is calling — nothing more.
What the IDP does not do
Section titled “What the IDP does not do”- No authorization decisions. The IDP never decides whether a caller may spend, read, or administer a resource.
- No balances, caps, or mandates. Identity and payments stay separate by design — sign-in can never silently authorize money. Services that move money make their own decisions, with their own guards.
- No in-band authority. There are no chat commands that grant or revoke power. Roles change where identities are managed, exactly as in VClaw Networks.
Why the guards live in the service
Section titled “Why the guards live in the service”The service that owns a resource is the only place its rules can be both correct and current — caps, scopes, and admin boundaries change with the resource, not with the identity layer. The token contract (Credentials & Tokens) carries the capability to the service; the service still decides.
The guarantees, read honestly
Section titled “The guarantees, read honestly”| a credential says | a credential does not say |
|---|---|
| this caller was verified by VClaw | this caller is allowed to do the thing |
| this delegation is published and unexpired | the delegation’s terms are wise |
| this signature came from this key | the key’s owner is honest |
Everything in the second column is a decision — and decisions belong to services and humans, in that order.