@openvtc/trust-tasks 0.12.7 → 0.12.9

package/src/vtc/community/profile/update/0.1/payload.ts

@@ -14,12 +14,34 @@ export interface VTCCommunityProfileUpdatePayload {
    * Set the community's declared relationship-identifier default. See `CommunityProfile.relationshipIdentifierDefault` in the `vtc/_shared/0.1/community` schema. Omit to leave it unchanged.
    */
   relationshipIdentifierDefault?: "attributed" | "pairwise";
+  personhood?: PersonhoodGovernance;
   /**
    * Opaque community-defined extension bag (maintainer-capped).
    */
   extensions?: {};
   ext?: Ext;
 }
+/**
+ * Set the community's published personhood position. See `CommunityProfile.personhood` in the `vtc/_shared/0.1/community` schema. Replaces the whole object — a partial update would leave a verifier unable to tell an unset member from a cleared one. Omit to leave it unchanged.
+ */
+export interface PersonhoodGovernance {
+  /**
+   * Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on.
+   */
+  realHuman?: boolean;
+  /**
+   * Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says "exactly one membership in that VTC" — so a single community can satisfy it without any network above it.
+   */
+  singleMembership?: boolean;
+  /**
+   * DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted.
+   */
+  acceptedIdvps?: string[];
+  /**
+   * Where the governance framework these assertions refer to can be read.
+   */
+  governanceFrameworkUrl?: string | null;
+}
 /**
  * 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.
  */
@@ -53,6 +75,28 @@ export interface CommunityProfile {
    * Trust-registry reachability. Populated on reads; not settable.
    */
   registryStatus?: "active" | "degraded";
+  personhood?: PersonhoodGovernance1;
+}
+/**
+ * What this community's governance asserts about the personhood of its members.
+ */
+export interface PersonhoodGovernance1 {
+  /**
+   * Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on.
+   */
+  realHuman?: boolean;
+  /**
+   * Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says "exactly one membership in that VTC" — so a single community can satisfy it without any network above it.
+   */
+  singleMembership?: boolean;
+  /**
+   * DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted.
+   */
+  acceptedIdvps?: string[];
+  /**
+   * Where the governance framework these assertions refer to can be read.
+   */
+  governanceFrameworkUrl?: string | null;
 }
 
 /** Trust Task type URI. */
@@ -120,6 +164,10 @@ export const PAYLOAD_SCHEMA = {
       ],
       "description": "Set the community's declared relationship-identifier default. See `CommunityProfile.relationshipIdentifierDefault` in the `vtc/_shared/0.1/community` schema. Omit to leave it unchanged."
     },
+    "personhood": {
+      "$ref": "#/$defs/PersonhoodGovernance",
+      "description": "Set the community's published personhood position. See `CommunityProfile.personhood` in the `vtc/_shared/0.1/community` schema. Replaces the whole object — a partial update would leave a verifier unable to tell an unset member from a cleared one. Omit to leave it unchanged."
+    },
     "extensions": {
       "type": "object",
       "description": "Opaque community-defined extension bag (maintainer-capped)."
@@ -221,6 +269,42 @@ export const PAYLOAD_SCHEMA = {
             "degraded"
           ],
           "description": "Trust-registry reachability. Populated on reads; not settable."
+        },
+        "personhood": {
+          "$ref": "#/$defs/PersonhoodGovernance",
+          "description": "What this community's governance asserts about the personhood of its members."
+        }
+      }
+    },
+    "PersonhoodGovernance": {
+      "$anchor": "personhoodGovernance",
+      "title": "PersonhoodGovernance",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "A community's published position on personhood.\n\nDTG Credentials §Personhood Credentials places PHC status here rather than in the credential — \"PHC status is determined by governance and trust registries, not by credential structure\" — so a verifier deciding whether a VMC carries personhood weight reads this, not the credential's type array. §Governance Considerations item 1 makes the acceptable-IDVP list the community's to define and publish.\n\nEvery member is a declaration, not an enforcement: what a community actually accepts is decided by its own policy. Absent means the community has not published a position, which is not the same as asserting the negative.",
+      "properties": {
+        "realHuman": {
+          "type": "boolean",
+          "description": "Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on."
+        },
+        "singleMembership": {
+          "type": "boolean",
+          "description": "Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says \"exactly one membership in that VTC\" — so a single community can satisfy it without any network above it."
+        },
+        "acceptedIdvps": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted."
+        },
+        "governanceFrameworkUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Where the governance framework these assertions refer to can be read."
         }
       }
     }
