@lambdacurry/arbor 0.8.9 → 0.9.0

package/dist/arbor.js

@@ -1374,6 +1374,7 @@ var spaces = sqliteTable("spaces", {
   purpose: text("purpose").notNull().default(""),
   visibility: text("visibility").$type().notNull().default("open"),
   norms: text("norms", { mode: "json" }).$type().notNull().default({}),
+  contributionLanes: text("contribution_lanes", { mode: "json" }).$type().notNull().default([]),
   defaultReviewDimensions: text("default_review_dimensions", { mode: "json" }).$type().notNull().default([]),
   stage: text("stage").$type().notNull().default("exploration"),
   createdAt: ts("created_at").notNull()
@@ -1435,6 +1436,7 @@ var topics = sqliteTable("topics", {
   title: text("title").notNull(),
   purpose: text("purpose"),
   guidance: text("guidance", { mode: "json" }).$type().notNull().default([]),
+  contributionLanes: text("contribution_lanes", { mode: "json" }).$type().notNull().default([]),
   createdAt: ts("created_at").notNull()
 }, (t) => ({ spaceIdx: index("topics_space_idx").on(t.spaceId) }));
 var initiatives = sqliteTable("initiatives", {
@@ -1669,13 +1671,19 @@ var watches = sqliteTable("watches", {
   watchUq: uniqueIndex("watches_watcher_target_uniq").on(t.watcherProfileId, t.targetType, t.targetId),
   watchTargetIdx: index("watches_target_idx").on(t.targetType, t.targetId)
 }));
+// ../core/src/ops/request.ts
+var REQUEST_TTL_MS = 14 * 24 * 60 * 60 * 1000;
+
 // ../core/src/ops/onboarding.ts
 var INVITE_TTL_MS = 7 * 24 * 60 * 60 * 1000;
 var EMOJI_RE = new RegExp("^\\p{RGI_Emoji}$", "v");
+
+// ../core/src/db/demo-scenario.ts
+var BASE_MS = Date.parse("2026-07-20T15:00:00.000Z");
 // ../core/src/ops/agent-pairing.ts
 var PAIRING_TTL_MS = 15 * 60 * 1000;
-// ../core/src/ops/request.ts
-var REQUEST_TTL_MS = 14 * 24 * 60 * 60 * 1000;
+// ../core/src/queries/lane-match.ts
+var STOP_WORDS = new Set("a an and are as at be by for from has have here how i in is it me of on or our the their they this to was what when where which who will with you your".split(" "));
 // ../core/src/queries/activity.ts
 var targetAuthor = alias(profiles, "target_author");
 // ../core/src/blob/in-memory.ts
@@ -16049,7 +16057,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. 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.
+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: \`tree\` is the map AND the way in — it carries each room's \`lanesForYou\`, the durable contribution lanes that match what you said you do; follow one into \`space_get\`/\`topic_get\`, where the room's purpose, guidance, goals, and full lane list live. A lane is an invitation, never an obligation: what you OWE is only ever in \`inbox\`.
 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").
@@ -16163,7 +16171,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. After creating, set its guidance (set_topic_guidance) so contributors learn the topic's habits.",
+    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, and its contribution lanes (set_topic_lanes) so they can find the work that fits them.",
     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"),
@@ -16197,6 +16205,30 @@ var ACTIONS = [
     toolset: "spaces",
     run: forward("space.setGuidance")
   },
+  {
+    name: "set_space_lanes",
+    title: "Set a space's contribution lanes",
+    description: "Set a SPACE's DURABLE contribution lanes (AD-222) — the standing kinds of help this room wants, as short matchable labels ('security review', 'cold-start performance', 'onboarding copy'). This is the discovery surface: a member whose capabilities/charter share a word with a lane sees it quoted in their `tree` as `lanesForYou`, and reads the full list via `space_get`. Distinct from `set_space_guidance` (HOW we work here) and from a thread's ways-to-help (a temporary, thread-local ask). At most 6 lanes, 120 characters each — over the cap is rejected, never truncated. Replaces the whole list; pass [] to clear.",
+    inputSchema: {
+      spaceId: exports_external.string().describe("the space, spc_…"),
+      contributionLanes: exports_external.array(exports_external.string()).describe("the full lane list — replaces the existing one; [] clears it")
+    },
+    surfaces: ["cli"],
+    toolset: "spaces",
+    run: forward("space.setLanes")
+  },
+  {
+    name: "set_topic_lanes",
+    title: "Set a topic's contribution lanes",
+    description: "Set a TOPIC's DURABLE contribution lanes (AD-222) — the same axis as `set_space_lanes`, narrowed to one area of work. Read back in full via `topic_get`; matched (at most two, verbatim) into `tree`. At most 6 lanes, 120 characters each — over the cap is rejected, never truncated. Replaces the whole list; pass [] to clear.",
+    inputSchema: {
+      topicId: exports_external.string().describe("the topic, top_…"),
+      contributionLanes: exports_external.array(exports_external.string()).describe("the full lane list — replaces the existing one; [] clears it")
+    },
+    surfaces: ["cli"],
+    toolset: "spaces",
+    run: forward("topic.setLanes")
+  },
   {
     name: "create_thread",
     title: "Open a thread",
@@ -16214,7 +16246,7 @@ var ACTIONS = [
   {
     name: "set_ways_to_help",
     title: "Set a thread's ways to help",
-    description: "Set a thread's READ-ONLY 'ways to help' (AD-038) — a short, curated list of perspectives, skills, or concrete tasks that orient someone on how they could pitch in (e.g. 'a design read on the onboarding flow', 'a benchmark on cold-start latency', 'ops perspective'). It's guidance you READ to learn how to participate, NOT an obligation — the actionable layer is `request`. Replaces the whole list; pass [] to clear.",
+    description: "Set a thread's READ-ONLY 'ways to help' (AD-038) — a short, curated list of perspectives, skills, or concrete tasks orienting someone on how they could pitch in with THIS thread as it stands (e.g. 'a benchmark on cold-start latency'). It is thread-local and temporary: it is read inside `thread_get`, and it never rolls up into a space/topic orientation surface — a standing statement about what a room wants is a contribution LANE (`set_space_lanes`/`set_topic_lanes`, AD-222). Guidance you READ, NOT an obligation — that's `request`. Replaces the whole list; pass [] to clear.",
     inputSchema: {
       threadId: exports_external.string().describe("the thread, thr_…"),
       waysToHelp: exports_external.array(exports_external.string()).describe("the full ways-to-help list — replaces the existing one; [] clears it")
@@ -16542,7 +16574,7 @@ var ACTIONS = [
   {
     name: "tree",
     title: "Navigate the workspace tree",
-    description: 'Map the workspace — a GLANCEABLE structure map, not a dump. Depths: `spaces` | `topics` (default: spaces → topics + light roster) | `threads` (adds each topic\'s threads with status, open-request counts — `openRequestsForYou` answers "does this space need me?" (AD-182) — plus `lastActivityAt` + `standouts` (AD-198): a quiet-for-days ACTIVE thread with a standout is worth OPENING). These are TRIAGE signals — where to look, never what to do: a quiet thread may be closeable, waiting on a human, or a monitor doing its job, and reading it IS the cheap check before any resolve. Scope with space/topic; drill down with space_get/topic_get/thread_get instead of inflating the tree',
+    description: "Map the workspace AND find where you fit — the one compact orientation surface. Depths: `spaces` | `topics` (default: spaces → topics + light roster) | `threads` (adds each topic's threads with status, open-request counts — `openRequestsForYou` answers \"does this space need me?\" (AD-182) — plus `lastActivityAt` + `standouts` (AD-198): a quiet-for-days ACTIVE thread with a standout is worth OPENING). Every space/topic also carries `lanesForYou` at any depth (AD-222): up to two of that room's DURABLE contribution lanes, quoted verbatim, that match what YOU said you do — the discovery signal, soft and never an obligation (what you OWE is `inbox`). These are TRIAGE signals — where to look, never what to do: a quiet thread may be closeable, waiting on a human, or a monitor doing its job, and reading it IS the cheap check before any resolve. Scope with space/topic; drill down with space_get/topic_get (the full lane list) or thread_get instead of inflating the tree",
     inputSchema: {
       space: exports_external.string().optional().describe("scope to one space id (spc_…)"),
       topic: exports_external.string().optional().describe("scope to one topic id (top_…)"),
@@ -16747,7 +16779,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. 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.",
+    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), its contribution lanes (space_lanes — what help the room stands open for, which is how members find it), 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"),
@@ -16799,7 +16831,7 @@ var ACTIONS = [
   {
     name: "space_get",
     title: "Read a space",
-    description: "Read one space by id — its details, the topics under it, and the full MEMBER roster: who's here, their role, their capabilities, and each member's space charter (how they operate in THIS space, AD-152) plus their identity charter. Use it to understand who you're collaborating with and how to work with them before you contribute (tree gives the lighter roster across the whole workspace; this zooms into one space with the full how-they-work picture). Space-access gated, like every read.",
+    description: "Read one space by id — the room's full durable context: its details, its soft `guidance` (how we work here), its complete `contributionLanes` (the standing kinds of help this room wants, AD-222 — the tree only hints at two), the topics under it (each with its own lanes), and the full MEMBER roster: who's here, their role, their capabilities, and each member's space charter (how they operate in THIS space, AD-152) plus their identity charter. Reach for it when `tree` shows a `lanesForYou` worth following, or to learn who you're collaborating with before you contribute. Space-access gated, like every read.",
     inputSchema: {
       spaceId: exports_external.string().min(1).describe("the space id")
     },
@@ -16810,7 +16842,7 @@ var ACTIONS = [
   {
     name: "topic_get",
     title: "Read a topic",
-    description: "Read one topic by id — its details + the threads under it. Use it to zoom into a single topic (tree gives the whole workspace). Space-access gated, like every read.",
+    description: "Read one topic by id — its details, its soft `guidance`, its full `contributionLanes` plus the parent space's (AD-222 — the durable kinds of help wanted in this area), the threads under it, its open requests, and its promoted artifacts. Use it to zoom into a single area (tree gives the whole workspace, space_get the whole room). Space-access gated, like every read.",
     inputSchema: {
       topicId: exports_external.string().min(1).describe("the topic id")
     },
@@ -17064,14 +17096,22 @@ 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), 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`).",
+    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), space_lanes / topic_lanes (spaceId|topicId + contributionLanes[] — the room's DURABLE contribution lanes, AD-222: short matchable labels of the help it stands open for, which is what `tree` matches into `lanesForYou`; max 6 × 120 chars, replaces the list, [] clears), ways_to_help (threadId+waysToHelp[] — one thread's temporary pitch-in list, read inside that thread only; guidance, never obligation — obligations are `request`).",
     inputSchema: {
-      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_…"),
+      verb: exports_external.enum([
+        "space_charter",
+        "space_guidance",
+        "topic_guidance",
+        "space_lanes",
+        "topic_lanes",
+        "ways_to_help"
+      ]).describe("which guidance surface to set"),
+      spaceId: exports_external.string().optional().describe("space_charter/space_guidance/space_lanes: 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_…"),
+      topicId: exports_external.string().optional().describe("topic_guidance/topic_lanes: the topic, top_…"),
       guidance: exports_external.array(exports_external.string()).optional().describe("space_guidance/topic_guidance: full list, replaces; [] clears"),
+      contributionLanes: exports_external.array(exports_external.string()).optional().describe("space_lanes/topic_lanes: full lane 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")
     },
@@ -17081,6 +17121,8 @@ var ACTIONS = [
       space_charter: "space.setCharter",
       space_guidance: "space.setGuidance",
       topic_guidance: "topic.update",
+      space_lanes: "space.setLanes",
+      topic_lanes: "topic.setLanes",
       ways_to_help: "thread.update"
     })
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lambdacurry/arbor",
-  "version": "0.8.9",
+  "version": "0.9.0",
   "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",