@openvtc/trust-tasks 0.12.9 → 0.12.10

package/src/vtc/endorsements/show/0.1/payload.ts

@@ -39,7 +39,7 @@ export interface Endorsement {
    * The attested claim body, validated against the endorsement type's claimSchema when it declares one.
    */
   claim?: {};
-  issued: IssuedCredential;
+  issued: CredentialReference;
   /**
    * The endorsement's slot on the community's shared Revocation status list. Published, so a foreign verifier can check revocation without contacting this community.
    */
@@ -50,22 +50,18 @@ export interface Endorsement {
   revokedAt?: string | null;
 }
 /**
- * The registry-wide issuance receipt — credentialId, the signed VEC, and expiry.
+ * A pointer to the issued VEC — its identifier and lifetime, not its bytes. `endorsements/issue` additionally returns the credential itself, because that is the one call whose caller has no other way to receive it.
  */
-export interface IssuedCredential {
+export interface CredentialReference {
   credentialId: CredentialId;
-  /**
-   * The issued Verifiable Credential (W3C VC Data Model 2.0), signed by the issuer's key. Opaque to the framework.
-   */
-  credential: {};
   /**
    * When the credential was minted.
    */
   issuedAt?: string;
   /**
-   * When the credential's validUntil falls due.
+   * When it lapses, or null when it does not.
    */
-  expiresAt: string;
+  expiresAt?: string | null;
 }
 
 /** Trust Task type URI. */
@@ -169,8 +165,8 @@ export const PAYLOAD_SCHEMA = {
           "description": "The attested claim body, validated against the endorsement type's claimSchema when it declares one."
         },
         "issued": {
-          "$ref": "#/$defs/IssuedCredential",
-          "description": "The registry-wide issuance receipt — credentialId, the signed VEC, and expiry."
+          "$ref": "#/$defs/CredentialReference",
+          "description": "A pointer to the issued VEC — its identifier and lifetime, not its bytes. `endorsements/issue` additionally returns the credential itself, because that is the one call whose caller has no other way to receive it."
         },
         "statusListIndex": {
           "type": "integer",
@@ -187,34 +183,31 @@ export const PAYLOAD_SCHEMA = {
         }
       }
     },
-    "IssuedCredential": {
-      "$anchor": "issuedCredential",
-      "title": "IssuedCredential",
-      "description": "The receipt for a successfully-minted Verifiable Credential: a stable handle for revocation and audit, the signed credential itself, and when it lapses.\n\nSCOPE — this is an *issuance* receipt, returned by the party that minted the credential. It is not the shape for a *delivery* receipt, where a holder hands an already-issued credential to a party that stores it: such a task returns a receipt naming what was stored (see vtc/members/vmc and vtc/join-requests/accept) and MUST NOT echo the credential back to the party that just sent it. Reaching for this definition on a delivery task is the mistake this paragraph exists to prevent.\n\n`additionalProperties` is false, so a specification needing extra members cannot compose this by `$ref` — `allOf` evaluates each subschema against the whole object and this one would reject them. vta/credentials/issue is that case: its response is this shape plus `supersedes` and `ext`, and it therefore states the members inline while `$ref`-ing the shared CredentialId. That is deliberate, not drift.",
+    "CredentialReference": {
+      "$anchor": "credentialReference",
+      "title": "CredentialReference",
       "type": "object",
       "additionalProperties": false,
+      "description": "A pointer to an issued credential, without the credential itself.\n\nThe counterpart to IssuedCredential, for the far more common case of *reading about* a credential rather than being handed one. A listing that embedded the signed credential in every row would grow with the size of the credentials rather than the number of them — a page of fifty is megabytes — and a reader that only needs to know a credential exists, when it lapses, and how to revoke it does not need the bytes.\n\nThe holder can always fetch the credential itself by `credentialId`, and a verifier can check revocation from the row's status-list slot without either. Reach for IssuedCredential only at the moment of minting, where the caller has no other way to receive what was just made for them.",
       "required": [
-        "credentialId",
-        "credential",
-        "expiresAt"
+        "credentialId"
       ],
       "properties": {
         "credentialId": {
           "$ref": "#/$defs/CredentialId"
         },
-        "credential": {
-          "type": "object",
-          "description": "The issued Verifiable Credential (W3C VC Data Model 2.0), signed by the issuer's key. Opaque to the framework."
-        },
         "issuedAt": {
           "type": "string",
           "format": "date-time",
           "description": "When the credential was minted."
         },
         "expiresAt": {
-          "type": "string",
+          "type": [
+            "string",
+            "null"
+          ],
           "format": "date-time",
-          "description": "When the credential's validUntil falls due."
+          "description": "When it lapses, or null when it does not."
         }
       }
     },
@@ -294,8 +287,8 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
           "description": "The attested claim body, validated against the endorsement type's claimSchema when it declares one."
         },
         "issued": {
-          "$ref": "#/$defs/IssuedCredential",
-          "description": "The registry-wide issuance receipt — credentialId, the signed VEC, and expiry."
+          "$ref": "#/$defs/CredentialReference",
+          "description": "A pointer to the issued VEC — its identifier and lifetime, not its bytes. `endorsements/issue` additionally returns the credential itself, because that is the one call whose caller has no other way to receive it."
         },
         "statusListIndex": {
           "type": "integer",
@@ -312,34 +305,31 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         }
       }
     },
