patchwork-os 1.1.0-beta.4.canary.480 → 1.1.0-beta.4.canary.482

package/dist/workers/boundaryPreview.d.ts

@@ -0,0 +1,47 @@
+/**
+ * The control boundary for a live worker — composition, not policy.
+ *
+ * `previewActions` answers "what would the gate say about these candidates?"
+ * given a worker and its trust store. This resolves those two from a recipe
+ * name, so a caller with nothing but "release-notes" can render the boundary.
+ *
+ * It reuses `loadWorkerTrustForRecipe` — the same resolution the live gate
+ * performs in `buildWorkerAutonomyGate`. That matters for the same reason
+ * `previewActions` reuses `decideWorkerAction`: if the preview resolved trust
+ * its own way, it could show a boundary computed from a different worker
+ * manifest or a staler store than the one enforcement will use, and be
+ * confidently wrong. Every layer of this screen has to be a view of the gate.
+ *
+ * Returns null when no worker owns the recipe — the honest answer, and
+ * distinguishable from "a worker that may do nothing", which is an empty
+ * boundary rather than a missing one.
+ */
+import type { ForbidRule } from "./forbidPolicy.js";
+import { type ActionBoundary, type CandidateAction } from "./previewActions.js";
+import type { RunWorkerShadowOpts } from "./runWorkerShadow.js";
+export interface WorkerBoundary {
+    workerId: string;
+    workerName: string;
+    recipeName: string;
+    boundary: ActionBoundary;
+    /**
+     * False when the worker-autonomy flag is off. The boundary is still computed
+     * and still correct as a statement of policy — but nothing is enforcing it,
+     * and a screen that does not say so would imply protection that is not
+     * running. The caller must surface this.
+     */
+    enforced: boolean;
+}
+export interface BoundaryPreviewOpts {
+    /** Caller-supplied candidates. Omitted ⇒ derived from the worker's `owns`. */
+    candidates?: readonly CandidateAction[];
+    forbidRules?: readonly ForbidRule[];
+    trustOpts?: RunWorkerShadowOpts;
+}
+/**
+ * Compute the control boundary for whichever worker owns `recipeName`.
+ *
+ * Read-only: resolves trust, evaluates hypotheticals, writes nothing. No
+ * approval is enqueued and no decision is recorded — see `previewActions`.
+ */
+export declare function boundaryForRecipe(recipeName: string, opts?: BoundaryPreviewOpts): WorkerBoundary | null;

package/dist/workers/boundaryPreview.js

@@ -0,0 +1,48 @@
+/**
+ * The control boundary for a live worker — composition, not policy.
+ *
+ * `previewActions` answers "what would the gate say about these candidates?"
+ * given a worker and its trust store. This resolves those two from a recipe
+ * name, so a caller with nothing but "release-notes" can render the boundary.
+ *
+ * It reuses `loadWorkerTrustForRecipe` — the same resolution the live gate
+ * performs in `buildWorkerAutonomyGate`. That matters for the same reason
+ * `previewActions` reuses `decideWorkerAction`: if the preview resolved trust
+ * its own way, it could show a boundary computed from a different worker
+ * manifest or a staler store than the one enforcement will use, and be
+ * confidently wrong. Every layer of this screen has to be a view of the gate.
+ *
+ * Returns null when no worker owns the recipe — the honest answer, and
+ * distinguishable from "a worker that may do nothing", which is an empty
+ * boundary rather than a missing one.
+ */
+import { FLAG_WORKER_AUTONOMY, isEnabled } from "../featureFlags.js";
+import { defaultCandidatesFor, previewActions, } from "./previewActions.js";
+import { loadWorkerTrustForRecipe } from "./runWorkerShadow.js";
+/**
+ * Compute the control boundary for whichever worker owns `recipeName`.
+ *
+ * Read-only: resolves trust, evaluates hypotheticals, writes nothing. No
+ * approval is enqueued and no decision is recorded — see `previewActions`.
+ */
+export function boundaryForRecipe(recipeName, opts = {}) {
+    const trust = loadWorkerTrustForRecipe(recipeName, opts.trustOpts);
+    if (!trust)
+        return null;
+    const { worker, store } = trust;
+    const candidates = opts.candidates ?? defaultCandidatesFor(worker);
+    return {
+        workerId: worker.id,
+        workerName: worker.name,
+        recipeName,
+        boundary: previewActions(worker, candidates, store, {
+            ...(opts.forbidRules ? { forbidRules: opts.forbidRules } : {}),
+        }),
+        // Deliberately reported rather than used to suppress the result. An
+        // operator asking "what may this worker do?" while the flag is off should
+        // get the answer AND be told it is not being enforced — hiding the boundary
+        // would leave them with no information at all, which is worse.
+        enforced: isEnabled(FLAG_WORKER_AUTONOMY),
+    };
+}
+//# sourceMappingURL=boundaryPreview.js.map

