@openvtc/trust-tasks 0.27.4 → 0.27.5

package/src/vtc/_shared/0.1/community-room.ts

@@ -14,4 +14,4 @@ export interface VTCSharedCommunityOwnedRoomDefinitions {
  * The definitions this shared schema publishes, hoisted to one declaration each.
  * See "../../../_shared/components.js".
  */
-export type { CommunityRoom, CommunityRoomV2_VtcV0_1 as CommunityRoomV2, MemberAction, MemberActions, MemberState, Offer, OfferCredentials, OfferV2, Reason, Renewal, RenewalCredentials, RoomDescription, RoomLabel, RoomMember, RoomMembership, RoomTag, RoomTags } from "../../../_shared/components.js";
+export type { CommunityRoom, CommunityRoomV2_VtcV0_1 as CommunityRoomV2, MemberAction, MemberActions, MemberState, Offer, OfferCredentials, OfferV2, Reason, Renewal_VtcV0_1 as Renewal, RenewalCredentials, RoomDescription, RoomLabel, RoomMember, RoomMembership, RoomTag, RoomTags } from "../../../_shared/components.js";

package/src/vtc/_shared/0.1/relationship-lifecycle.ts

@@ -14,4 +14,4 @@ export interface VTCSharedRelationshipLifecycleDefinitions {
  * The definitions this shared schema publishes, hoisted to one declaration each.
  * See "../../../_shared/components.js".
  */
-export type { InForce, LifecycleReason } from "../../../_shared/components.js";
+export type { InForce_VtcV0_1 as InForce, LifecycleReason } from "../../../_shared/components.js";

package/src/vtc/_shared/0.4/community-room.ts

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/_shared/0.4/community-room.schema.json
+ */
+
+/**
+ * Shared types for rooms a community owns rather than merely hosts: the vtc/rooms/community/* tasks an administrator runs them with, and the vtc/rooms/offers/* tasks a member collects and accepts an admission with. The community is the room's owner; the community's own VTA holds the room's signing key and, on a sealed tier, the community's place in its MLS group. The community holds no room key and no group secret. What it records here is the owner's own record of whom it admitted — never read when the community serves the room as its host, where authorization is the room's credential chain and nothing else. Version 0.3 changed nothing here but where `HostedRoom` comes from: `room` resolves to vtc/_shared/0.3/room-storage, whose `HostedRoom` instants are RFC 3339 strings; every other referenced definition stays at 0.1. Version 0.4 renames `Renewal.renews` to `renewsAt` (type unchanged), for the registry's naming consistency; nothing else changes. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).
+ */
+export interface VTCSharedCommunityOwnedRoomDefinitions {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { MemberAction, MemberActions, OfferCredentials, OfferV2, Renewal_VtcV0_4 as Renewal, RenewalCredentials, RoomDescription, RoomLabel } from "../../../_shared/components.js";

package/src/vtc/_shared/0.4/relationship-lifecycle.ts

@@ -0,0 +1,17 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/_shared/0.4/relationship-lifecycle.schema.json
+ */
+
+/**
+ * Shared types for vtc/relationships/{suspend,restore}: an edge's resolved state after a lifecycle event. Version 0.4 renames `InForce.at` to `endedAt` (type unchanged), for the registry's naming consistency; nothing else changes. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).
+ */
+export interface VTCSharedRelationshipLifecycleDefinitions {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { InForce_VtcV0_4 as InForce, LifecycleReason } from "../../../_shared/components.js";

package/src/vtc/admin/actions/_shared/0.3/action.ts

@@ -0,0 +1,29 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/vtc/admin/actions/_shared/0.3/action.schema.json
+ */
+
+/**
+ * Shared shapes for a Verifiable Trust Community's administrative ACTIONS: operations parked for other administrators' decision instead of being refused.
+ *
+ * THE MODEL. When an administrative operation needs more than its requester's own authority — a grant of administrative authority that needs N-of-M approval, an operator's offline (break-glass) write every administrator must see, a human decision such as a join review — the community does not refuse it. It parks the operation as an Action. An Action names its eligible approvers (or acknowledgers) and, for `approval`, a threshold N. When the N-th approval lands, the community re-checks everything it checked at submission — the requester's standing, each approver's standing, the community's policy, the state the operation acts on — and executes the parked operation EXACTLY ONCE; the action then leaves every administrator's list. One deny closes it for everyone. An open action lapses at `expiresAt`: 72 hours by default, community-configurable between 15 minutes and 14 days.
+ *
+ * COOLING OFF (new in 0.2). Some operations need a third party's agreement that does not exist — the removal of an administrator in a community where nobody other than the requester and the subject holds the authority to consent. The community neither refuses such an operation nor lets it take effect at once: it parks it as a `coolingOff` action, which has no threshold, no approvers and no expiry. It LANDS at `landsAt` — the community executes the parked payload then, exactly once and after the same execution-time re-check as any other action — unless the requester withdraws it with `vtc/admin/actions/cancel` first. The cooling-off period is 24 hours by default and community-configurable. The subject is shown the action (`callerRole: subject`) and told of it by `vtc/members/authority-reduction-pending-notice`, so a reduction nobody else reviewed is never a surprise; the subject cannot block it, because a veto held by the subject would protect a compromised subject from its own removal.
+ *
+ * VERSION 0.3 renames `approvals[].at` to `decidedAt` (type unchanged), for the registry's naming consistency; nothing else changes.
+ *
+ * THE REPLY TO THE REQUESTER. The gated operation is not answered with an error or with its own `#response`. The community answers it with the framework-reserved `trust-task-next-step/0.1`, carrying `continuation: proceed` and one `expects` entry whose `typeUri` is `https://trusttasks.org/spec/vtc/admin/actions/show/0.3` with `hint: {"actionId": "…"}`. `proceed` is deliberate: the requester does NOT re-submit the original operation — the community executes the parked payload itself once the threshold is met — so the requester's next step is to follow the action, not to retry. No separate response specification exists for this reply.
+ *
+ * THE DECISION. A `coolingOff` action takes no decision: nobody approves it and nobody acknowledges it. An approver decides through `task-consent/decision` (0.2 or later), echoing the `challenge` it was shown on the action and quoting `actionId`. An acknowledger answers `acknowledge` actions with `vtc/admin/actions/acknowledge`. The requester may withdraw an open action with `vtc/admin/actions/cancel`.
+ *
+ * WHAT APPROVERS ARE SHOWN. The `summary` is rendered from a SUMMARY TEMPLATE delivered as data — a title, an effect sentence, and named fields each locating a value in the digested payload by JSON Pointer — and the template is pinned per kind by `templateDigest`. A renderer MUST derive every field it shows from `payload` via that field's `pointer`, and MUST refuse to render an action whose carried `value` differs from the value at the pointer, or whose `payloadDigest` does not match `payload`. It MUST NOT present an action from `title` or `effect` text alone: those are prose the community authored, and a decision taken on prose is a decision about whatever the prose claimed rather than about the payload that will execute (VTI-APV-013).
+ */
+export interface VTCAdminActionsSharedDefinitions {
+  [k: string]: unknown | undefined;
+}
+
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../../../_shared/components.js".
+ */
+export type { Action_VtcAdminActionsV0_3 as Action, ActionId, Field, Summary } from "../../../../../_shared/components.js";