-    "IssuedCredential": {
-      "$anchor": "issuedCredential",
-      "title": "IssuedCredential",
-      "description": "The receipt for a successfully-minted Verifiable Credential: a stable handle for revocation and audit, the signed credential itself, and when it lapses.\n\nSCOPE — this is an *issuance* receipt, returned by the party that minted the credential. It is not the shape for a *delivery* receipt, where a holder hands an already-issued credential to a party that stores it: such a task returns a receipt naming what was stored (see vtc/members/vmc and vtc/join-requests/accept) and MUST NOT echo the credential back to the party that just sent it. Reaching for this definition on a delivery task is the mistake this paragraph exists to prevent.\n\n`additionalProperties` is false, so a specification needing extra members cannot compose this by `$ref` — `allOf` evaluates each subschema against the whole object and this one would reject them. vta/credentials/issue is that case: its response is this shape plus `supersedes` and `ext`, and it therefore states the members inline while `$ref`-ing the shared CredentialId. That is deliberate, not drift.",
+    "CredentialReference": {
+      "$anchor": "credentialReference",
+      "title": "CredentialReference",
       "type": "object",
       "additionalProperties": false,
+      "description": "A pointer to an issued credential, without the credential itself.\n\nThe counterpart to IssuedCredential, for the far more common case of *reading about* a credential rather than being handed one. A listing that embedded the signed credential in every row would grow with the size of the credentials rather than the number of them — a page of fifty is megabytes — and a reader that only needs to know a credential exists, when it lapses, and how to revoke it does not need the bytes.\n\nThe holder can always fetch the credential itself by `credentialId`, and a verifier can check revocation from the row's status-list slot without either. Reach for IssuedCredential only at the moment of minting, where the caller has no other way to receive what was just made for them.",
       "required": [
-        "credentialId",
-        "credential",
-        "expiresAt"
+        "credentialId"
       ],
       "properties": {
         "credentialId": {
           "$ref": "#/$defs/CredentialId"
         },
-        "credential": {
-          "type": "object",
-          "description": "The issued Verifiable Credential (W3C VC Data Model 2.0), signed by the issuer's key. Opaque to the framework."
-        },
         "issuedAt": {
           "type": "string",
           "format": "date-time",
           "description": "When the credential was minted."
         },
         "expiresAt": {
-          "type": "string",
+          "type": [
+            "string",
+            "null"
+          ],
           "format": "date-time",
-          "description": "When the credential's validUntil falls due."
+          "description": "When it lapses, or null when it does not."
         }
       }
     },

package/src/vtc/install/claim/start/0.1/payload.ts

@@ -8,6 +8,14 @@ export interface VTCInstallClaimStartPayload {
    * The EdDSA-signed install JWT (aud=vtc-install) printed by vtc setup.
    */
   installToken: string;
+  /**
+   * A short code the operator receives **out of band**, alongside the install URL but through a separate channel.
+   *
+   * The second factor on a claim: the URL alone is deliberately insufficient, so a stolen or forwarded install link cannot claim the passkey by itself. A maintainer that mints one shows the plaintext once and stores only a hash; a claim that omits or fails it is refused before any registration challenge is issued.
+   *
+   * Optional in the schema because a maintainer may issue tokens without one — but a maintainer that does issue one MUST require it, and SHOULD issue one for any invite that travels over a channel it does not control.
+   */
+  claimSecret?: string;
   ext?: Ext;
 }
 /**
@@ -68,6 +76,11 @@ export const PAYLOAD_SCHEMA = {
       "minLength": 1,
       "description": "The EdDSA-signed install JWT (aud=vtc-install) printed by vtc setup."
     },
+    "claimSecret": {
+      "type": "string",
+      "minLength": 1,
+      "description": "A short code the operator receives **out of band**, alongside the install URL but through a separate channel.\n\nThe second factor on a claim: the URL alone is deliberately insufficient, so a stolen or forwarded install link cannot claim the passkey by itself. A maintainer that mints one shows the plaintext once and stores only a hash; a claim that omits or fails it is refused before any registration challenge is issued.\n\nOptional in the schema because a maintainer may issue tokens without one — but a maintainer that does issue one MUST require it, and SHOULD issue one for any invite that travels over a channel it does not control."
+    },
     "ext": {
       "$ref": "#/$defs/Ext"
     }

package/src/vtc/registry/diagnostics/0.1/payload.ts

@@ -40,6 +40,89 @@ export interface VTCRegistryDiagnosticsResponsePayload {
    */
   lastError?: string | null;
   ext?: Ext;
+  /**
+   * Whether the membership syncer is configured to run at all — false when no trust registry is configured.
+   */
+  syncerEnabled?: boolean;
+  /**
+   * Whether the syncer task is alive right now. `syncerEnabled && !syncerRunning` means spawned but dead — mid-restart after a panic, which no queue count reveals.
+   */
+  syncerRunning?: boolean;
+  /**
+   * How many times the syncer has been restarted after a panic. A rising value is the "it keeps crashing" signal; queue depth alone looks identical to a healthy idle queue.
+   */
+  syncerRestarts?: number;
+  /**
+   * Live messaging connectivity: `connected` when the delivery layer reports a live mediator connection. A re-falsifiable signal read at request time, never a boot-time latch — a maintainer that connected once and dropped must report `disconnected`.
+   */
+  messagingStatus?: "connected" | "disconnected";
+  /**
+   * The DID of the agent this maintainer was provisioned against. Admin-gated rather than public: infrastructure topology is not a free reconnaissance oracle.
+   */
+  vtaDid?: string;
+  /**
+   * The mediator's endpoint, when one is configured.
+   */
+  mediatorUrl?: string | null;
+  /**
+   * The mediator's DID, when one is configured.
+   */
+  mediatorDid?: string | null;
+  registryTransport?: RegistryTransport;
+  /**
+   * Every protocol this maintainer knows about, whether its own document advertises it, and whether it can serve it right now.
+   *
+   * Reports all protocols rather than only the advertised ones, so a client can tell "not advertised" from "absent from an older response".
+   */
+  transports?: TransportStatus[];
+}
+/**
+ * How this maintainer reaches its trust registry, and which protocol the last attempt actually chose.
+ */
+export interface RegistryTransport {
+  /**
+   * The registry's DID, when addressed by one.
+   */
+  did?: string | null;
+  /**
+   * The registry's endpoint, when addressed by one.
+   */
+  url?: string | null;
+  /**
+   * Protocols the registry's own document advertises, in preference order. Empty before the DID has been resolved, or when addressed by URL alone.
+   */
+  advertised?: string[];
+  /**
+   * The protocol the last selection chose. Null before the first call, or when selection failed — see `error`.
+   */
+  active?: string | null;
+  /**
+   * Why the last selection failed, if it did.
+   */
+  error?: string | null;
+}
+/**
+ * One protocol's advertised and serviceable state.
+ *
+ * The two are separate on purpose. `advertised` is read from the DID document; `serviceable` is whether this maintainer can answer on it right now. Advertised-but-not-serviceable is the broken state a single boolean hides; serviceable-but-not-advertised is the staged rollout, where the binary is ready and the document has not caught up.
+ */
+export interface TransportStatus {
+  /**
+   * The protocol this row describes.
+   */
+  protocol: string;
+  /**
+   * Present in the DID document, so a resolving client will find it.
+   */
+  advertised: boolean;
+  /**
+   * This maintainer can answer on it right now. For messaging transports that means the build supports the protocol *and* the connection is live.
+   */
+  serviceable: boolean;
+  /**
+   * The advertised endpoint, or null when not advertised — there is no endpoint to give.
+   */
+  endpoint?: string | null;
 }
 
 /** Trust Task type URI. */
