---
slug: vtc/schemas/accepts/list
version: "0.2"
title: "VTC Schemas — Accepts — List"
summary: An administrator pages through the community's Accepts criteria — the evidence rules its ceremonies decide against.
status: draft
targetFrameworkVersion: "0.6.0"
category: governance
parties:
  - role: community administrator
    requirement: REQUIRED
    member: issuer
    identifierScope: any
  - role: community maintainer
    requirement: REQUIRED
    member: recipient
    identifierScope: public
proofRequirement:
  requirement: RECOMMENDED
  rationale: >-
    Authority is the signer's administrator standing, which the community can establish from a verified proof or a transport-authenticated sender. A proof is recommended so the read is attributable on every transport, relayed ones included. What it returns is the community's own configuration, not personal data.
sideEffects:
  level: none
  rationale: >-
    Reads the registered criteria. Persists nothing.
exposure:
  discloses: metadata
  ingests: none
  actsAsSubject: false
  rationale: >-
    Discloses community policy — admission modes, DCQL queries, vetting and invitation requirements, descriptions, and who registered each — to an administrator.
retention:
  class: transient
  rationale: >-
    A read; the community keeps nothing.
errorCodes: []
related:
  - vtc/schemas/accepts/show
  - vtc/schemas/accepts/register
  - vtc/join-requests/manifest
---

## Abstract

The **VTC Schemas — Accepts — List** Trust Task pages through the community's registered Accepts criteria in id order, each in full. Unlike [`vtc/schemas/list`](../../../list/0.1/spec.md), items carry their whole body: a criterion is its admission mode and its optional DCQL query, vetting and invitation requirement, bounded by their own schemas, not an arbitrary JSON Schema. [`vtc/schemas/accepts/show`](../../show/0.2/spec.md) fetches one by id and answers `notFound` for an unknown one.

This is the administrator's view of what the join manifest publishes to applicants, without the manifest's derivation (presentation-definition shape, `requirementsDigest`).

## Status of this Document

This specification is a **draft** ([SPEC §5.3](/SPEC.md#53-maturity-levels)). It targets framework version 0.6.0 and may change without a version bump while it remains a draft ([SPEC §5.2](/SPEC.md#52-compatibility-rules)).


### Changes from 0.1

The criterion returned is the 0.2 `AcceptsCriterion` of [`vtc/_shared/0.2/schema-registry.schema.json`](../../../../_shared/0.2/schema-registry.schema.json): it always carries `admission` (`automatic` or `review`), and carries `query` only when it requires credentials, with `credentialIssuers` beside it, and `invitationRequired` when it requires an invitation. See [`vtc/schemas/accepts/register/0.2`](../../register/0.2/spec.md).

## Conformance

The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY** and **OPTIONAL** in this document are to be interpreted as described in [BCP 14](https://www.rfc-editor.org/info/bcp14) when, and only when, they appear in all capitals.

A conforming producer and consumer satisfy [SPEC §7.1 and §7.2](/SPEC.md#7-minimum-requirements) in addition to the requirements stated here.

A conforming **community** (`recipient`):

1. **MUST** refuse a caller without administrator standing with `permissionDenied`.
2. **MUST** return criteria in ascending `id` order, at most `limit` per page, with `nextCursor` present exactly when more remain, and `items: []` when none are registered.

## Definitions

- **Item** — an `AcceptsCriterion` from [`vtc/_shared/0.2/schema-registry.schema.json`](../../../../_shared/0.2/schema-registry.schema.json).

## Request

A community administrator (`issuer`) asks the community (`recipient`) for a page.

### First page

```json
{
  "id": "urn:uuid:00000000-0000-4000-8000-000000000001",
  "type": "https://trusttasks.org/spec/vtc/schemas/accepts/list/0.2#request",
  "issuer": "did:example:administrator",
  "recipient": "did:example:community",
  "issuedAt": "2026-09-28T10:00:00Z",
  "threadId": "urn:uuid:00000000-0000-4000-8000-0000000001ff",
  "payload": {}
}
```

## Response

The community answers with the sub-schema reachable via `$anchor: "response"`. A refusal is a `trust-task-error`.

### One criterion

```json
{
  "id": "urn:uuid:00000000-0000-4000-8000-000000000002",
  "type": "https://trusttasks.org/spec/vtc/schemas/accepts/list/0.2#response",
  "issuer": "did:example:community",
  "recipient": "did:example:administrator",
  "issuedAt": "2026-09-28T10:00:01Z",
  "threadId": "urn:uuid:00000000-0000-4000-8000-0000000001ff",
  "payload": {
    "items": [
      {
        "id": "membership",
        "admission": "automatic",
        "query": {
          "credentials": [
            {
              "id": "membership",
              "format": "vc+sd-jwt",
              "meta": {
                "vct_values": [
                  "https://openvtc.org/credentials/MembershipCredential"
                ]
              }
            }
          ]
        },
        "credentialIssuers": "recognised",
        "createdAt": "2026-09-28T10:00:01Z",
        "createdByDid": "did:example:administrator"
      }
    ]
  }
}
```

## Security & Privacy

### Data carried

The community's own registry configuration: type URIs, DTG catalog bindings, JSON Schemas, DCQL queries and administrators' descriptions. The description members are free text written by administrators, bounded at 1024 characters, read by other administrators (and, for a criterion, by applicants in the join manifest); untrusted, and attributed to `createdByDid` wherever rendered. `createdByDid` names an administrator.

### Correlation

The community is declared with identifier scope `public`: it is the one DID every administrator, member and applicant addresses, and the records this task reads or writes are its own. A pairwise identifier for it would leave a caller unable to tell which community answered. The response names the administrator who last registered each entry — information about the community's own administrators, disclosed only to another administrator.

### Retention

A read. The community keeps nothing; the caller's copy is stale at the next registration or deletion.

### Consent/purpose

The purpose is to let administrators see and maintain what the community issues and accepts. The registry is community configuration and not a privacy-sensitive enumeration; it is disclosed to administrators because they maintain it.