package/dist/workers/boundaryPreview.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"boundaryPreview.js","sourceRoot":"","sources":["../../src/workers/boundaryPreview.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EAAE,oBAAoB,EAAE,SAAS,EAAE,MAAM,oBAAoB,CAAC;AAErE,OAAO,EAGL,oBAAoB,EACpB,cAAc,GACf,MAAM,qBAAqB,CAAC;AAE7B,OAAO,EAAE,wBAAwB,EAAE,MAAM,sBAAsB,CAAC;AAuBhE;;;;;GAKG;AACH,MAAM,UAAU,iBAAiB,CAC/B,UAAkB,EAClB,OAA4B,EAAE;IAE9B,MAAM,KAAK,GAAG,wBAAwB,CAAC,UAAU,EAAE,IAAI,CAAC,SAAS,CAAC,CAAC;IACnE,IAAI,CAAC,KAAK;QAAE,OAAO,IAAI,CAAC;IAExB,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,CAAC;IAChC,MAAM,UAAU,GAAG,IAAI,CAAC,UAAU,IAAI,oBAAoB,CAAC,MAAM,CAAC,CAAC;IAEnE,OAAO;QACL,QAAQ,EAAE,MAAM,CAAC,EAAE;QACnB,UAAU,EAAE,MAAM,CAAC,IAAI;QACvB,UAAU;QACV,QAAQ,EAAE,cAAc,CAAC,MAAM,EAAE,UAAU,EAAE,KAAK,EAAE;YAClD,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAC/D,CAAC;QACF,oEAAoE;QACpE,0EAA0E;QAC1E,4EAA4E;QAC5E,+DAA+D;QAC/D,QAAQ,EAAE,SAAS,CAAC,oBAAoB,CAAC;KAC1C,CAAC;AACJ,CAAC"}

package/dist/workers/previewActions.d.ts

@@ -37,7 +37,7 @@
  * that never happened.
  */
 import type { ForbidRule } from "./forbidPolicy.js";
