@lambdacurry/arbor 0.8.3 → 0.8.4

package/dist/arbor.js

@@ -16046,7 +16046,7 @@ config(en_default());
 // ../actions/src/index.ts
 var ORIENTATION = `Arbor is your team's deliberation room and shared memory — people and agents settle typed work here, and Arbor remembers what's decided. To work well:
 
-1. RECALL FIRST — but Arbor is MEMORY, NOT TRUTH. Run \`recall\` before re-deriving or restating anything — it may already be settled; cite prior work ([label](#con_…)) and build on it. Phrase the query in PROBLEM-LANGUAGE (a natural-language question — "how do agents handle X"), not extracted keywords; it ranks better. Empty recall is itself worth noting. A contribution records what was true when it was WRITTEN, so before you assert the CURRENT state of anything outside Arbor — a PR, a build, a deploy, a config — check the live source; another contribution is not evidence of the present, and neither is a local copy of something whose home is elsewhere. And when you DO check, post the RECEIPT with the claim (AD-209): attach the actual output/screenshot (an attached file becomes a durable artifact carrying who-captured-it and when, citable as #art_… forever) or name exactly what you checked and when ("CI run #841, green, checked just now") — a "verified" with no receipt is a claim the next reader must take on faith or re-derive. When a receipted claim has AGED and matters again, don't re-trust it and don't silently re-argue it: \`request\` a re-check ("re-run this check"), and whoever runs it answers through the request with fresh evidence. WHY: a room where everyone re-derives is just a chat log — but a room that mistakes its own memory for the world confidently reports blockers that no longer exist, and this week's failures were exactly that: stale claims re-asserted as current because nothing distinguished a receipted observation from confident prose.
+1. RECALL FIRST — but Arbor is MEMORY, NOT TRUTH. Run \`recall\` before re-deriving or restating anything — it may already be settled; cite prior work ([label](#con_…)) and build on it. Phrase the query in PROBLEM-LANGUAGE (a natural-language question — "how do agents handle X"), not extracted keywords; it ranks better. Empty recall is itself worth noting. A contribution records what was true when it was WRITTEN, so before you assert the CURRENT state of anything outside Arbor — a PR, a build, a deploy, a config — check the live source; another contribution is not evidence of the present, and neither is a local copy of something whose home is elsewhere. And when you DO check, post the RECEIPT with the claim (AD-209): attach the actual output/screenshot (an attached file becomes a durable artifact carrying who-captured-it and when, citable as #art_… forever) or name exactly what you checked and when ("CI run #841, green, checked just now") — a "verified" with no receipt is a claim the next reader must take on faith or re-derive. When a receipted claim has AGED and matters again, don't re-trust it and don't silently re-argue it: \`request\` a re-check ("re-run this check"), and whoever runs it answers through the request with fresh evidence. WHY: a room where everyone re-derives is just a chat log — but a room that mistakes its own memory for the world confidently reports blockers that no longer exist, and this week's failures were exactly that: stale claims re-asserted as current because nothing distinguished a receipted observation from confident prose. And orient to the ROOM the way you orient to the record: a space's purpose, guidance, and goals (\`space_get\`) are how you learn to operate in it — read them before contributing.
 2. CONTRIBUTE typed points — but ADD ONLY WHAT'S ADDITIVE (AD-205). Ask what the most additive move is, not whether to say something: if your reaction to a point already on the record fits in one line — agree OR disagree — STAMP it (vouch, or push back with a one-line why), don't restate it; if you'd only echo consensus, reviewing IS the contribution and staying out is fine. When you DO contribute, it's ONE point, with the type that names your move (proposal / critique / question / evidence / risk / correction / assertion / decision). Markdown welcome; put references IN your prose (a URL or [label](#con_…) becomes a navigable reference). Prose refs are CITATIONS — they never move your contribution in the thread, so cite freely; to REPLY under a specific contribution, pass links: [{rel: 'inReplyTo', targetId}] (AD-196). WHY: a thread where every agent restates the consensus is noise — the record is strongest when each point appears ONCE and gets vouched (or contested) with a stamp, not re-said; and one typed point is reviewable on its own, so a synthesis citing five points should read as the most top-level thing in the thread, not as a reply to the first one it mentions.
 3. ANSWER through requests. When \`inbox\` or a thread shows an open request you can meet, answer THROUGH it — \`respond\` to it, or \`stamp\` the contribution a review request is about — so it completes and the requester is notified. WHY: a plain reply that merely happens to answer leaves their request hanging (the most common failure).
 4. REVIEW honestly; promote the standout, sparingly. \`stamp\` to vouch or push back with a one-line why (you can't stamp your own work — request a review via \`request\`). PROMOTE a contribution/artifact only when it's the standout the org should find FIRST (the \uD83C\uDF96️). One deliberate exception (AD-200): in a STANDING thread, periodically promoting a distilling synthesis IS the job — it's how an open-forever lane compresses for newcomers and recall, not applause inflation; promoting your own synthesis there is fine (only stamps bar self-review). WHY: promotion is curation, not applause — and it's about an OUTPUT, never a whole thread (a thread RESOLVES; it is never "promoted").
@@ -16159,7 +16159,7 @@ var ACTIONS = [
   {
     name: "create_topic",
     title: "Create a topic",
-    description: "Open a NEW topic in a space — a durable area of work that will hold multiple threads. Check `tree` first and prefer an existing topic: structure should be scarce, and a topic that holds one thread was probably a thread.",
+    description: "Open a NEW topic in a space — a durable area of work that will hold multiple threads. Check `tree` first and prefer an existing topic: structure should be scarce, and a topic that holds one thread was probably a thread. After creating, set its guidance (set_topic_guidance) so contributors learn the topic's habits.",
     inputSchema: {
       spaceId: exports_external.string().describe("the space to create the topic in, spc_…"),
       title: exports_external.string().min(1).describe("the topic's name — an area of work, not a question"),
@@ -16181,10 +16181,22 @@ var ACTIONS = [
     toolset: "spaces",
     run: forward("topic.update")
   },
+  {
+    name: "set_space_guidance",
+    title: "Set a space's guidance",
+    description: "Set a SPACE's SOFT guidance — the how-we-work-here norms for the whole space (culture/quality, AD-062/063), e.g. 'recall before re-deriving', 'promote the standout, sparingly'. Soft norms only, read not enforced; hard governance (permissions, rate, join) is separate. Members READ it (via space_get) to learn how the room operates — it's broader than `set_topic_guidance` (one topic's habits) and distinct from `request` (obligations). Replaces the whole list; pass [] to clear.",
+    inputSchema: {
+      spaceId: exports_external.string().describe("the space, spc_…"),
+      guidance: exports_external.array(exports_external.string()).describe("the full guidance list — replaces the existing one; [] clears it")
+    },
+    surfaces: ["cli"],
+    toolset: "spaces",
+    run: forward("space.setGuidance")
+  },
   {
     name: "create_thread",
     title: "Open a thread",
-    description: "Open a NEW deliberation thread under a topic, named by its OBJECTIVE (the question to settle or outcome to reach). Check `tree` first and prefer contributing to an existing thread — open a new one only when the deliberation genuinely doesn't fit anywhere; then make the first contribution yourself.",
+    description: "Open a NEW deliberation thread under a topic, named by its OBJECTIVE (the question to settle or outcome to reach). Check `tree` first and prefer contributing to an existing thread — open a new one only when the deliberation genuinely doesn't fit anywhere; then make the first contribution yourself. After opening, set its waysToHelp (set_ways_to_help) so others see how to pitch in.",
     inputSchema: {
       spaceId: exports_external.string().describe("the space, spc_…"),
       topicId: exports_external.string().describe("the topic to file it under, top_…"),
@@ -16717,7 +16729,7 @@ var ACTIONS = [
   {
     name: "space_create",
     title: "Create a space",
-    description: "Create a top-level space — the org-foundation container topics and threads live under. ORG OWNER/ADMIN only (a non-admin gets a clean 403): stand up a new area of work, e.g. a 'Saffron' space for cross-agent infra/tooling deliberation. Pass visibility private for invite-only (default open). Pass memberProfileIds to seed the space with members in one step — agents are added directly, humans get a pending invite to accept.",
+    description: "Create a top-level space — the org-foundation container topics and threads live under. ORG OWNER/ADMIN only (a non-admin gets a clean 403): stand up a new area of work, e.g. a 'Saffron' space for cross-agent infra/tooling deliberation. Pass visibility private for invite-only (default open). Pass memberProfileIds to seed the space with members in one step — agents are added directly, humans get a pending invite to accept. After creating, set the space's guidance (the `charter` tool's space_guidance verb) and its goals (create_goal) so members and agents know how to operate here.",
     inputSchema: {
       title: exports_external.string().min(1).describe("the space title"),
       purpose: exports_external.string().optional().describe("optional one-line purpose"),
@@ -16830,7 +16842,7 @@ var ACTIONS = [
   {
     name: "goal",
     title: "Work with goals",
-    description: "GOALS (initiatives) — the wide 'why' threads serve toward (AD-146/180). verb=get (id — one goal read fully, ANY status incl. archived), create (spaceId+title, optional purpose/threadIds — the creating space becomes its HOME), list (threadId — the goals that thread's space offers), update (id + title/purpose), set_status (id+status: active|paused|completed|archived — completed = reached, archived = retired from pick lists), delete (id), link_thread/unlink_thread (threadId+initiativeId), attach_space/detach_space (initiativeId+spaceId — surface a goal in MORE spaces).",
+    description: "GOALS (initiatives) — the wide 'why' threads serve toward (AD-146/180). verb=get (id — one goal read fully, ANY status incl. archived), create (spaceId+title, optional purpose/threadIds — the creating space becomes its HOME), list (spaceId — a space's goals, OR threadId — a thread's linked goals), update (id + title/purpose), set_status (id+status: active|paused|completed|archived — completed = reached, archived = retired from pick lists), delete (id), link_thread/unlink_thread (threadId+initiativeId), attach_space/detach_space (initiativeId+spaceId — surface a goal in MORE spaces).",
     inputSchema: {
       verb: exports_external.enum([
         "create",
@@ -16843,7 +16855,7 @@ var ACTIONS = [
         "attach_space",
         "detach_space"
       ]).describe("which goal move to make"),
-      spaceId: exports_external.string().optional().describe("create: HOME space · attach/detach_space: the target space, spc_…"),
+      spaceId: exports_external.string().optional().describe("create: HOME space · list: a space's goals · attach/detach_space: the target space, spc_…"),
       title: exports_external.string().optional().describe("create/update: the goal's name — an outcome, not a task"),
       purpose: exports_external.string().optional().describe("create/update: one or two lines on what reaching it means"),
       threadIds: exports_external.array(exports_external.string()).optional().describe("create: threads to link at birth"),
@@ -16854,18 +16866,28 @@ var ACTIONS = [
     },
     surfaces: ["mcp"],
     toolset: "goals",
-    run: dispatch({
-      get: "initiative.get",
-      create: "initiative.create",
-      list: "initiative.forThread",
-      update: "initiative.update",
-      set_status: "initiative.setStatus",
-      delete: "initiative.delete",
-      link_thread: "initiative.linkThread",
-      unlink_thread: "initiative.unlinkThread",
-      attach_space: "initiative.attachSpace",
-      detach_space: "initiative.detachSpace"
-    })
+    run: (ex, input) => {
+      const { verb, spaceId, threadId } = input;
+      if (verb === "list") {
+        if (typeof spaceId === "string")
+          return ex.call("initiative.listForSpace", { spaceId });
+        if (typeof threadId === "string")
+          return ex.call("initiative.forThread", { threadId });
+        return Promise.reject(new Error("goal list requires a spaceId (a space's goals) or a threadId (a thread's goals)"));
+      }
+      return dispatch({
+        get: "initiative.get",
+        create: "initiative.create",
+        list: "initiative.forThread",
+        update: "initiative.update",
+        set_status: "initiative.setStatus",
+        delete: "initiative.delete",
+        link_thread: "initiative.linkThread",
+        unlink_thread: "initiative.unlinkThread",
+        attach_space: "initiative.attachSpace",
+        detach_space: "initiative.detachSpace"
+      })(ex, input);
+    }
   },
   {
     name: "membership",
@@ -17010,14 +17032,14 @@ var ACTIONS = [
   {
     name: "charter",
     title: "Set the guidance surfaces",
-    description: "The guidance you WRITE (read back via space_get/topic_get/thread_get). verb=space_charter (spaceId+charter — how YOU operate in this space, AD-152; org admins may pass profileId to bootstrap another member's), topic_guidance (topicId+guidance[] — the topic's soft norms, replaces the list, [] clears), ways_to_help (threadId+waysToHelp[] — a thread's curated pitch-in list; guidance, never obligation — obligations are `request`).",
+    description: "The guidance you WRITE (read back via space_get/topic_get/thread_get). verb=space_charter (spaceId+charter — how YOU operate in this space, AD-152; org admins may pass profileId to bootstrap another member's), space_guidance (spaceId+guidance[] — the SPACE's soft norms/how-we-work-here, replaces the list, [] clears), topic_guidance (topicId+guidance[] — the topic's soft norms, replaces the list, [] clears), ways_to_help (threadId+waysToHelp[] — a thread's curated pitch-in list; guidance, never obligation — obligations are `request`).",
     inputSchema: {
-      verb: exports_external.enum(["space_charter", "topic_guidance", "ways_to_help"]).describe("which guidance surface to set"),
-      spaceId: exports_external.string().optional().describe("space_charter: the space, spc_…"),
+      verb: exports_external.enum(["space_charter", "space_guidance", "topic_guidance", "ways_to_help"]).describe("which guidance surface to set"),
+      spaceId: exports_external.string().optional().describe("space_charter/space_guidance: the space, spc_…"),
       charter: exports_external.string().optional().describe("space_charter: the text; empty string clears"),
       profileId: exports_external.string().optional().describe("space_charter admin override: whose charter"),
       topicId: exports_external.string().optional().describe("topic_guidance: the topic, top_…"),
-      guidance: exports_external.array(exports_external.string()).optional().describe("topic_guidance: full list, replaces; [] clears"),
+      guidance: exports_external.array(exports_external.string()).optional().describe("space_guidance/topic_guidance: full list, replaces; [] clears"),
       threadId: exports_external.string().optional().describe("ways_to_help: the thread, thr_…"),
       waysToHelp: exports_external.array(exports_external.string()).optional().describe("ways_to_help: full list, replaces; [] clears")
     },
@@ -17025,6 +17047,7 @@ var ACTIONS = [
     toolset: "spaces",
     run: dispatch({
       space_charter: "space.setCharter",
+      space_guidance: "space.setGuidance",
       topic_guidance: "topic.update",
       ways_to_help: "thread.update"
     })

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lambdacurry/arbor",
-  "version": "0.8.3",
+  "version": "0.8.4",
   "description": "The Arbor CLI — a shared workspace for people and agents. The human + headless-agent write path over Arbor's guarded operation surface.",
   "keywords": [
     "agents",