@openvtc/trust-tasks 0.27.4 → 0.27.5

package/src/vtc/members/authority-reduction-pending-notice/0.1/payload.ts

@@ -39,7 +39,7 @@ export interface VTCMembersAuthorityReductionPendingNoticePayload {
    */
   landsAt: string;
   /**
-   * The cooling-off action holding the reduction. The subject follows it with vtc/admin/actions/show/0.2, where it appears with `callerRole: subject`, to learn whether it was cancelled or landed.
+   * The cooling-off action holding the reduction. The subject follows it with vtc/admin/actions/show (0.2 or later), where it appears with `callerRole: subject`, to learn whether it was cancelled or landed.
    */
   actionId: ActionId;
   /**
@@ -127,7 +127,7 @@ export const PAYLOAD_SCHEMA = {
     },
     "actionId": {
       "$ref": "#/$defs/ActionId",
-      "description": "The cooling-off action holding the reduction. The subject follows it with vtc/admin/actions/show/0.2, where it appears with `callerRole: subject`, to learn whether it was cancelled or landed."
+      "description": "The cooling-off action holding the reduction. The subject follows it with vtc/admin/actions/show (0.2 or later), where it appears with `callerRole: subject`, to learn whether it was cancelled or landed."
     },
     "reason": {
       "type": "string",

package/src/vtc/members/step-up-passkey-notice/0.2/payload.ts

@@ -0,0 +1,137 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/members/step-up-passkey-notice/0.2/payload.schema.json
+ */
+
+import type { Ext } from "../../../../_shared/components.js";
+
+
+/**
+ * The VTC tells a member that a step-up passkey was enrolled for them or revoked from them, naming who acted and when. Unsolicited: the member did not ask, and may be offline.
+ */
+export interface VTCMembersStepUpPasskeyNoticePayload {
+  /**
+   * `enrolled` — a step-up passkey (auth/passkey/enroll/invite or auth/passkey/enroll/finish, purpose stepUp) is now bound to the member. `revoked` — one was unbound (auth/passkey/revoke/finish).
+   */
+  event: "enrolled" | "revoked";
+  /**
+   * The member's own DID — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice, detached from its transport, still names its subject.
+   */
+  did: string;
+  /**
+   * Durable identifier of the step-up credential, as auth/passkey/revoke/start and auth/passkey/admin-list carry it: opaque, non-secret metadata, never key material. Lets the member recognise or distinguish a credential without disclosing anything that would help an attacker.
+   */
+  credentialId: string;
+  /**
+   * Who acted: the member themselves (equal to `did`) when they enrolled or revoked it on their own session, or an administrator's DID when they invited the enrollment or revoked for the member. A `by` other than `did` is the signal this task exists to carry — act on someone else's behalf is exactly the account-takeover shape a silent change would hide.
+   */
+  by: string;
+  /**
+   * When the event took effect at the VTC — not when the notice was sent, which differs whenever the member was offline.
+   */
+  occurredAt: string;
+  /**
+   * The acting administrator's stated reason, verbatim, when one was given. Absent rather than empty when none was: a community that chose not to explain is itself information. Never populated for a member acting on their own credential — they already know why.
+   */
+  reason?: string;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.2" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCMembersStepUpPasskeyNoticePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/vtc/members/step-up-passkey-notice/0.2",
+  "title": "VTC Members — Step-up Passkey Notice — payload",
+  "description": "The VTC tells a member that a step-up passkey was enrolled for them or revoked from them, naming who acted and when. Unsolicited: the member did not ask, and may be offline.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "event",
+    "did",
+    "credentialId",
+    "by",
+    "occurredAt"
+  ],
+  "properties": {
+    "event": {
+      "type": "string",
+      "enum": [
+        "enrolled",
+        "revoked"
+      ],
+      "description": "`enrolled` — a step-up passkey (auth/passkey/enroll/invite or auth/passkey/enroll/finish, purpose stepUp) is now bound to the member. `revoked` — one was unbound (auth/passkey/revoke/finish)."
+    },
+    "did": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The member's own DID — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice, detached from its transport, still names its subject."
+    },
+    "credentialId": {
+      "type": "string",
+      "minLength": 1,
+      "description": "Durable identifier of the step-up credential, as auth/passkey/revoke/start and auth/passkey/admin-list carry it: opaque, non-secret metadata, never key material. Lets the member recognise or distinguish a credential without disclosing anything that would help an attacker."
+    },
+    "by": {
+      "type": "string",
+      "minLength": 1,
+      "description": "Who acted: the member themselves (equal to `did`) when they enrolled or revoked it on their own session, or an administrator's DID when they invited the enrollment or revoked for the member. A `by` other than `did` is the signal this task exists to carry — act on someone else's behalf is exactly the account-takeover shape a silent change would hide."
+    },
+    "occurredAt": {
+      "type": "string",
+      "format": "date-time",
+      "description": "When the event took effect at the VTC — not when the notice was sent, which differs whenever the member was offline."
+    },
+    "reason": {
+      "type": "string",
+      "maxLength": 1024,
+      "description": "The acting administrator's stated reason, verbatim, when one was given. Absent rather than empty when none was: a community that chose not to explain is itself information. Never populated for a member acting on their own credential — they already know why."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Ext": {
+      "title": "Ext",
+      "description": "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.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;

package/src/vtc/operator/offline-write/0.2/payload.ts

@@ -0,0 +1,133 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/operator/offline-write/0.2/payload.schema.json
+ */
+
+import type { Ext } from "../../../../_shared/components.js";
+
+
+/**
+ * A RECORD TYPE, not a request. It describes one change to a Verifiable Trust Community's access control made by an operator with access to the community's host, through an offline command run against the community's store (`vtc admin emergency-bootstrap` and its siblings) rather than through any Trust Task. No party sends a document of this type to another and no consumer executes one: its Type URI exists so that an `acknowledge` action (vtc/admin/actions/_shared/0.3) can name what happened in `typeUri`, and so that the community's audit trail can reference it. When an action names it, the action's `payload` is this record. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface VTCOperatorOfflineWriteRecord {
+  /**
+   * Which offline command made the change. `aclAdd` — an access control entry was written. `aclRemove` — an access control entry was removed. `adminInvite` — an administrator invitation was minted. `createDidKeyAdmin` — a new `did:key` was minted on the host and made an administrator. `enrolApprover` — an approver was enrolled for a subject. `emergencyBootstrap` — the break-glass recovery that installs an administrator when none can act. A closed set: a new offline command is a new version, so that a renderer never shows an administrator a change it cannot name.
+   */
+  command: "aclAdd" | "aclRemove" | "adminInvite" | "createDidKeyAdmin" | "enrolApprover" | "emergencyBootstrap";
+  /**
+   * The DIDs whose access the command changed — the subject of an entry added or removed, the administrator installed or invited, the subject an approver was enrolled for and the approver — in the order the command reports them. Never empty: an offline write that changed nobody's access is not one administrators need to acknowledge.
+   *
+   * @minItems 1
+   * @maxItems 64
+   */
+  dids: [string, ...string[]];
+  /**
+   * The host the command ran on, as the community knows it (its hostname, or the deployment's name for the instance). Identifies where an operator held access, not who the operator was; attribution to a person, where the community has one, is the action's `requester`.
+   */
+  host: string;
+  /**
+   * When the command wrote the change to the community's store, as recorded on the host. Not when the community noticed it, which is the action's `createdAt`.
+   */
+  writtenAt: string;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/operator/offline-write/0.2" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCOperatorOfflineWriteRecord;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/vtc/operator/offline-write/0.2",
+  "title": "VTC Operator Offline Write — record",
+  "description": "A RECORD TYPE, not a request. It describes one change to a Verifiable Trust Community's access control made by an operator with access to the community's host, through an offline command run against the community's store (`vtc admin emergency-bootstrap` and its siblings) rather than through any Trust Task. No party sends a document of this type to another and no consumer executes one: its Type URI exists so that an `acknowledge` action (vtc/admin/actions/_shared/0.3) can name what happened in `typeUri`, and so that the community's audit trail can reference it. When an action names it, the action's `payload` is this record. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "command",
+    "dids",
+    "host",
+    "writtenAt"
+  ],
+  "properties": {
+    "command": {
+      "type": "string",
+      "enum": [
+        "aclAdd",
+        "aclRemove",
+        "adminInvite",
+        "createDidKeyAdmin",
+        "enrolApprover",
+        "emergencyBootstrap"
+      ],
+      "description": "Which offline command made the change. `aclAdd` — an access control entry was written. `aclRemove` — an access control entry was removed. `adminInvite` — an administrator invitation was minted. `createDidKeyAdmin` — a new `did:key` was minted on the host and made an administrator. `enrolApprover` — an approver was enrolled for a subject. `emergencyBootstrap` — the break-glass recovery that installs an administrator when none can act. A closed set: a new offline command is a new version, so that a renderer never shows an administrator a change it cannot name."
+    },
+    "dids": {
+      "type": "array",
+      "minItems": 1,
+      "maxItems": 64,
+      "uniqueItems": true,
+      "items": {
+        "type": "string",
+        "minLength": 1,
+        "maxLength": 2048
+      },
+      "description": "The DIDs whose access the command changed — the subject of an entry added or removed, the administrator installed or invited, the subject an approver was enrolled for and the approver — in the order the command reports them. Never empty: an offline write that changed nobody's access is not one administrators need to acknowledge."
+    },
+    "host": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 253,
+      "description": "The host the command ran on, as the community knows it (its hostname, or the deployment's name for the instance). Identifies where an operator held access, not who the operator was; attribution to a person, where the community has one, is the action's `requester`."
+    },
+    "writtenAt": {
+      "type": "string",
+      "format": "date-time",
+      "description": "When the command wrote the change to the community's store, as recorded on the host. Not when the community noticed it, which is the action's `createdAt`."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Ext": {
+      "title": "Ext",
+      "description": "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.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: false,
+  isRecipientRequired: false,
+  isIssuedAtRequired: false,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;

package/src/vtc/relationships/restore/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/vtc/relationships/restore/0.1/payload.schema.json
  */
 
-import type { Ext, InForce, LifecycleReason } from "../../../../_shared/components.js";
+import type { Ext, InForce_VtcV0_1 as InForce, LifecycleReason } from "../../../../_shared/components.js";
 
 
 /**

package/src/vtc/relationships/restore/0.2/payload.ts

@@ -0,0 +1,307 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/relationships/restore/0.2/payload.schema.json
+ */
+
+import type { Ext, InForce_VtcV0_4 as InForce, LifecycleReason } from "../../../../_shared/components.js";
+
+
+/**
+ * Restore one published relationship edge. The outer document members are owned by the framework — SPEC §6.3.
+ */
+export interface VTCRelationshipsRestorePayload {
+  /**
+   * The relationship (VRC) id, as vtc/relationships/list returns it.
+   */
+  id: string;
+  reason?: LifecycleReason;
+  ext?: Ext;
+}
+export interface VTCRelationshipsRestoreResponsePayload {
+  /**
+   * Echoed.
+   */
+  id: string;
+  state: InForce;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Ext, InForce, LifecycleReason };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/restore/0.2" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCRelationshipsRestorePayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/relationships/restore/0.2#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCRelationshipsRestoreResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/vtc/relationships/restore/0.2",
+  "title": "VTC Relationships — Restore — payload",
+  "description": "Restore one published relationship edge. The outer document members are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "id"
+  ],
+  "properties": {
+    "id": {
+      "type": "string",
+      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+      "description": "The relationship (VRC) id, as vtc/relationships/list returns it."
+    },
+    "reason": {
+      "$ref": "#/$defs/LifecycleReason"
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Relationships — Restore — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "id",
+        "state"
+      ],
+      "properties": {
+        "id": {
+          "type": "string",
+          "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+          "description": "Echoed."
+        },
+        "state": {
+          "$ref": "#/$defs/InForce"
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "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.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "InForce": {
+      "title": "InForce",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "state"
+      ],
+      "description": "Whether the edge is in force now, and if not, why not — the edge's resolved state, which is not the same thing as the event just recorded: restoring an edge whose `validUntil` passed while it was suspended records the restoration and still resolves `expired`. Exactly the members its `state` names are present.",
+      "properties": {
+        "state": {
+          "type": "string",
+          "enum": [
+            "yes",
+            "notYetValid",
+            "expired",
+            "suspended",
+            "superseded",
+            "withdrawn",
+            "indeterminate"
+          ],
+          "description": "`yes`: inside its window, nothing standing against it. `notYetValid`: its `validFrom` has not arrived. `expired`: its `validUntil` has passed. `suspended`: temporarily ineffective — the only non-`yes` state a lifecycle event can reverse. `superseded`: displaced by a later credential. `withdrawn`: terminal. `indeterminate`: the credential's own window could not be read, so no honest answer is available."
+        },
+        "validFrom": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `notYetValid`."
+        },
+        "validUntil": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `expired`."
+        },
+        "since": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `suspended`: when the standing suspension was recorded."
+        },
+        "endedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `superseded` and `withdrawn`: when the edge stopped being in force."
+        },
+        "by": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 256,
+          "description": "Present for `superseded`: the digest of the credential that displaced it."
+        },
+        "reason": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 500,
+          "description": "Present for `indeterminate`: why the window could not be read. Written by the community."
+        }
+      }
+    },
+    "LifecycleReason": {
+      "title": "LifecycleReason",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 500,
+      "description": "Why the edge was suspended or restored, stored verbatim on the lifecycle event. Free text written by the caller — the edge's issuer or a moderating administrator — and read by the counterparty and by administrators; retained with the edge. Untrusted, attributed to its author wherever rendered, and never read by the community's state machine."
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Relationships — Restore — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "id",
+        "state"
+      ],
+      "properties": {
+        "id": {
+          "type": "string",
+          "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+          "description": "Echoed."
+        },
+        "state": {
+          "$ref": "#/$defs/InForce"
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "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.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "InForce": {
+      "title": "InForce",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "state"
+      ],
+      "description": "Whether the edge is in force now, and if not, why not — the edge's resolved state, which is not the same thing as the event just recorded: restoring an edge whose `validUntil` passed while it was suspended records the restoration and still resolves `expired`. Exactly the members its `state` names are present.",
+      "properties": {
+        "state": {
+          "type": "string",
+          "enum": [
+            "yes",
+            "notYetValid",
+            "expired",
+            "suspended",
+            "superseded",
+            "withdrawn",
+            "indeterminate"
+          ],
+          "description": "`yes`: inside its window, nothing standing against it. `notYetValid`: its `validFrom` has not arrived. `expired`: its `validUntil` has passed. `suspended`: temporarily ineffective — the only non-`yes` state a lifecycle event can reverse. `superseded`: displaced by a later credential. `withdrawn`: terminal. `indeterminate`: the credential's own window could not be read, so no honest answer is available."
+        },
+        "validFrom": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `notYetValid`."
+        },
+        "validUntil": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `expired`."
+        },
+        "since": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `suspended`: when the standing suspension was recorded."
+        },
+        "endedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present for `superseded` and `withdrawn`: when the edge stopped being in force."
+        },
+        "by": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 256,
+          "description": "Present for `superseded`: the digest of the credential that displaced it."
+        },
+        "reason": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 500,
+          "description": "Present for `indeterminate`: why the window could not be read. Written by the community."
+        }
+      }
+    },
+    "LifecycleReason": {
+      "title": "LifecycleReason",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 500,
+      "description": "Why the edge was suspended or restored, stored verbatim on the lifecycle event. Free text written by the caller — the edge's issuer or a moderating administrator — and read by the counterparty and by administrators; retained with the edge. Untrusted, attributed to its author wherever rendered, and never read by the community's state machine."
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/vtc/relationships/suspend/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/vtc/relationships/suspend/0.1/payload.schema.json
  */
 
-import type { Ext, InForce, LifecycleReason } from "../../../../_shared/components.js";
+import type { Ext, InForce_VtcV0_1 as InForce, LifecycleReason } from "../../../../_shared/components.js";
 
 
 /**