@@ -140,6 +223,136 @@ export const PAYLOAD_SCHEMA = {
         },
         "ext": {
           "$ref": "#/$defs/Ext"
+        },
+        "syncerEnabled": {
+          "type": "boolean",
+          "description": "Whether the membership syncer is configured to run at all — false when no trust registry is configured."
+        },
+        "syncerRunning": {
+          "type": "boolean",
+          "description": "Whether the syncer task is alive right now. `syncerEnabled && !syncerRunning` means spawned but dead — mid-restart after a panic, which no queue count reveals."
+        },
+        "syncerRestarts": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "How many times the syncer has been restarted after a panic. A rising value is the \"it keeps crashing\" signal; queue depth alone looks identical to a healthy idle queue."
+        },
+        "messagingStatus": {
+          "type": "string",
+          "enum": [
+            "connected",
+            "disconnected"
+          ],
+          "description": "Live messaging connectivity: `connected` when the delivery layer reports a live mediator connection. A re-falsifiable signal read at request time, never a boot-time latch — a maintainer that connected once and dropped must report `disconnected`."
+        },
+        "vtaDid": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The DID of the agent this maintainer was provisioned against. Admin-gated rather than public: infrastructure topology is not a free reconnaissance oracle."
+        },
+        "mediatorUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The mediator's endpoint, when one is configured."
+        },
+        "mediatorDid": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The mediator's DID, when one is configured."
+        },
+        "registryTransport": {
+          "$ref": "#/$defs/RegistryTransport",
+          "description": "How this maintainer reaches its trust registry, and which protocol the last attempt actually chose."
+        },
+        "transports": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/TransportStatus"
+          },
+          "description": "Every protocol this maintainer knows about, whether its own document advertises it, and whether it can serve it right now.\n\nReports all protocols rather than only the advertised ones, so a client can tell \"not advertised\" from \"absent from an older response\"."
+        }
+      }
+    },
+    "TransportStatus": {
+      "$anchor": "transportStatus",
+      "title": "TransportStatus",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "One protocol's advertised and serviceable state.\n\nThe two are separate on purpose. `advertised` is read from the DID document; `serviceable` is whether this maintainer can answer on it right now. Advertised-but-not-serviceable is the broken state a single boolean hides; serviceable-but-not-advertised is the staged rollout, where the binary is ready and the document has not caught up.",
+      "required": [
+        "protocol",
+        "advertised",
+        "serviceable"
+      ],
+      "properties": {
+        "protocol": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The protocol this row describes."
+        },
+        "advertised": {
+          "type": "boolean",
+          "description": "Present in the DID document, so a resolving client will find it."
+        },
+        "serviceable": {
+          "type": "boolean",
+          "description": "This maintainer can answer on it right now. For messaging transports that means the build supports the protocol *and* the connection is live."
+        },
+        "endpoint": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The advertised endpoint, or null when not advertised — there is no endpoint to give."
+        }
+      }
+    },
+    "RegistryTransport": {
+      "$anchor": "registryTransport",
+      "title": "RegistryTransport",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "How a maintainer addresses its trust registry, and what the last selection chose.\n\nAdvertised and active are reported separately: a registry that advertises a protocol this maintainer cannot answer is *configured* and *unreachable* at the same time, and one collapsed field cannot say so.",
+      "properties": {
+        "did": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The registry's DID, when addressed by one."
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The registry's endpoint, when addressed by one."
+        },
+        "advertised": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Protocols the registry's own document advertises, in preference order. Empty before the DID has been resolved, or when addressed by URL alone."
+        },
+        "active": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The protocol the last selection chose. Null before the first call, or when selection failed — see `error`."
+        },
+        "error": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Why the last selection failed, if it did."
         }
       }
     },
