@knowsuchagency/fulcrum 3.5.1 → 3.5.2

package/bin/fulcrum.js

@@ -46421,7 +46421,7 @@ async function runMcpServer(urlOverride, portOverride) {
   const client = new FulcrumClient(urlOverride, portOverride);
   const server = new McpServer({
     name: "fulcrum",
-    version: "3.5.1"
+    version: "3.5.2"
   });
   registerTools(server, client);
   const transport = new StdioServerTransport;
@@ -48770,7 +48770,7 @@ var marketplace_default = `{
       "name": "fulcrum",
       "source": "./",
       "description": "Task orchestration for Claude Code",
-      "version": "3.5.1",
+      "version": "3.5.2",
       "skills": [
         "./skills/fulcrum"
       ],
@@ -49974,7 +49974,7 @@ function compareVersions(v1, v2) {
 var package_default = {
   name: "@knowsuchagency/fulcrum",
   private: true,
-  version: "3.5.1",
+  version: "3.5.2",
   description: "Harness Attention. Orchestrate Agents. Ship.",
   license: "PolyForm-Perimeter-1.0.0",
   type: "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knowsuchagency/fulcrum",
-  "version": "3.5.1",
+  "version": "3.5.2",
   "description": "Harness Attention. Orchestrate Agents. Ship.",
   "license": "PolyForm-Perimeter-1.0.0",
   "repository": {

package/server/index.js

@@ -1136599,7 +1136599,7 @@ ${formattingGuide}`;
 function getObserveOnlySystemPrompt(channelType, context) {
   return `## Observe-Only Mode
 
-You are the user's observer \u2014 your core job is to prevent things from falling through the cracks. When you see something actionable, make it visible by creating a Fulcrum task. Memories are secondary \u2014 useful for tracking context that doesn't warrant a task.
+You are the user's observer. Only create a task when the user must take a specific action or fulfill a commitment they might otherwise forget. Default to storing a memory or doing nothing \u2014 only escalate to a task when doing nothing would cause the user to miss something important. A frivolous task is worse than no task: it wastes the user's time and erodes trust.
 
 **Channel**: ${context.channel}
 **From**: ${context.sender}${context.senderName ? ` (${context.senderName})` : ""}
@@ -1136634,12 +1136634,36 @@ ${context.metadata?.isGroup ? `**Group Chat**: yes` : ""}
 
 Silently analyze this message and take the appropriate action:
 
-1. **Actionable requests directed at the user** (deadlines, meetings, tasks, to-dos, follow-ups) \u2192 Use \`list_tasks\` to check for duplicates, then \`create_task\` with a clear title, description, relevant tags, and dueDate if mentioned. Tag with \`from:${context.channel}\`. After creating a task, use \`send_notification\` to alert the user (e.g., title: "New task from ${context.channel}", message: the task title).
-2. **Updates about existing matters** (confirmations, status changes, new details on known topics) \u2192 Use \`list_tasks\` to find the related task, then \`update_task\` or \`add_task_link\` as appropriate.
+1. **The user must take a specific action or respond** (someone asks them to do something, they need to fulfill a commitment, a genuine deadline they must meet) \u2192 Use \`list_tasks\` to check for duplicates, then \`create_task\` with a clear title, description, relevant tags, and dueDate if mentioned. Tag with \`from:${context.channel}\`. After creating a task, use \`send_notification\` to alert the user.
+2. **Updates about existing matters** (new details on a known topic) \u2192 Use \`list_tasks\` to find the related task, then \`update_task\` or \`add_task_link\` as appropriate.
 3. **Important persistent observations** (learning someone's name, recurring topics, key relationships) \u2192 \`memory_store\` with tag \`persistent\`
-4. **Casual messages, spam, or irrelevant content** \u2192 Do nothing
+4. **Everything else** (automated notifications, FYI messages, status updates, casual chat, spam) \u2192 Do nothing
 
-When creating tasks, write the title as a clear action item (e.g., "Arrange cow rental for parade" not "Message about cow rental"). Include the sender and channel context in the description.
+### Do NOT create tasks for:
+- Automated notifications (shipping updates, RSVP notifications, social media alerts, CI/CD results)
+- FYI/informational messages that don't require user action
+- Event reminders for events the user is merely attending
+- Status updates and confirmations (order confirmations, booking confirmations)
+- Newsletters, promotional emails, marketing content
+
+### Examples
+
+**CREATE a task:**
+- WhatsApp message: "Can you send me that document?" \u2192 "Send document to Alice"
+- Email asking for details: "Can you confirm the budget?" \u2192 "Reply to Bob with project budget details"
+- Proposal needing review: "Here's the proposal, let me know your thoughts" \u2192 "Review and respond to proposal from Carol"
+- Follow-up request: "Let's schedule a call next week" \u2192 "Schedule call with Dave"
+
+**Do NOT create a task:**
+- Meetup RSVP notification: "3 new RSVPs for your event" \u2192 do nothing (automated FYI)
+- Shipping update: "Your package is out for delivery" \u2192 do nothing (automated FYI)
+- Order confirmation: "Your order #1234 has been confirmed" \u2192 do nothing (automated FYI)
+- Newsletter or marketing email \u2192 do nothing
+
+### Decision test
+Before creating a task, ask: "Is the user being asked to DO something specific, or would they miss a commitment without this?" If no, do nothing.
+
+When creating tasks, write the title as a clear action item (e.g., "Send invoice to Alice" not "Email from Alice about invoice"). Include the sender and channel context in the description.
 
 **Always use \`memory_store\`** for non-task observations \u2014 never write to MEMORY.md directly. The hourly sweep reviews stored memories and promotes important patterns to the memory file.
 Include the source channel as the \`source\` field (e.g., "channel:${context.channel}").
@@ -1150255,7 +1150279,7 @@ ${contextualMessage}`;
     yield { type: "error", data: { message: errorMsg } };
   }
 }