@@ -324,6 +408,42 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
             "degraded"
           ],
           "description": "Trust-registry reachability. Populated on reads; not settable."
+        },
+        "personhood": {
+          "$ref": "#/$defs/PersonhoodGovernance",
+          "description": "What this community's governance asserts about the personhood of its members."
+        }
+      }
+    },
+    "PersonhoodGovernance": {
+      "$anchor": "personhoodGovernance",
+      "title": "PersonhoodGovernance",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "A community's published position on personhood.\n\nDTG Credentials §Personhood Credentials places PHC status here rather than in the credential — \"PHC status is determined by governance and trust registries, not by credential structure\" — so a verifier deciding whether a VMC carries personhood weight reads this, not the credential's type array. §Governance Considerations item 1 makes the acceptable-IDVP list the community's to define and publish.\n\nEvery member is a declaration, not an enforcement: what a community actually accepts is decided by its own policy. Absent means the community has not published a position, which is not the same as asserting the negative.",
+      "properties": {
+        "realHuman": {
+          "type": "boolean",
+          "description": "Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on."
+        },
+        "singleMembership": {
+          "type": "boolean",
+          "description": "Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says \"exactly one membership in that VTC\" — so a single community can satisfy it without any network above it."
+        },
+        "acceptedIdvps": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted."
+        },
+        "governanceFrameworkUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Where the governance framework these assertions refer to can be read."
         }
       }
     }

package/src/vtc/config/export/0.1/payload.ts

@@ -61,6 +61,7 @@ export interface CommunityProfileSnapshot {
    * The community's declared relationship-identifier default, as defined on `CommunityProfile` in the `vtc/_shared/0.1/community` schema. Carried in a config export so a restore reproduces the declaration rather than silently reverting it to the implementation default.
    */
   relationshipIdentifierDefault?: "attributed" | "pairwise";
+  personhood?: PersonhoodGovernance;
   /**
    * Opaque community-defined extension bag.
    */
@@ -70,6 +71,27 @@ export interface CommunityProfileSnapshot {
    */
   createdAt?: string;
 }
+/**
+ * The community's published personhood position, carried so an export restores it. Governance state, not runtime state — unlike `registryStatus`, which is deliberately absent here because reachability belongs to a running maintainer rather than to exported state.
+ */
+export interface PersonhoodGovernance {
+  /**
+   * Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on.
+   */
+  realHuman?: boolean;
+  /**
+   * Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says "exactly one membership in that VTC" — so a single community can satisfy it without any network above it.
+   */
+  singleMembership?: boolean;
+  /**
+   * DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted.
+   */
+  acceptedIdvps?: string[];
+  /**
+   * Where the governance framework these assertions refer to can be read.
+   */
+  governanceFrameworkUrl?: string | null;
+}
 
 /** Trust Task type URI. */
 export const TYPE_URI = "https://trusttasks.org/spec/vtc/config/export/0.1" as const;
@@ -224,6 +246,10 @@ export const PAYLOAD_SCHEMA = {
           ],
           "description": "The community's declared relationship-identifier default, as defined on `CommunityProfile` in the `vtc/_shared/0.1/community` schema. Carried in a config export so a restore reproduces the declaration rather than silently reverting it to the implementation default."
         },
+        "personhood": {
+          "$ref": "#/$defs/PersonhoodGovernance",
+          "description": "The community's published personhood position, carried so an export restores it. Governance state, not runtime state — unlike `registryStatus`, which is deliberately absent here because reachability belongs to a running maintainer rather than to exported state."
+        },
         "extensions": {
           "type": "object",
           "description": "Opaque community-defined extension bag."
@@ -234,6 +260,38 @@ export const PAYLOAD_SCHEMA = {
           "description": "When the community was created. Provenance only — an import never writes it."
         }
       }