@@ -226,6 +439,136 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
         },
         "ext": {
           "$ref": "#/$defs/Ext"
+        },
+        "syncerEnabled": {
+          "type": "boolean",
+          "description": "Whether the membership syncer is configured to run at all — false when no trust registry is configured."
+        },
+        "syncerRunning": {
+          "type": "boolean",
+          "description": "Whether the syncer task is alive right now. `syncerEnabled && !syncerRunning` means spawned but dead — mid-restart after a panic, which no queue count reveals."
+        },
+        "syncerRestarts": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "How many times the syncer has been restarted after a panic. A rising value is the \"it keeps crashing\" signal; queue depth alone looks identical to a healthy idle queue."
+        },
+        "messagingStatus": {
+          "type": "string",
+          "enum": [
+            "connected",
+            "disconnected"
+          ],
+          "description": "Live messaging connectivity: `connected` when the delivery layer reports a live mediator connection. A re-falsifiable signal read at request time, never a boot-time latch — a maintainer that connected once and dropped must report `disconnected`."
+        },
+        "vtaDid": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The DID of the agent this maintainer was provisioned against. Admin-gated rather than public: infrastructure topology is not a free reconnaissance oracle."
+        },
+        "mediatorUrl": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The mediator's endpoint, when one is configured."
+        },
+        "mediatorDid": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The mediator's DID, when one is configured."
+        },
+        "registryTransport": {
+          "$ref": "#/$defs/RegistryTransport",
+          "description": "How this maintainer reaches its trust registry, and which protocol the last attempt actually chose."
+        },
+        "transports": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/TransportStatus"
+          },
+          "description": "Every protocol this maintainer knows about, whether its own document advertises it, and whether it can serve it right now.\n\nReports all protocols rather than only the advertised ones, so a client can tell \"not advertised\" from \"absent from an older response\"."
+        }
+      }
+    },
+    "TransportStatus": {
+      "$anchor": "transportStatus",
+      "title": "TransportStatus",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "One protocol's advertised and serviceable state.\n\nThe two are separate on purpose. `advertised` is read from the DID document; `serviceable` is whether this maintainer can answer on it right now. Advertised-but-not-serviceable is the broken state a single boolean hides; serviceable-but-not-advertised is the staged rollout, where the binary is ready and the document has not caught up.",
+      "required": [
+        "protocol",
+        "advertised",
+        "serviceable"
+      ],
+      "properties": {
+        "protocol": {
+          "type": "string",
+          "minLength": 1,
+          "description": "The protocol this row describes."
+        },
+        "advertised": {
+          "type": "boolean",
+          "description": "Present in the DID document, so a resolving client will find it."
+        },
+        "serviceable": {
+          "type": "boolean",
+          "description": "This maintainer can answer on it right now. For messaging transports that means the build supports the protocol *and* the connection is live."
+        },
+        "endpoint": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The advertised endpoint, or null when not advertised — there is no endpoint to give."
+        }
+      }
+    },
+    "RegistryTransport": {
+      "$anchor": "registryTransport",
+      "title": "RegistryTransport",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "How a maintainer addresses its trust registry, and what the last selection chose.\n\nAdvertised and active are reported separately: a registry that advertises a protocol this maintainer cannot answer is *configured* and *unreachable* at the same time, and one collapsed field cannot say so.",
+      "properties": {
+        "did": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The registry's DID, when addressed by one."
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The registry's endpoint, when addressed by one."
+        },
+        "advertised": {
+          "type": "array",
+          "items": {
+            "type": "string",
+            "minLength": 1
+          },
+          "description": "Protocols the registry's own document advertises, in preference order. Empty before the DID has been resolved, or when addressed by URL alone."
+        },
+        "active": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "The protocol the last selection chose. Null before the first call, or when selection failed — see `error`."
+        },
+        "error": {
+          "type": [
+            "string",
+            "null"
+          ],
+          "description": "Why the last selection failed, if it did."
         }
       }
     },