-var OPENCODE_DEFAULT_PORT = 4096, opencodeClient = null, OBSERVER_SYSTEM_PROMPT = `You are the user's observer \u2014 your core job is to prevent things from falling through the cracks. When you see something actionable, create a task. Memories are secondary \u2014 useful for context that doesn't warrant a task.
+var OPENCODE_DEFAULT_PORT = 4096, opencodeClient = null, OBSERVER_SYSTEM_PROMPT = `You are the user's observer. Only create a task when the user must take a specific action or fulfill a commitment they might otherwise forget. Default to storing a memory or doing nothing \u2014 only escalate to a task when doing nothing would cause the user to miss something important. A frivolous task is worse than no task: it wastes the user's time and erodes trust.
 
 IMPORTANT: You have NO tools. Instead, respond with a JSON object describing what actions to take.
 
@@ -1150283,31 +1150307,54 @@ If the message contains nothing worth tracking (casual chat, greetings, spam, et
 
 ## Action types
 
-### create_task (preferred for actionable items)
-Use for: deadlines, meetings, to-dos, follow-ups, requests directed at the user.
+### create_task (only for genuine action items)
+Use for: someone specifically asks the user to do something, the user must fulfill a commitment, a genuine deadline the user must meet.
+Do NOT use for: automated notifications, FYI messages, event reminders, status updates, confirmations.
 Fields: title (required, imperative action item), description, tags (array), dueDate (YYYY-MM-DD if mentioned).
-Write titles as clear action items (e.g., "Arrange cow rental for parade" not "Message about cow rental").
+Write titles as clear action items (e.g., "Send invoice to Alice" not "Email from Alice about invoice").
 
 ### store_memory (for non-task observations)
-Use for: learning someone's name, recurring patterns, key relationships, context updates.
+Use for: learning someone's name, recurring patterns, key relationships, context updates, noteworthy information from notifications.
 Fields: content (required), tags (array), source (e.g., "channel:whatsapp").
 
 ## Guidelines
 
-Create a task for:
-- Deadlines, appointments, meetings
-- Action items or requests directed at the user
-- Follow-ups or reminders
+Create a task ONLY when:
+- Someone specifically asks the user to do something ("Can you send me X?", "Please review Y")
+- The user made a commitment they might forget (promised to call someone, agreed to deliver something)
+- A genuine deadline the user must personally meet (tax filing, contract deadline)
 
 Store a memory for:
 - Contact details, names, relationships
 - Project context or status updates
 - Patterns worth remembering
+- Noteworthy information from notifications (without creating a task)
 
 Do nothing for:
+- Automated notifications (shipping updates, RSVP alerts, CI/CD results, social media)
+- FYI/informational messages that don't require user action
+- Event reminders for events already on the calendar
+- Status updates and confirmations (order confirmations, booking confirmations)
+- Newsletters, promotional emails, marketing content
 - Casual greetings or small talk
-- Spam or promotional content
-- Messages you don't understand`;
+- Messages you don't understand
+
+## Examples
+
+CREATE a task:
+- WhatsApp: "Can you send me that document?" \u2192 title: "Send document to Alice"
+- Email: "Can you confirm the budget for the project?" \u2192 title: "Reply to Bob with project budget details"
+- Email: "Here's the proposal, let me know your thoughts" \u2192 title: "Review and respond to proposal from Carol"
+- WhatsApp: "Let's schedule a call next week" \u2192 title: "Schedule call with Dave"
+
+Do NOT create a task:
+- Meetup RSVP notification: "3 new RSVPs for your event" \u2192 do nothing (automated FYI)
+- Shipping update: "Your package is out for delivery" \u2192 do nothing (automated FYI)
+- Order confirmation: "Your order #1234 has been confirmed" \u2192 do nothing (automated FYI)
+- Newsletter or marketing email \u2192 do nothing
+
+## Decision test
+Before creating a task, ask: "Is the user being asked to DO something specific, or would they miss a commitment without this?" If no, do nothing.`;
 var init_opencode_channel_service = __esm(() => {
   init_dist10();
   init_logger3();
@@ -1255022,7 +1255069,7 @@ mcpRoutes.all("/", async (c) => {
   });
   const server2 = new McpServer({
     name: "fulcrum",
-    version: "3.5.1"
+    version: "3.5.2"
   });
   const client3 = new FulcrumClient(`http://localhost:${port}`);
   registerTools(server2, client3);