@openvtc/trust-tasks 0.23.7 → 0.23.9

package/src/vtc/storage/credentials/set/0.1/payload.ts

@@ -0,0 +1,339 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/storage/credentials/set/0.1/payload.schema.json
+ */
+
+import type { CredentialState, DigestMultibase, Ext, ExternalAccountId, StorageConfigId } from "../../../../../_shared/components.js";
+
+
+/**
+ * Store a `sealed` storage config's long-lived credential, sealed end to end to the community. Write-only: no task returns it. The outer document members are owned by the framework — SPEC §6.3.
+ */
+export interface VTCStorageCredentialsSetPayload {
+  configId: StorageConfigId;
+  /**
+   * OpenPGP-style ASCII-armored `sealed_transfer` ciphertext of the credential. HPKE base mode, X25519-HKDF-SHA256 KEM, ChaCha20-Poly1305 AEAD, info string `vta-sealed-transfer/v1`; recipient the X25519 derivation of the community DID's Ed25519 key.
+   */
+  sealed: string;
+  /**
+   * Digest over the armored bytes exactly as carried in `sealed`. Covered by the document's proof, and shown to approvers in place of the credential.
+   */
+  digestMultibase: DigestMultibase;
+  /**
+   * Why the administrator is making this change. Recorded with the change in the audit trail and shown to approvers. Attributed to its author on every surface and untrusted: it MUST NOT carry personal data or a credential, and a reader MUST NOT treat it as instructions.
+   */
+  reason: string;
+  ext?: Ext;
+}
+export interface VTCStorageCredentialsSetResponsePayload {
+  configId: StorageConfigId;
+  credentialState: CredentialState;
+  /**
+   * Present when the community probed the config with the new credential.
+   */
+  probeOk?: boolean;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { CredentialState, DigestMultibase, Ext, ExternalAccountId, StorageConfigId };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/storage/credentials/set/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCStorageCredentialsSetPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/storage/credentials/set/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCStorageCredentialsSetResponsePayload;
+
+/**
+ * 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/storage/credentials/set/0.1",
+  "title": "VTC Storage — Credentials — Set — payload",
+  "description": "Store a `sealed` storage config's long-lived credential, sealed end to end to the community. Write-only: no task returns it. The outer document members are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "configId",
+    "sealed",
+    "digestMultibase",
+    "reason"
+  ],
+  "properties": {
+    "configId": {
+      "$ref": "#/$defs/StorageConfigId"
+    },
+    "sealed": {
+      "type": "string",
+      "minLength": 64,
+      "maxLength": 16384,
+      "pattern": "^-----BEGIN VTA SEALED BUNDLE-----",
+      "description": "OpenPGP-style ASCII-armored `sealed_transfer` ciphertext of the credential. HPKE base mode, X25519-HKDF-SHA256 KEM, ChaCha20-Poly1305 AEAD, info string `vta-sealed-transfer/v1`; recipient the X25519 derivation of the community DID's Ed25519 key."
+    },
+    "digestMultibase": {
+      "$ref": "#/$defs/DigestMultibase",
+      "description": "Digest over the armored bytes exactly as carried in `sealed`. Covered by the document's proof, and shown to approvers in place of the credential."
+    },
+    "reason": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 500,
+      "description": "Why the administrator is making this change. Recorded with the change in the audit trail and shown to approvers. Attributed to its author on every surface and untrusted: it MUST NOT carry personal data or a credential, and a reader MUST NOT treat it as instructions."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Storage — Credentials — Set — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "configId",
+        "credentialState"
+      ],
+      "properties": {
+        "configId": {
+          "$ref": "#/$defs/StorageConfigId"
+        },
+        "credentialState": {
+          "$ref": "#/$defs/CredentialState"
+        },
+        "probeOk": {
+          "type": "boolean",
+          "description": "Present when the community probed the config with the new credential."
+        },
+        "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-]+)+$"
+      }
+    },
+    "CredentialState": {
+      "title": "CredentialState",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "status"
+      ],
+      "description": "Whether a config can authenticate now, and how — never the credential. `status`: `vta-account`, `ambient` and `sealed` are usable; `required` means the config cannot store until a credential is provided (a `sealed` config never set, or set before a restore, which carries no credential); `none` is a `local` config.",
+      "properties": {
+        "status": {
+          "type": "string",
+          "enum": [
+            "vta-account",
+            "ambient",
+            "sealed",
+            "required",
+            "none"
+          ]
+        },
+        "account": {
+          "$ref": "#/$defs/ExternalAccountId",
+          "description": "Present with `vta-account`."
+        },
+        "fingerprint": {
+          "$ref": "#/$defs/DigestMultibase",
+          "description": "Present with `sealed`: a digest identifying the stored credential, so an administrator can tell which one is set without anyone being able to read it. Computed over the credential with a community-held key, never a bare hash of a low-entropy secret."
+        },
+        "setAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present with `sealed`: when the stored credential was last set."
+        },
+        "roomsHoldingCredentials": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Present with `vta-account`: how many rooms the community currently holds a live room-scoped credential for."
+        }
+      }
+    },
+    "ExternalAccountId": {
+      "title": "ExternalAccountId",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z0-9](?:[a-z0-9-]{0,62}[a-z0-9])?$",
+      "description": "The identifier of an external account held by the community's VTA (the external/accounts/* family), which issues the community short-lived, room-scoped credentials and holds the long-lived authority itself."
+    },
+    "DigestMultibase": {
+      "title": "DigestMultibase",
+      "description": "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.",
+      "type": "string",
+      "minLength": 16,
+      "pattern": "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$",
+      "examples": [
+        "zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"
+      ]
+    },
+    "StorageConfigId": {
+      "title": "StorageConfigId",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z0-9](?:[a-z0-9-]{0,62}[a-z0-9])?$",
+      "description": "A storage config's identifier, chosen by the administrator who creates it and immutable thereafter: lowercase letters, digits and inner hyphens, at most 64 characters (`eu-s3-primary`, `walrus-main`). Unique within the community. Never reused after a config is retired, because blobs name their config by this value."
+    }
+  }
+} 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 Storage — Credentials — Set — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "configId",
+        "credentialState"
+      ],
+      "properties": {
+        "configId": {
+          "$ref": "#/$defs/StorageConfigId"
+        },
+        "credentialState": {
+          "$ref": "#/$defs/CredentialState"
+        },
+        "probeOk": {
+          "type": "boolean",
+          "description": "Present when the community probed the config with the new credential."
+        },
+        "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-]+)+$"
+      }
+    },
+    "CredentialState": {
+      "title": "CredentialState",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "status"
+      ],
+      "description": "Whether a config can authenticate now, and how — never the credential. `status`: `vta-account`, `ambient` and `sealed` are usable; `required` means the config cannot store until a credential is provided (a `sealed` config never set, or set before a restore, which carries no credential); `none` is a `local` config.",
+      "properties": {
+        "status": {
+          "type": "string",
+          "enum": [
+            "vta-account",
+            "ambient",
+            "sealed",
+            "required",
+            "none"
+          ]
+        },
+        "account": {
+          "$ref": "#/$defs/ExternalAccountId",
+          "description": "Present with `vta-account`."
+        },
+        "fingerprint": {
+          "$ref": "#/$defs/DigestMultibase",
+          "description": "Present with `sealed`: a digest identifying the stored credential, so an administrator can tell which one is set without anyone being able to read it. Computed over the credential with a community-held key, never a bare hash of a low-entropy secret."
+        },
+        "setAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "Present with `sealed`: when the stored credential was last set."
+        },
+        "roomsHoldingCredentials": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Present with `vta-account`: how many rooms the community currently holds a live room-scoped credential for."
+        }
+      }
+    },
+    "ExternalAccountId": {
+      "title": "ExternalAccountId",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z0-9](?:[a-z0-9-]{0,62}[a-z0-9])?$",
+      "description": "The identifier of an external account held by the community's VTA (the external/accounts/* family), which issues the community short-lived, room-scoped credentials and holds the long-lived authority itself."
+    },
+    "DigestMultibase": {
+      "title": "DigestMultibase",
+      "description": "A cryptographic digest as a multibase-encoded multihash — the encoding the W3C Verifiable Credentials Data Model 2.0 defines for `digestMultibase`, and the one `did:webvh` uses for its SCID and entry hashes.\n\nMultihash carries the hash algorithm in-band, so the value is self-describing and the wire format survives an algorithm change without a schema revision; multibase does the same for the base encoding, so a verifier never infers base58 from base64url by context. A bare hex string or a `sha-256:`-style prefix hard-codes one algorithm into the wire contract and is non-conforming here.\n\nThis definition constrains the *encoding only*. What the digest is computed over is stated by each referencing field, because it differs legitimately: a digest over a JSON document is taken over its RFC 8785 (JCS) canonicalization, while a digest over an opaque artifact is taken over its bytes. A field whose input is a JSON document and which does not name a canonicalization is not reproducible.\n\nRestricted to the two multibase headers W3C Controlled Identifiers 1.0 §2.4 normatively requires — `z` (base58btc) and `u` (base64url-no-pad). CID permits others but states that \"interoperability is not guaranteed between implementations using such values\", and a registry whose purpose is interoperability should not mint digests a conforming verifier may be unable to read. The alphabets are enforced rather than assumed: base58btc excludes 0, O, I and l, and an earlier permissive pattern let three published examples carry digests that were not valid base58 at all. base58btc is RECOMMENDED, for consistency with `did:key` and `did:webvh`.",
+      "type": "string",
+      "minLength": 16,
+      "pattern": "^(z[1-9A-HJ-NP-Za-km-z]+|u[A-Za-z0-9_-]+)$",
+      "examples": [
+        "zQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"
+      ]
+    },
+    "StorageConfigId": {
+      "title": "StorageConfigId",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "pattern": "^[a-z0-9](?:[a-z0-9-]{0,62}[a-z0-9])?$",
+      "description": "A storage config's identifier, chosen by the administrator who creates it and immutable thereafter: lowercase letters, digits and inner hyphens, at most 64 characters (`eu-s3-primary`, `walrus-main`). Unique within the community. Never reused after a config is retired, because blobs name their config by this value."
+    }
+  }
+} 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/vetting/hidden/publish/0.1/payload.ts

@@ -6,6 +6,11 @@
 import type { Ext } from "../../../../../_shared/components.js";
 
 
+/**
+ * The length of one tick of the drip, as an ISO 8601 duration in days and/or hours — at least `PT1H`; a request that omits it gets `P3D`. A label's tick `t` is the window starting `t` tick lengths after the label's start (`vtc/vetting/vetters/pcs-tokens`).
+ */
+export type TickLength = string;
+
 /**
  * Turn on (or rotate the parameters of) hidden-vetter admission for one criterion. Every member but criterionId has a default. The outer document members are owned by the framework — SPEC §6.3.
  */
@@ -30,6 +35,7 @@ export interface VTCVettingHiddenPublishPayload {
    * How many attestation tokens a vetter draws per tick. Defaults to three.
    */
   dripPerTick?: number;
+  tickLength?: TickLength;
   /**
    * Events this community is running, replacing whatever was there. Absent or empty removes every event.
    */
@@ -113,6 +119,7 @@ export interface StoredConfig {
   livePeriods: string[];
   liveTokenLabels: string[];
   dripPerTick: number;
+  tickLength: TickLength;
   events: StoredEvent[];
 }
 export interface StoredEvent {
@@ -146,6 +153,7 @@ export interface PublishedConfig {
   vetterLabels: string[];
   tokenLabels: string[];
   dripPerTick: number;
+  tickLength: TickLength;
   events: PublishedEvent[];
 }
 /**
@@ -222,6 +230,9 @@ export const PAYLOAD_SCHEMA = {
       "minimum": 1,
       "description": "How many attestation tokens a vetter draws per tick. Defaults to three."
     },
+    "tickLength": {
+      "$ref": "#/$defs/TickLength"
+    },
     "events": {
       "type": "array",
       "items": {
@@ -234,6 +245,12 @@ export const PAYLOAD_SCHEMA = {
     }
   },
   "$defs": {
+    "TickLength": {
+      "title": "TickLength",
+      "type": "string",
+      "pattern": "^P(?:\\d+D(?:T\\d+H)?|T\\d+H)$",
+      "description": "The length of one tick of the drip, as an ISO 8601 duration in days and/or hours — at least `PT1H`; a request that omits it gets `P3D`. A label's tick `t` is the window starting `t` tick lengths after the label's start (`vtc/vetting/vetters/pcs-tokens`)."
+    },
     "RequestEvent": {
       "title": "RequestEvent",
       "type": "object",
@@ -403,6 +420,7 @@ export const PAYLOAD_SCHEMA = {
         "livePeriods",
         "liveTokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -440,6 +458,9 @@ export const PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {
@@ -460,6 +481,7 @@ export const PAYLOAD_SCHEMA = {
         "vetterLabels",
         "tokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -496,6 +518,9 @@ export const PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {
@@ -557,6 +582,12 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$ref": "#/$defs/Response",
   "$defs": {
+    "TickLength": {
+      "title": "TickLength",
+      "type": "string",
+      "pattern": "^P(?:\\d+D(?:T\\d+H)?|T\\d+H)$",
+      "description": "The length of one tick of the drip, as an ISO 8601 duration in days and/or hours — at least `PT1H`; a request that omits it gets `P3D`. A label's tick `t` is the window starting `t` tick lengths after the label's start (`vtc/vetting/vetters/pcs-tokens`)."
+    },
     "RequestEvent": {
       "title": "RequestEvent",
       "type": "object",
@@ -726,6 +757,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "livePeriods",
         "liveTokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -763,6 +795,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {
@@ -783,6 +818,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "vetterLabels",
         "tokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -819,6 +855,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {

package/src/vtc/vetting/hidden/show/0.1/payload.ts

@@ -6,6 +6,11 @@
 import type { Ext } from "../../../../../_shared/components.js";
 
 
+/**
+ * The length of one tick of the drip, as an ISO 8601 duration in days and/or hours — at least `PT1H`. A label's tick `t` is the window starting `t` tick lengths after the label's start (`vtc/vetting/vetters/pcs-tokens`).
+ */
+export type TickLength = string;
+
 /**
  * Read one criterion's stored hidden-vetting configuration, what it publishes, and the aggregate counts an administrator needs to run it. The outer document members are owned by the framework — SPEC §6.3.
  */
@@ -65,6 +70,7 @@ export interface StoredConfig {
   livePeriods: string[];
   liveTokenLabels: string[];
   dripPerTick: number;
+  tickLength: TickLength;
   events: StoredEvent[];
 }
 export interface StoredEvent {
@@ -108,6 +114,7 @@ export interface PublishedConfig {
   vetterLabels: string[];
   tokenLabels: string[];
   dripPerTick: number;
+  tickLength: TickLength;
   events: PublishedEvent[];
 }
 /**
@@ -306,6 +313,7 @@ export const PAYLOAD_SCHEMA = {
         "livePeriods",
         "liveTokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -343,6 +351,9 @@ export const PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {
@@ -363,6 +374,7 @@ export const PAYLOAD_SCHEMA = {
         "vetterLabels",
         "tokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -399,6 +411,9 @@ export const PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {
@@ -516,6 +531,12 @@ export const PAYLOAD_SCHEMA = {
         }
       }
     },
+    "TickLength": {
+      "title": "TickLength",
+      "type": "string",
+      "pattern": "^P(?:\\d+D(?:T\\d+H)?|T\\d+H)$",
+      "description": "The length of one tick of the drip, as an ISO 8601 duration in days and/or hours — at least `PT1H`. A label's tick `t` is the window starting `t` tick lengths after the label's start (`vtc/vetting/vetters/pcs-tokens`)."
+    },
     "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.",
@@ -652,6 +673,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "livePeriods",
         "liveTokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -689,6 +711,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {
@@ -709,6 +734,7 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         "vetterLabels",
         "tokenLabels",
         "dripPerTick",
+        "tickLength",
         "events"
       ],
       "properties": {
@@ -745,6 +771,9 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "type": "integer",
           "minimum": 1
         },
+        "tickLength": {
+          "$ref": "#/$defs/TickLength"
+        },
         "events": {
           "type": "array",
           "items": {
@@ -862,6 +891,12 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         }
       }
     },
+    "TickLength": {
+      "title": "TickLength",
+      "type": "string",
+      "pattern": "^P(?:\\d+D(?:T\\d+H)?|T\\d+H)$",
+      "description": "The length of one tick of the drip, as an ISO 8601 duration in days and/or hours — at least `PT1H`. A label's tick `t` is the window starting `t` tick lengths after the label's start (`vtc/vetting/vetters/pcs-tokens`)."
+    },
     "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.",

package/src/vtc/vetting/vetters/pcs-tokens/0.1/payload.ts

@@ -15,7 +15,7 @@ export interface VTCVettingPCSTokensPayload {
    */
   label: string;
   /**
-   * The vetter's own schedule counter for this label. It makes `once per tick` a rule the community can enforce without learning whether the vetter has been busy.
+   * Which tick of this label is being drawn: tick `t` is the window starting `t` tick lengths after the label's start instant (see the specification's Definitions). The community refuses a tick that has not begun (`tickNotYet`) and one already served (`alreadyServed`), so the total drawn under a label is bounded by the drip rate times the ticks elapsed.
    */
   tick: number;
   /**
@@ -116,7 +116,7 @@ export const PAYLOAD_SCHEMA = {
     "tick": {
       "type": "integer",
       "minimum": 0,
-      "description": "The vetter's own schedule counter for this label. It makes `once per tick` a rule the community can enforce without learning whether the vetter has been busy."
+      "description": "Which tick of this label is being drawn: tick `t` is the window starting `t` tick lengths after the label's start instant (see the specification's Definitions). The community refuses a tick that has not begun (`tickNotYet`) and one already served (`alreadyServed`), so the total drawn under a label is bounded by the drip rate times the ticks elapsed."
     },
     "requests": {
       "type": "array",