A Verifiable Trust Community's community groups: named sets of members that administrators (and the group managers they appoint) run. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen). EVERY GROUP HAS ITS OWN DID. The community's own VTA mints it from a DID template and holds its keys; the community never does. Where the group issues credentials (`issuesCredentials`, default true), the community issues the group an authorization credential naming it a membership issuer, and the group's DID issues each member a short-lived membership credential, renewed for as long as they stay. A verifier chains member's group credential → group's authorization credential → community. GROUPS PROVISION; THE ACCESS-CONTROL LIST AUTHORISES. A group never answers an authorization question at the community. Authority a group carries (a `grants` or `role` binding) is written into each member's access-control entry as a resource grant whose source is the group, and removed when they leave. A group's membership credential is evidence for others — rooms, peers, other communities — and is never consulted by the community's own authorization. MEMBERSHIP IS KEYED BY ENTRY. Members are directory entries (`EntryId`), so membership survives a rotation of the member's DID, and departure from the community removes it.
https://trusttasks.org/spec/vtc/groups/_shared/0.1/groupTrust Tasks — the registry of Trust Task specifications.
Loading the registry… If this message stays, the page's scripts could not load or run. The site needs JavaScript and access to unpkg.com.
Every specification is also on GitHub: trustoverip/dtgwg-trust-tasks-tf/specs, and the framework specification at /SPEC.md.