-import type { WorkerManifest } from "./worker.js";
+import { type WorkerManifest } from "./worker.js";
 import type { WorkerLevelStore } from "./workerLevelStore.js";
 /** An action to ask about. `label` is what a person should see. */
 export interface CandidateAction {
@@ -78,3 +78,27 @@ export interface PreviewOpts {
 export declare function previewActions(worker: WorkerManifest, candidates: readonly CandidateAction[], store: WorkerLevelStore, opts?: PreviewOpts): ActionBoundary;
 /** Total candidates evaluated — for a "N actions considered" caption. */
 export declare function boundarySize(b: ActionBoundary): number;
+/**
+ * The default candidate set for a worker: every action-class tool it owns.
+ *
+ * A boundary screen needs something to evaluate. Making the caller always
+ * supply that list would mean the generic product has no default view, and the
+ * only way to see a worker's boundary would be to hand-write its actions —
+ * which is fine for a scripted walkthrough and useless for an operator asking
+ * "what can this thing actually do?".
+ *
+ * So the default is derived from the worker's own manifest: the tools the
+ * classifier knows (`knownActionTools`), filtered to the classes this worker
+ * `owns`. That is the honest answer to the question, because a worker's `owns`
+ * IS the declaration of what it is for.
+ *
+ * Deliberately NOT the whole tool registry. Showing every tool in the product
+ * would bury the handful that matter under a hundred rows the worker will never
+ * touch, and every one of them would land in "needs approval" — a screen that
+ * is technically true and tells an operator nothing.
+ *
+ * Callers with a specific set in mind (a case, a scripted scenario) pass their
+ * own candidates to `previewActions` instead. This is the default, not the
+ * only, list.
+ */
+export declare function defaultCandidatesFor(worker: WorkerManifest): CandidateAction[];

package/dist/workers/previewActions.js

@@ -36,6 +36,8 @@
  * not a decision, and writing one would pollute the audit trail with things
  * that never happened.
  */
+import { classifyActionClass, knownActionTools } from "./actionClass.js";
+import { ownsAction } from "./worker.js";
 import { decideWorkerAction, gateOutcomeFor } from "./workerGate.js";
 /**
  * Bucket candidate actions into the three columns.
@@ -83,4 +85,33 @@ export function previewActions(worker, candidates, store, opts = {}) {
 export function boundarySize(b) {
     return b.mayDoNow.length + b.needsApproval.length + b.notPermitted.length;
 }
+/**
+ * The default candidate set for a worker: every action-class tool it owns.
+ *
+ * A boundary screen needs something to evaluate. Making the caller always
+ * supply that list would mean the generic product has no default view, and the
+ * only way to see a worker's boundary would be to hand-write its actions —
+ * which is fine for a scripted walkthrough and useless for an operator asking
+ * "what can this thing actually do?".
+ *
+ * So the default is derived from the worker's own manifest: the tools the
+ * classifier knows (`knownActionTools`), filtered to the classes this worker
+ * `owns`. That is the honest answer to the question, because a worker's `owns`
+ * IS the declaration of what it is for.
+ *
+ * Deliberately NOT the whole tool registry. Showing every tool in the product
+ * would bury the handful that matter under a hundred rows the worker will never
+ * touch, and every one of them would land in "needs approval" — a screen that
+ * is technically true and tells an operator nothing.
+ *
+ * Callers with a specific set in mind (a case, a scripted scenario) pass their
+ * own candidates to `previewActions` instead. This is the default, not the
+ * only, list.
+ */
+export function defaultCandidatesFor(worker) {
+    return knownActionTools()
+        .filter((toolName) => ownsAction(worker, classifyActionClass(toolName)))
+        .sort()
+        .map((toolName) => ({ toolName }));
+}
 //# sourceMappingURL=previewActions.js.map

package/dist/workers/previewActions.js.map

@@ -1 +1 @@
-{"version":3,"file":"previewActions.js","sourceRoot":"","sources":["../../src/workers/previewActions.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AAIH,OAAO,EAAE,kBAAkB,EAAE,cAAc,EAAE,MAAM,iBAAiB,CAAC;AAoCrE;;;;;;GAMG;AACH,MAAM,UAAU,cAAc,CAC5B,MAAsB,EACtB,UAAsC,EACtC,KAAuB,EACvB,OAAoB,EAAE;IAEtB,MAAM,QAAQ,GAAmB;QAC/B,QAAQ,EAAE,EAAE;QACZ,aAAa,EAAE,EAAE;QACjB,YAAY,EAAE,EAAE;KACjB,CAAC;IAEF,KAAK,MAAM,CAAC,IAAI,UAAU,EAAE,CAAC;QAC3B,MAAM,QAAQ,GAAG,kBAAkB,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,KAAK,EAAE;YACvE,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;YAC9D,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAC/D,CAAC,CAAC;QAEH,MAAM,KAAK,GAAoB;YAC7B,KAAK,EAAE,CAAC,CAAC,KAAK,IAAI,CAAC,CAAC,QAAQ;YAC5B,QAAQ,EAAE,CAAC,CAAC,QAAQ;YACpB,QAAQ,EAAE,QAAQ,CAAC,QAAQ;YAC3B,MAAM,EAAE,QAAQ,CAAC,MAAM;SACxB,CAAC;QAEF,wEAAwE;QACxE,sDAAsD;QACtD,QAAQ,cAAc,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC;YACxC,KAAK,MAAM;gBACT,QAAQ,CAAC,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;gBAC9B,MAAM;YACR,KAAK,OAAO;gBACV,QAAQ,CAAC,aAAa,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;gBACnC,MAAM;YACR;gBACE,qEAAqE;gBACrE,kEAAkE;gBAClE,QAAQ,CAAC,YAAY,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;gBAClC,MAAM;QACV,CAAC;IACH,CAAC;IAED,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED,yEAAyE;AACzE,MAAM,UAAU,YAAY,CAAC,CAAiB;IAC5C,OAAO,CAAC,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,CAAC,aAAa,CAAC,MAAM,GAAG,CAAC,CAAC,YAAY,CAAC,MAAM,CAAC;AAC5E,CAAC"}
+{"version":3,"file":"previewActions.js","sourceRoot":"","sources":["../../src/workers/previewActions.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AAEH,OAAO,EAAE,mBAAmB,EAAE,gBAAgB,EAAE,MAAM,kBAAkB,CAAC;AAEzE,OAAO,EAAE,UAAU,EAAuB,MAAM,aAAa,CAAC;AAC9D,OAAO,EAAE,kBAAkB,EAAE,cAAc,EAAE,MAAM,iBAAiB,CAAC;AAoCrE;;;;;;GAMG;AACH,MAAM,UAAU,cAAc,CAC5B,MAAsB,EACtB,UAAsC,EACtC,KAAuB,EACvB,OAAoB,EAAE;IAEtB,MAAM,QAAQ,GAAmB;QAC/B,QAAQ,EAAE,EAAE;QACZ,aAAa,EAAE,EAAE;QACjB,YAAY,EAAE,EAAE;KACjB,CAAC;IAEF,KAAK,MAAM,CAAC,IAAI,UAAU,EAAE,CAAC;QAC3B,MAAM,QAAQ,GAAG,kBAAkB,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,KAAK,EAAE;YACvE,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;YAC9D,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAC/D,CAAC,CAAC;QAEH,MAAM,KAAK,GAAoB;YAC7B,KAAK,EAAE,CAAC,CAAC,KAAK,IAAI,CAAC,CAAC,QAAQ;YAC5B,QAAQ,EAAE,CAAC,CAAC,QAAQ;YACpB,QAAQ,EAAE,QAAQ,CAAC,QAAQ;YAC3B,MAAM,EAAE,QAAQ,CAAC,MAAM;SACxB,CAAC;QAEF,wEAAwE;QACxE,sDAAsD;QACtD,QAAQ,cAAc,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC;YACxC,KAAK,MAAM;gBACT,QAAQ,CAAC,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;gBAC9B,MAAM;YACR,KAAK,OAAO;gBACV,QAAQ,CAAC,aAAa,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;gBACnC,MAAM;YACR;gBACE,qEAAqE;gBACrE,kEAAkE;gBAClE,QAAQ,CAAC,YAAY,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;gBAClC,MAAM;QACV,CAAC;IACH,CAAC;IAED,OAAO,QAAQ,CAAC;AAClB,CAAC;AAED,yEAAyE;AACzE,MAAM,UAAU,YAAY,CAAC,CAAiB;IAC5C,OAAO,CAAC,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,CAAC,aAAa,CAAC,MAAM,GAAG,CAAC,CAAC,YAAY,CAAC,MAAM,CAAC;AAC5E,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,UAAU,oBAAoB,CAClC,MAAsB;IAEtB,OAAO,gBAAgB,EAAE;SACtB,MAAM,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,UAAU,CAAC,MAAM,EAAE,mBAAmB,CAAC,QAAQ,CAAC,CAAC,CAAC;SACvE,IAAI,EAAE;SACN,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAC,CAAC;AACvC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchwork-os",
-  "version": "1.1.0-beta.4.canary.480",
+  "version": "1.1.0-beta.4.canary.482",
   "description": "Your personal AI runtime, local-first. Patchwork OS gives any AI model a consistent set of tools, YAML recipes, a delegation policy with approval queue, and a durable trace memory — all on your machine, all under your policy.",
   "type": "module",
   "main": "dist/index.js",