specs/vtc/join_requests/submit/v0_2/payload
library
Classes
-
Payload
-
VTC Join-Requests Submit — payload
-
PayloadAttributesItem
-
PayloadAttributesItem, generated from its schema.
-
Response
-
VTC Join-Requests Submit — response payload
-
Verdict
-
A ceremony decision: the effect, plus its effect-dependent detail.
-
VerdictWith
-
The effect-dependent detail of a verdict. Every member is optional at the schema
level and which ones are meaningful depends on
effect: role / obligations /
bundleRef on allow, code / reason on deny, queue / reason on refer,
needs / presentationDefinition on requestMore. The dependency is stated here
rather than enforced by if/then per effect, so that the shape stays a single
flat object a generated type can carry without a discriminated union per family — a
deliberate trade of schema strictness for implementability, and the reason a
consumer MUST branch on effect rather than on which members happen to be present.
Extension Types
-
VerdictEffect
-
What the policy decided.
allow — admitted. deny — refused, terminally for this
submission. refer — parked for a human or quorum decision; the applicant is
neither in nor out. requestMore — the policy cannot decide yet and names what
further evidence it needs. The four are not reducible to a pending/decided pair.
refer and requestMore are both 'not decided', but they place the next action
with different parties: refer waits on the community, requestMore waits on the
applicant. A consumer that cannot tell them apart cannot tell a user whether to
wait or to act.
Typedefs
-
Ext
= Map<String, dynamic>
-
Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a
reverse-DNS namespace; structure under each namespace is opaque to the framework.