package/src/vtc/website/files/list/0.1/payload.ts

@@ -33,6 +33,10 @@ export interface VTCWebsiteFilesListResponsePayload {
      * File size in bytes.
      */
     size: number;
+    /**
+     * An opaque content hash for the file, matching the `ETag` a direct read of the same path returns. Lets a client detect a change — or confirm one it just wrote — without downloading the body, which is why the listing carries it rather than making the caller fetch each file to compare.
+     */
+    etag?: string;
     modifiedAt?: string;
   }[];
   nextCursor?: string | null;
@@ -111,6 +115,11 @@ export const PAYLOAD_SCHEMA = {
                 "minimum": 0,
                 "description": "File size in bytes."
               },
+              "etag": {
+                "type": "string",
+                "minLength": 1,
+                "description": "An opaque content hash for the file, matching the `ETag` a direct read of the same path returns. Lets a client detect a change — or confirm one it just wrote — without downloading the body, which is why the listing carries it rather than making the caller fetch each file to compare."
+              },
               "modifiedAt": {
                 "type": "string",
                 "format": "date-time"
@@ -177,6 +186,11 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
                 "minimum": 0,
                 "description": "File size in bytes."
               },
+              "etag": {
+                "type": "string",
+                "minLength": 1,
+                "description": "An opaque content hash for the file, matching the `ETag` a direct read of the same path returns. Lets a client detect a change — or confirm one it just wrote — without downloading the body, which is why the listing carries it rather than making the caller fetch each file to compare."
+              },
               "modifiedAt": {
                 "type": "string",
                 "format": "date-time"

package/src/vtc/website/generations/list/0.1/payload.ts

@@ -22,6 +22,14 @@ export interface VTCWebsiteGenerationsListResponsePayload {
      * True for the generation current resolves to.
      */
     current: boolean;
+    /**
+     * When this generation was deployed. A rollback target is chosen by *when* far more often than by number.
+     */
+    deployedAt?: string;
+    /**
+     * Total size of the generation on disk. Distinguishes a real deployment from a truncated or empty one before an operator rolls onto it.
+     */
+    sizeBytes?: number;
   }[];
   ext?: Ext;
 }
@@ -86,6 +94,16 @@ export const PAYLOAD_SCHEMA = {
               "current": {
                 "type": "boolean",
                 "description": "True for the generation current resolves to."
+              },
+              "deployedAt": {
+                "type": "string",
+                "format": "date-time",
+                "description": "When this generation was deployed. A rollback target is chosen by *when* far more often than by number."
+              },
+              "sizeBytes": {
+                "type": "integer",
+                "minimum": 0,
+                "description": "Total size of the generation on disk. Distinguishes a real deployment from a truncated or empty one before an operator rolls onto it."
               }
             }
           }
@@ -140,6 +158,16 @@ export const RESPONSE_PAYLOAD_SCHEMA = {
               "current": {
                 "type": "boolean",
                 "description": "True for the generation current resolves to."
+              },
+              "deployedAt": {
+                "type": "string",
+                "format": "date-time",
+                "description": "When this generation was deployed. A rollback target is chosen by *when* far more often than by number."
+              },
+              "sizeBytes": {
+                "type": "integer",
+                "minimum": 0,
+                "description": "Total size of the generation on disk. Distinguishes a real deployment from a truncated or empty one before an operator rolls onto it."
               }
             }
           }