+    },
+    "PersonhoodGovernance": {
+      "$anchor": "personhoodGovernance",
+      "title": "PersonhoodGovernance",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "A community's published position on personhood.\n\nDTG Credentials §Personhood Credentials places PHC status here rather than in the credential — \"PHC status is determined by governance and trust registries, not by credential structure\" — so a verifier deciding whether a VMC carries personhood weight reads this, not the credential's type array. §Governance Considerations item 1 makes the acceptable-IDVP list the community's to define and publish.\n\nEvery member is a declaration, not an enforcement: what a community actually accepts is decided by its own policy. Absent means the community has not published a position, which is not the same as asserting the negative.",
+      "properties": {
+        "realHuman": {
+          "type": "boolean",
+          "description": "Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on."
+        },
+        "singleMembership": {
+          "type": "boolean",
+          "description": "Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says \"exactly one membership in that VTC\" — so a single community can satisfy it without any network above it."
+        },
+        "acceptedIdvps": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted."
+        },
+        "governanceFrameworkUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Where the governance framework these assertions refer to can be read."
+        }
+      }
     }
   }
 } as const;
@@ -362,6 +420,10 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           ],
           "description": "The community's declared relationship-identifier default, as defined on `CommunityProfile` in the `vtc/_shared/0.1/community` schema. Carried in a config export so a restore reproduces the declaration rather than silently reverting it to the implementation default."
         },
+        "personhood": {
+          "$ref": "#/$defs/PersonhoodGovernance",
+          "description": "The community's published personhood position, carried so an export restores it. Governance state, not runtime state — unlike `registryStatus`, which is deliberately absent here because reachability belongs to a running maintainer rather than to exported state."
+        },
         "extensions": {
           "type": "object",
           "description": "Opaque community-defined extension bag."
@@ -372,6 +434,38 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "description": "When the community was created. Provenance only — an import never writes it."
         }
       }
+    },
+    "PersonhoodGovernance": {
+      "$anchor": "personhoodGovernance",
+      "title": "PersonhoodGovernance",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "A community's published position on personhood.\n\nDTG Credentials §Personhood Credentials places PHC status here rather than in the credential — \"PHC status is determined by governance and trust registries, not by credential structure\" — so a verifier deciding whether a VMC carries personhood weight reads this, not the credential's type array. §Governance Considerations item 1 makes the acceptable-IDVP list the community's to define and publish.\n\nEvery member is a declaration, not an enforcement: what a community actually accepts is decided by its own policy. Absent means the community has not published a position, which is not the same as asserting the negative.",
+      "properties": {
+        "realHuman": {
+          "type": "boolean",
+          "description": "Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on."
+        },
+        "singleMembership": {
+          "type": "boolean",
+          "description": "Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says \"exactly one membership in that VTC\" — so a single community can satisfy it without any network above it."
+        },
+        "acceptedIdvps": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted."
+        },
+        "governanceFrameworkUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Where the governance framework these assertions refer to can be read."
+        }
+      }
     }
   }
 } as const;

package/src/vtc/config/import/0.1/payload.ts

@@ -56,6 +56,7 @@ export interface CommunityProfileSnapshot {
    * The community's declared relationship-identifier default, as defined on `CommunityProfile` in the `vtc/_shared/0.1/community` schema. Carried in a config export so a restore reproduces the declaration rather than silently reverting it to the implementation default.
    */
   relationshipIdentifierDefault?: "attributed" | "pairwise";
+  personhood?: PersonhoodGovernance;
   /**
    * Opaque community-defined extension bag.
    */
@@ -65,6 +66,27 @@ export interface CommunityProfileSnapshot {
    */
   createdAt?: string;
 }
+/**
+ * The community's published personhood position, carried so an export restores it. Governance state, not runtime state — unlike `registryStatus`, which is deliberately absent here because reachability belongs to a running maintainer rather than to exported state.
+ */
+export interface PersonhoodGovernance {
+  /**
+   * Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on.
+   */
+  realHuman?: boolean;
+  /**
+   * Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says "exactly one membership in that VTC" — so a single community can satisfy it without any network above it.
+   */
+  singleMembership?: boolean;
+  /**
+   * DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted.
+   */
+  acceptedIdvps?: string[];
+  /**
+   * Where the governance framework these assertions refer to can be read.
+   */
+  governanceFrameworkUrl?: string | null;
+}
 /**
  * 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.
  */
@@ -375,6 +397,10 @@ export const PAYLOAD_SCHEMA = {
           ],
           "description": "The community's declared relationship-identifier default, as defined on `CommunityProfile` in the `vtc/_shared/0.1/community` schema. Carried in a config export so a restore reproduces the declaration rather than silently reverting it to the implementation default."
         },
