context property
The maintainer's context identifier the integration is to be provisioned into. When
present, authoritative — overrides any contextHint carried inside request.ask.
When ABSENT, the maintainer infers the target context using these rules in order:
(1) if the relayer's grant scopes to exactly one context, use that context; (2) if
the relayer is a super-admin (Admin role with unrestricted scope) and the
maintainer has exactly one context registered, use that context; (3) otherwise
reject the request with provision/integration:contextRequired. Wallet-class
consumers (browser plugins, mobile companions) that don't know the maintainer's
context layout SHOULD omit this field; integration-class consumers (mediator,
did-hosting) targeting a specific operational context SHOULD send it explicitly.
Implementation
final String? context;