@openvtc/trust-tasks 0.22.5 → 0.22.7

package/src/vtc/install/claim/finish/0.3/payload.ts

@@ -0,0 +1,253 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/install/claim/finish/0.3/payload.schema.json
+ */
+
+import type { ApproverDid, ApproverLabel, AttestStatement, Ext } from "../../../../../_shared/components.js";
+
+
+/**
+ * Complete first-administrator enrolment under a DID the founder already controls: the document is signed by the DID the install token names, verified against its live document, and carries the founder's step-up approver's enrolment statement over the claim's challenge. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface VTCInstallClaimFinishPayload {
+  /**
+   * From claim/start 0.3, echoed verbatim. Also the `boundTo` of the statement.
+   */
+  claimId: string;
+  /**
+   * The founder's step-up approver. MUST equal the statement's issuer.
+   */
+  approverDid: ApproverDid;
+  label?: ApproverLabel;
+  /**
+   * The approver's complete, signed auth/step-up/approver/attest/0.1 document with `purpose: enrol`, `boundTo` equal to `claimId`, over the start's `challenge`. Verified as received.
+   */
+  statement: AttestStatement;
+  ext?: Ext;
+}
+export interface VTCInstallClaimFinishResponsePayload {
+  /**
+   * The founder's DID — the DID the install token named and the claim was signed by — which vtc/admin/bootstrap writes as the first administrator.
+   */
+  adminDid: string;
+  /**
+   * EdDSA JWT (aud=vtc-install-session, 5min TTL) consumed by vtc/admin/bootstrap. The approver binding takes effect when it is consumed.
+   */
+  setupSessionToken: string;
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { ApproverDid, ApproverLabel, AttestStatement, Ext };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/vtc/install/claim/finish/0.3" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCInstallClaimFinishPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/install/claim/finish/0.3#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCInstallClaimFinishResponsePayload;
+
+/**
+ * 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/install/claim/finish/0.3",
+  "title": "VTC Install Claim Finish — payload",
+  "description": "Complete first-administrator enrolment under a DID the founder already controls: the document is signed by the DID the install token names, verified against its live document, and carries the founder's step-up approver's enrolment statement over the claim's challenge. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "claimId",
+    "approverDid",
+    "statement"
+  ],
+  "properties": {
+    "claimId": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 256,
+      "description": "From claim/start 0.3, echoed verbatim. Also the `boundTo` of the statement."
+    },
+    "approverDid": {
+      "$ref": "#/$defs/ApproverDid",
+      "description": "The founder's step-up approver. MUST equal the statement's issuer."
+    },
+    "label": {
+      "$ref": "#/$defs/ApproverLabel"
+    },
+    "statement": {
+      "$ref": "#/$defs/AttestStatement",
+      "description": "The approver's complete, signed auth/step-up/approver/attest/0.1 document with `purpose: enrol`, `boundTo` equal to `claimId`, over the start's `challenge`. Verified as received."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Install Claim Finish — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "adminDid",
+        "setupSessionToken"
+      ],
+      "properties": {
+        "adminDid": {
+          "type": "string",
+          "pattern": "^did:",
+          "minLength": 5,
+          "maxLength": 2048,
+          "description": "The founder's DID — the DID the install token named and the claim was signed by — which vtc/admin/bootstrap writes as the first administrator."
+        },
+        "setupSessionToken": {
+          "type": "string",
+          "minLength": 1,
+          "description": "EdDSA JWT (aud=vtc-install-session, 5min TTL) consumed by vtc/admin/bootstrap. The approver binding takes effect when it is consumed."
+        },
+        "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-]+)+$"
+      }
+    },
+    "AttestStatement": {
+      "title": "AttestStatement",
+      "type": "object",
+      "minProperties": 1,
+      "description": "A complete, signed auth/step-up/approver/attest/0.1 Trust Task document — envelope, payload and proof — issued by the approver. Deliberately an open object here rather than a typed one: the consumer verifies it as a document in its own right (envelope, proof and payload against that specification's schemas), and verifies its proof over the members exactly as received, which a binding that narrowed it to a typed struct and re-serialised it could silently break."
+    },
+    "ApproverLabel": {
+      "title": "ApproverLabel",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "description": "A human-readable name for where the approver lives — e.g. `Browser plugin — work laptop`. Chosen by the subject (or suggested by an inviter), untrusted, and attributed to its author wherever it is rendered. Absent rather than invented when none was chosen."
+    },
+    "ApproverDid": {
+      "title": "ApproverDid",
+      "type": "string",
+      "minLength": 16,
+      "maxLength": 128,
+      "pattern": "^did:key:z6Mk[1-9A-HJ-NP-Za-km-z]+$",
+      "description": "A step-up approver, as an Ed25519 `did:key` (`z6Mk…`). `did:key` only, because its document is a function of the key and resolves with no network, so verifying an approver's statement never depends on a fetch, and a key whose DID document could be rewritten after enrolment would not be the key that was enrolled. Distinct from the subject's DID, from every verification method in the subject's DID document, and from every key the subject can sign operations with at the relying party."
+    }
+  }
+} 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 Install Claim Finish — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "adminDid",
+        "setupSessionToken"
+      ],
+      "properties": {
+        "adminDid": {
+          "type": "string",
+          "pattern": "^did:",
+          "minLength": 5,
+          "maxLength": 2048,
+          "description": "The founder's DID — the DID the install token named and the claim was signed by — which vtc/admin/bootstrap writes as the first administrator."
+        },
+        "setupSessionToken": {
+          "type": "string",
+          "minLength": 1,
+          "description": "EdDSA JWT (aud=vtc-install-session, 5min TTL) consumed by vtc/admin/bootstrap. The approver binding takes effect when it is consumed."
+        },
+        "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-]+)+$"
+      }
+    },
+    "AttestStatement": {
+      "title": "AttestStatement",
+      "type": "object",
+      "minProperties": 1,
+      "description": "A complete, signed auth/step-up/approver/attest/0.1 Trust Task document — envelope, payload and proof — issued by the approver. Deliberately an open object here rather than a typed one: the consumer verifies it as a document in its own right (envelope, proof and payload against that specification's schemas), and verifies its proof over the members exactly as received, which a binding that narrowed it to a typed struct and re-serialised it could silently break."
+    },
+    "ApproverLabel": {
+      "title": "ApproverLabel",
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "description": "A human-readable name for where the approver lives — e.g. `Browser plugin — work laptop`. Chosen by the subject (or suggested by an inviter), untrusted, and attributed to its author wherever it is rendered. Absent rather than invented when none was chosen."
+    },
+    "ApproverDid": {
+      "title": "ApproverDid",
+      "type": "string",
+      "minLength": 16,
+      "maxLength": 128,
+      "pattern": "^did:key:z6Mk[1-9A-HJ-NP-Za-km-z]+$",
+      "description": "A step-up approver, as an Ed25519 `did:key` (`z6Mk…`). `did:key` only, because its document is a function of the key and resolves with no network, so verifying an approver's statement never depends on a fetch, and a key whose DID document could be rewritten after enrolment would not be the key that was enrolled. Distinct from the subject's DID, from every verification method in the subject's DID document, and from every key the subject can sign operations with at the relying party."
+    }
+  }
+} 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/install/claim/start/0.3/payload.ts

@@ -0,0 +1,256 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/install/claim/start/0.3/payload.schema.json
+ */
+
+import type { Ext } from "../../../../../_shared/components.js";
+
+
+/**
+ * Begin claiming a fresh community under a DID the founder already controls: exchange the install token and its claim code for a challenge the founder's step-up approver will sign. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface VTCInstallClaimStartPayload {
+  /**
+   * The EdDSA-signed install JWT (aud=vtc-install) printed by vtc setup. In 0.3 it names the founder's DID.
+   */
+  token: string;
+  /**
+   * The claim code the operator received out of band, through a different channel from the install URL. Required in 0.3. Compared with its stored hash; never logged.
+   */
+  claimCode: string;
+  ext?: Ext;
+}
+export interface VTCInstallClaimStartResponsePayload {
+  /**
+   * Opaque, single-use handle for this claim. Echoed in claim/finish, and the `boundTo` of the approver's enrolment statement.
+   */
+  claimId: string;
+  /**
+   * The DID the install token names — the DID that must sign claim/finish and that becomes the first administrator. Returned so the installer need not decode the token.
+   */
+  adminDid: string;
+  /**
+   * A fresh challenge (≥128 bits) the founder's step-up approver signs over in its auth/step-up/approver/attest/0.1 statement with `purpose: enrol`.
+   */
+  challenge: string;
+  /**
+   * The community's DID, which the statement names as its `audience` and `recipient`, and to which claim/finish is addressed.
+   */
+  audience: string;
+  /**
+   * When this claim ceremony lapses (not the install token).
+   */
+  expiresAt: 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/install/claim/start/0.3" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCInstallClaimStartPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/vtc/install/claim/start/0.3#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = VTCInstallClaimStartResponsePayload;
+
+/**
+ * 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/install/claim/start/0.3",
+  "title": "VTC Install Claim Start — payload",
+  "description": "Begin claiming a fresh community under a DID the founder already controls: exchange the install token and its claim code for a challenge the founder's step-up approver will sign. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "token",
+    "claimCode"
+  ],
+  "properties": {
+    "token": {
+      "type": "string",
+      "minLength": 16,
+      "maxLength": 4096,
+      "description": "The EdDSA-signed install JWT (aud=vtc-install) printed by vtc setup. In 0.3 it names the founder's DID."
+    },
+    "claimCode": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 64,
+      "description": "The claim code the operator received out of band, through a different channel from the install URL. Required in 0.3. Compared with its stored hash; never logged."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "VTC Install Claim Start — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "claimId",
+        "adminDid",
+        "challenge",
+        "audience",
+        "expiresAt"
+      ],
+      "properties": {
+        "claimId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 256,
+          "description": "Opaque, single-use handle for this claim. Echoed in claim/finish, and the `boundTo` of the approver's enrolment statement."
+        },
+        "adminDid": {
+          "type": "string",
+          "pattern": "^did:",
+          "minLength": 5,
+          "maxLength": 2048,
+          "description": "The DID the install token names — the DID that must sign claim/finish and that becomes the first administrator. Returned so the installer need not decode the token."
+        },
+        "challenge": {
+          "type": "string",
+          "minLength": 16,
+          "maxLength": 512,
+          "description": "A fresh challenge (≥128 bits) the founder's step-up approver signs over in its auth/step-up/approver/attest/0.1 statement with `purpose: enrol`."
+        },
+        "audience": {
+          "type": "string",
+          "pattern": "^did:",
+          "minLength": 5,
+          "maxLength": 2048,
+          "description": "The community's DID, which the statement names as its `audience` and `recipient`, and to which claim/finish is addressed."
+        },
+        "expiresAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When this claim ceremony lapses (not the install token)."
+        },
+        "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-]+)+$"
+      }
+    }
+  }
+} 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 Install Claim Start — response payload",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "claimId",
+        "adminDid",
+        "challenge",
+        "audience",
+        "expiresAt"
+      ],
+      "properties": {
+        "claimId": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 256,
+          "description": "Opaque, single-use handle for this claim. Echoed in claim/finish, and the `boundTo` of the approver's enrolment statement."
+        },
+        "adminDid": {
+          "type": "string",
+          "pattern": "^did:",
+          "minLength": 5,
+          "maxLength": 2048,
+          "description": "The DID the install token names — the DID that must sign claim/finish and that becomes the first administrator. Returned so the installer need not decode the token."
+        },
+        "challenge": {
+          "type": "string",
+          "minLength": 16,
+          "maxLength": 512,
+          "description": "A fresh challenge (≥128 bits) the founder's step-up approver signs over in its auth/step-up/approver/attest/0.1 statement with `purpose: enrol`."
+        },
+        "audience": {
+          "type": "string",
+          "pattern": "^did:",
+          "minLength": 5,
+          "maxLength": 2048,
+          "description": "The community's DID, which the statement names as its `audience` and `recipient`, and to which claim/finish is addressed."
+        },
+        "expiresAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When this claim ceremony lapses (not the install token)."
+        },
+        "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-]+)+$"
+      }
+    }
+  }
+} 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: 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: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: true,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

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

@@ -0,0 +1,162 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/members/authority-reduced-notice/0.1/payload.schema.json
+ */
+
+import type { Ext } from "../../../../_shared/components.js";
+
+
+/**
+ * A community tells a subject that an administrator reduced their administrative authority — revoked their entry, demoted their role, or narrowed what it allows — on whose authority, when, why, and whether anyone else agreed. Unsolicited: the subject did not ask. The removal of a member is vtc/members/removal-notice; this is the reduction of authority, which may leave the subject a member.
+ */
+export interface VTCMembersAuthorityReducedNoticePayload {
+  /**
+   * The subject whose authority was reduced — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice still names its subject.
+   */
+  did: string;
+  /**
+   * What happened. `revoked`: the subject's access control entry was removed. `demoted`: its role was changed to one with a lower ceiling. `narrowed`: its role stayed and what it allows was reduced.
+   */
+  code: "revoked" | "demoted" | "narrowed";
+  /**
+   * The role the subject held before the change.
+   */
+  previousRole: string;
+  /**
+   * The role the subject holds after the change. Absent exactly when `code` is `revoked`.
+   */
+  resultingRole?: string;
+  /**
+   * Whether a party other than the deciding administrator and the subject agreed. `consented`: the reduction ran on the consent of at least one other administrator. `unopposed`: nobody other than the decider and the subject held the authority to consent, so the decider's own re-authentication was the only gate. The distinction is the subject's evidence that a reduction no third party reviewed happened.
+   */
+  agreement: "consented" | "unopposed";
+  /**
+   * The deciding administrator's stated reason, verbatim. Absent when none was given; absent and empty are different claims.
+   */
+  reason?: string;
+  /**
+   * When the reduction took effect — not when the notice was sent.
+   */
+  decidedAt: string;
+  /**
+   * DID of the administrator who decided. The community itself is the document's issuer.
+   */
+  decidedBy: 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/authority-reduced-notice/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = VTCMembersAuthorityReducedNoticePayload;
+
+/**
+ * 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/authority-reduced-notice/0.1",
+  "title": "VTC Members Authority-Reduced Notice — payload",
+  "description": "A community tells a subject that an administrator reduced their administrative authority — revoked their entry, demoted their role, or narrowed what it allows — on whose authority, when, why, and whether anyone else agreed. Unsolicited: the subject did not ask. The removal of a member is vtc/members/removal-notice; this is the reduction of authority, which may leave the subject a member.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "did",
+    "code",
+    "previousRole",
+    "decidedAt",
+    "decidedBy",
+    "agreement"
+  ],
+  "properties": {
+    "did": {
+      "type": "string",
+      "minLength": 1,
+      "description": "The subject whose authority was reduced — the notice's recipient. Carried in the payload as well as the envelope so that a forwarded notice still names its subject."
+    },
+    "code": {
+      "type": "string",
+      "enum": [
+        "revoked",
+        "demoted",
+        "narrowed"
+      ],
+      "description": "What happened. `revoked`: the subject's access control entry was removed. `demoted`: its role was changed to one with a lower ceiling. `narrowed`: its role stayed and what it allows was reduced."
+    },
+    "previousRole": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "description": "The role the subject held before the change."
+    },
+    "resultingRole": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 128,
+      "description": "The role the subject holds after the change. Absent exactly when `code` is `revoked`."
+    },
+    "agreement": {
+      "type": "string",
+      "enum": [
+        "consented",
+        "unopposed"
+      ],
+      "description": "Whether a party other than the deciding administrator and the subject agreed. `consented`: the reduction ran on the consent of at least one other administrator. `unopposed`: nobody other than the decider and the subject held the authority to consent, so the decider's own re-authentication was the only gate. The distinction is the subject's evidence that a reduction no third party reviewed happened."
+    },
+    "reason": {
+      "type": "string",
+      "maxLength": 1024,
+      "description": "The deciding administrator's stated reason, verbatim. Absent when none was given; absent and empty are different claims."
+    },
+    "decidedAt": {
+      "type": "string",
+      "format": "date-time",
+      "description": "When the reduction took effect — not when the notice was sent."
+    },
+    "decidedBy": {
+      "type": "string",
+      "minLength": 1,
+      "description": "DID of the administrator who decided. The community itself is the document's issuer."
+    },
+    "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;