+        "personhood": {
+          "$ref": "#/$defs/PersonhoodGovernance",
+          "description": "The community's published personhood position, carried so an export restores it. Governance state, not runtime state — unlike `registryStatus`, which is deliberately absent here because reachability belongs to a running maintainer rather than to exported state."
+        },
         "extensions": {
           "type": "object",
           "description": "Opaque community-defined extension bag."
@@ -385,6 +411,38 @@ export const PAYLOAD_SCHEMA = {
           "description": "When the community was created. Provenance only — an import never writes it."
         }
       }
+    },
+    "PersonhoodGovernance": {
+      "$anchor": "personhoodGovernance",
+      "title": "PersonhoodGovernance",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "A community's published position on personhood.\n\nDTG Credentials §Personhood Credentials places PHC status here rather than in the credential — \"PHC status is determined by governance and trust registries, not by credential structure\" — so a verifier deciding whether a VMC carries personhood weight reads this, not the credential's type array. §Governance Considerations item 1 makes the acceptable-IDVP list the community's to define and publish.\n\nEvery member is a declaration, not an enforcement: what a community actually accepts is decided by its own policy. Absent means the community has not published a position, which is not the same as asserting the negative.",
+      "properties": {
+        "realHuman": {
+          "type": "boolean",
+          "description": "Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on."
+        },
+        "singleMembership": {
+          "type": "boolean",
+          "description": "Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says \"exactly one membership in that VTC\" — so a single community can satisfy it without any network above it."
+        },
+        "acceptedIdvps": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted."
+        },
+        "governanceFrameworkUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Where the governance framework these assertions refer to can be read."
+        }
+      }
     }
   }
 } as const;
@@ -595,6 +653,10 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           ],
           "description": "The community's declared relationship-identifier default, as defined on `CommunityProfile` in the `vtc/_shared/0.1/community` schema. Carried in a config export so a restore reproduces the declaration rather than silently reverting it to the implementation default."
         },
+        "personhood": {
+          "$ref": "#/$defs/PersonhoodGovernance",
+          "description": "The community's published personhood position, carried so an export restores it. Governance state, not runtime state — unlike `registryStatus`, which is deliberately absent here because reachability belongs to a running maintainer rather than to exported state."
+        },
         "extensions": {
           "type": "object",
           "description": "Opaque community-defined extension bag."
@@ -605,6 +667,38 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "description": "When the community was created. Provenance only — an import never writes it."
         }
       }
+    },
+    "PersonhoodGovernance": {
+      "$anchor": "personhoodGovernance",
+      "title": "PersonhoodGovernance",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "A community's published position on personhood.\n\nDTG Credentials §Personhood Credentials places PHC status here rather than in the credential — \"PHC status is determined by governance and trust registries, not by credential structure\" — so a verifier deciding whether a VMC carries personhood weight reads this, not the credential's type array. §Governance Considerations item 1 makes the acceptable-IDVP list the community's to define and publish.\n\nEvery member is a declaration, not an enforcement: what a community actually accepts is decided by its own policy. Absent means the community has not published a position, which is not the same as asserting the negative.",
+      "properties": {
+        "realHuman": {
+          "type": "boolean",
+          "description": "Governance requires that members are real humans. Defaults to `false` when absent: a community that has not considered the question asserts nothing, which is the only safe default for a claim a verifier may rely on."
+        },
+        "singleMembership": {
+          "type": "boolean",
+          "description": "Governance requires that each person holds at most one membership in **this** community. Per-community by definition — the glossary says \"exactly one membership in that VTC\" — so a single community can satisfy it without any network above it."
+        },
+        "acceptedIdvps": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "DIDs of the identity-verification providers whose credentials this community accepts as personhood evidence. A community that vets its own members in person lists its own community DID here — it is acting as its own IDVP, which §IDVC permits. An empty list means no list has been published, not that everything is accepted."
+        },
+        "governanceFrameworkUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Where the governance framework these assertions refer to can be read."
+        }
+      }
     }
   }
 } as const;

package/src/vtc/endorsement-types/list/0.1/payload.ts

@@ -30,6 +30,10 @@ export interface EndorsementType {
    */
   claimSchema?: {};
   createdAt?: string;
+  /**
+   * The member who registered this endorsement type. An endorsement vocabulary is community-defined and shapes what every later endorsement can claim, so who introduced a type is audit-relevant in a way its creation time alone is not.
+   */
+  createdByDid?: string;
 }
 
 /** Trust Task type URI. */
@@ -135,6 +139,10 @@ export const PAYLOAD_SCHEMA = {
         "createdAt": {
           "type": "string",
           "format": "date-time"
+        },
+        "createdByDid": {
+          "type": "string",
+          "description": "The member who registered this endorsement type. An endorsement vocabulary is community-defined and shapes what every later endorsement can claim, so who introduced a type is audit-relevant in a way its creation time alone is not."
         }
       }
     }
@@ -208,6 +216,10 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "createdAt": {
           "type": "string",
           "format": "date-time"
+        },
+        "createdByDid": {
+          "type": "string",
+          "description": "The member who registered this endorsement type. An endorsement vocabulary is community-defined and shapes what every later endorsement can claim, so who introduced a type is audit-relevant in a way its creation time alone is not."
         }
       }
     }

package/src/vtc/endorsement-types/register/0.1/payload.ts

@@ -33,6 +33,10 @@ export interface EndorsementType {
    */
   claimSchema?: {};
   createdAt?: string;
+  /**
+   * The member who registered this endorsement type. An endorsement vocabulary is community-defined and shapes what every later endorsement can claim, so who introduced a type is audit-relevant in a way its creation time alone is not.
+   */
+  createdByDid?: string;
 }
 
 /** Trust Task type URI. */
@@ -137,6 +141,10 @@ export const PAYLOAD_SCHEMA = {
         "createdAt": {
           "type": "string",
           "format": "date-time"
+        },
+        "createdByDid": {
+          "type": "string",
+          "description": "The member who registered this endorsement type. An endorsement vocabulary is community-defined and shapes what every later endorsement can claim, so who introduced a type is audit-relevant in a way its creation time alone is not."
         }
       }
     }
@@ -201,6 +209,10 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "createdAt": {
           "type": "string",
           "format": "date-time"
+        },
+        "createdByDid": {
+          "type": "string",
+          "description": "The member who registered this endorsement type. An endorsement vocabulary is community-defined and shapes what every later endorsement can claim, so who introduced a type is audit-relevant in a way its creation time alone is not."
         }
       }
     }

package/src/vtc/join-requests/decide/0.1/payload.ts

@@ -33,6 +33,16 @@ export interface VTCJoinRequestsDecideResponsePayload {
    * The request's post-decision state; echoes the decision.
    */
   status: "approved" | "rejected";
+  /**
+   * The membership credential issued by this decision, delivered inline. Present only where the decision admitted the applicant.
+   *
+   * Inline because the alternative is worse: the applicant would poll for a status, learn they were admitted, and then fetch the credential separately — a second round trip whose only purpose is to collect something the community already had in hand when it decided.
+   */
+  vmc?: {} | null;
+  /**
+   * The endorsement credential carrying the role this decision granted, delivered inline alongside `vmc` and on the same reasoning. Present only where the decision admitted the applicant and granted a role.
+   */
+  roleVec?: {} | null;
   ext?: Ext;
 }
 
@@ -114,6 +124,20 @@ export const PAYLOAD_SCHEMA = {
           ],
           "description": "The request's post-decision state; echoes the decision."
         },
+        "vmc": {
+          "type": [
+            "object",
+            "null"
+          ],
+          "description": "The membership credential issued by this decision, delivered inline. Present only where the decision admitted the applicant.\n\nInline because the alternative is worse: the applicant would poll for a status, learn they were admitted, and then fetch the credential separately — a second round trip whose only purpose is to collect something the community already had in hand when it decided."
+        },
+        "roleVec": {
+          "type": [
+            "object",
+            "null"
+          ],
+          "description": "The endorsement credential carrying the role this decision granted, delivered inline alongside `vmc` and on the same reasoning. Present only where the decision admitted the applicant and granted a role."
+        },
         "ext": {
           "$ref": "#/$defs/Ext"
         }
@@ -160,6 +184,20 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           ],
           "description": "The request's post-decision state; echoes the decision."
         },
+        "vmc": {
+          "type": [
+            "object",
+            "null"
+          ],
+          "description": "The membership credential issued by this decision, delivered inline. Present only where the decision admitted the applicant.\n\nInline because the alternative is worse: the applicant would poll for a status, learn they were admitted, and then fetch the credential separately — a second round trip whose only purpose is to collect something the community already had in hand when it decided."
+        },
+        "roleVec": {
+          "type": [
+            "object",
+            "null"
+          ],
+          "description": "The endorsement credential carrying the role this decision granted, delivered inline alongside `vmc` and on the same reasoning. Present only where the decision admitted the applicant and granted a role."
+        },
         "ext": {
           "$ref": "#/$defs/Ext"
         }