@productbrain/mcp 0.0.1-beta.8633 → 0.0.1-beta.8637

package/dist/{chunk-LDWP3UNV.js → chunk-OZXZLLHS.js}

@@ -13731,7 +13731,7 @@ var ALLOWED_RELATION_TYPES_LIST = [
 var ALLOWED_RELATION_TYPES = new Set(ALLOWED_RELATION_TYPES_LIST);
 
 // src/resources/agentCheatsheet.ts
-var DATA_HANDLING_SECTION = "### How PB Handles Your Data\n- **The reply is the source of truth**: every reply carries `ok`; on failure it carries `code` and guidance. Read the reply, never an expectation.\n- **Empty-workspace safe**: the orientation resource and this cheatsheet render on a workspace with no entries and no collections.\n- **Workspace-agnostic**: PB is one product used by many teams. Nothing in these instructions is specific to your workspace; your own principles, standards and rules arrive through `productbrain://orientation`.\n- **Served, not installed**: these instructions, `productbrain://orientation` and `productbrain://agent-cheatsheet` are served over MCP.";
+var DATA_HANDLING_SECTION = "### How PB Handles Your Data\n- **The reply is the source of truth**: every reply carries `ok`; on failure it carries `code` and guidance. Read the reply, never an expectation.\n- **Empty-workspace safe**: the orientation resource and this cheatsheet render on a workspace with no entries and no collections.\n- **Workspace-agnostic**: PB is one product used by many teams. Nothing in these instructions is specific to your workspace; your own rules arrive as the rule lists that session start and orient serve you.\n- **Served, not installed**: these instructions, `productbrain://orientation` and `productbrain://agent-cheatsheet` are served over MCP.";
 var AGENT_CHEATSHEET = `# Product Brain \u2014 Agent Cheatsheet
 
 ## Core Tools (Serves 15 compound tools, always)
@@ -13756,8 +13756,7 @@ var AGENT_CHEATSHEET = `# Product Brain \u2014 Agent Cheatsheet
 This table lists actions only. See \`tools/list\` for each tool's input schema; a missing or invalid parameter is named in the call's own reply.
 
 ## Collection Prefixes
-GLO (glossary), BR (business-rules), PRI (principles), STD (standards),
-DEC (decisions), STR (strategy), TEN (tensions), FEAT (features),
+GLO (glossary), RULE (rules), DEC (decisions), STR (strategy), TEN (tensions), FEAT (features),
 BET (bets), INS (insights), ARCH (architecture), TEAM (teams),
 ROL (roles), MTRC (tracking-events), ST (semantic-types)
 
@@ -13771,7 +13770,11 @@ Write via \`update\`: \`draft\` | \`archived\` (\`accepted\` via \`commit\`, nev
 - **tensions:** open \u2192 processing \u2192 decided \u2192 closed
 - **decisions:** pending \u2192 decided
 - **bets:** shaped \u2192 bet \u2192 building \u2192 shipped
-- **business-rules:** active | conflict | review
+
+## Rule Lists
+- Session start and \`orient action=task\` serve the rules that bind you, each as one sentence with its why.
+- A rule's \`applies\` and its one owner role place it on one list: everyone (cap 15), team (cap 5 per team) or role (cap 5 per role).
+- A rule on no list binds nobody; a full list refuses a new rule until one retires, and a list over its cap is served whole.
 
 ## Key Patterns
 - **Capture flow:** \`capture\` \u2192 \`relations action=suggest\` \u2192 \`relations action=batch-create\` \u2192 \`entries action=commit\`
@@ -14444,67 +14447,43 @@ Make sure the rule is consistent with existing rules and doesn't contradict them
 // src/server.ts
 var SERVER_VERSION = "0.7.2";
 var INSTRUCTIONS = [
-  "Product Brain \u2014 the single source of truth for product knowledge.",
-  "Terminology, standards, and core data all live here \u2014 no need to check external docs.",
-  "",
-  "## About Product Brain (PB)",
+  "Product Brain (PB) is the single source of truth for your team's product knowledge: decisions, tensions, rules, work and the links between them.",
   "",
-  "PB is a knowledge management system used by many product teams.",
-  "These describe how PB works \u2014 not your product.",
+  "## What session start hands you",
   "",
-  "### How PB Organizes Its Tools",
-  "- **Tools** are for actions with side-effects or dynamic computation (capture, accept, search).",
-  "- **Resources** are for stable, read-only data (orientation, terminology, collection schemas).",
-  "- **Prompts** are for multi-step choreography (workflows, guided capture, deep dives).",
-  "- Every tool, resource, and prompt works for ANY workspace \u2014 no bespoke logic.",
-  "- Resource templates (URI params) provide workspace-specific data through generic patterns.",
-  "- Tool count stays minimal: compound tools with `action` enums over many single-purpose tools.",
+  "Call `session action=start` first. The reply names:",
+  "- the workspace and the role you act as;",
+  "- notices, including open questions routed to you;",
+  "- the rule lists that bind you, each rule as one sentence with its why, its owner role and, when it has one, its date.",
   "",
-  DATA_HANDLING_SECTION,
+  "Read those rules before you propose or build. If the work conflicts with one, stop, name the rule and ask the user before going on. Never design around a rule.",
   "",
-  "## Your Workspace Principles",
+  "## What applies means",
   "",
-  "When you orient or start, PB surfaces active entries from your `principles`, `standards`,",
-  "and `business-rules` collections. These are YOUR team's guardrails \u2014 respect them during implementation.",
-  "If no principles exist yet, PB will tell you and suggest how to add them.",
+  "Every rule (collection `rules`) declares whom it applies to, and its one owner role places it:",
+  "- **everyone**: the whole workspace, owned by the root team's lead; capped at 15 rules;",
+  "- **team**: its owner role's team; capped at 5 per team;",
+  "- **role**: its owner role; capped at 5 per role.",
   "",
-  "The three governance collections:",
-  "- **Principles** (`principles`) \u2014 beliefs that guide decisions. 'We believe X.' You reason from a principle.",
-  "- **Standards** (`standards`) \u2014 conventions about how work is done. 'We do X this way.' You lint for a standard.",
-  "- **Business Rules** (`business-rules`) \u2014 system constraints. 'The system must do X.' You test for a rule.",
+  "A rule on no list binds nobody. A full list refuses a new rule until one retires; a list already over its cap is served whole.",
   "",
-  "## Workflow",
+  "## Pull the rest",
   "",
-  "  1. Start: call `session action=start` to open a tracked write session, then `orient action=start` \u2014 it returns a standup briefing for every workspace state, fresh or active. (`orient` orients the session; only `session action=start` creates one.)",
-  "  2. Re-orient: call `orient action=task` mid-session for task-scoped context or a compact status refresh.",
-  "  3. Discover: use `entries action=search` to find entries, or `entries action=list` to browse.",
-  '  4. Drill in: use `entries action=get entryId="..."` for full details \u2014 data, labels, relations, history.',
-  "  5. Context: use `context action=gather` with an entryId or a task description.",
-  "  6. Capture: use `capture` to create entries \u2014 auto-links and scores in one call.",
-  "  7. Accept: use `entries action=commit` to send a draft for acceptance \u2014 read the reply's outcome/status field for what happened; read the capture reply first, since an entry that came back accepted needs no commit.",
-  "  8. Connect: use `relations action=suggest` then `relations action=create` to build the graph.",
-  "  9. Wrapup: call `session action=wrapup-review` before closing \u2014 reviews drafts, coaches quality, suggests links.",
-  "  10. Close: call `session action=close` when done \u2014 records session activity. Auto-nudges if wrapup was skipped.",
+  '- `orient action=task task="<what you are doing>"`: context shaped to the task, with the rules for your team and role.',
+  '- `entries action=get entryId="<ID>"`: one entry in full, with data, relations and history.',
+  '- `entries action=search query="<noun>"`: find entries by what they are about.',
   "",
-  "Write tools (capture, entries action=update, relations, entries action=commit) require:",
-  "  - An active agent session \u2014 call `session action=start` first, then `orient action=start` for context. Call `orient action=task` mid-session for a refresh.",
-  "  - A readwrite API key scope",
+  "## Writing",
   "",
-  "Alignment-first: before proposing or building anything, check orient's Workspace Governance",
-  "and Active work packages sections. These are constraints, not reference material.",
-  "If the proposal conflicts with a principle, standard, or business rule \u2014 stop, flag the conflict,",
-  "and get explicit user confirmation before proceeding. Do not design around governance.",
-  "If the work is outside the scope of active work packages \u2014 stop, name the gap, and ask the user",
-  "to confirm before designing. Do not propose implementation for out-of-scope work without a go-ahead.",
+  "Write actions (capture, entries update and commit, relations create, batch-create, dismiss and delete) need an active session and a readwrite key.",
+  "Use `capture` to create an entry and read its reply: an entry that came back accepted needs no `entries action=commit`.",
+  "Link with `relations action=suggest`, then `relations action=create`.",
+  "Finish with `session action=wrapup-review`, then `session action=close`.",
+  "If the work falls outside the active work packages, name the gap and ask the user before designing it.",
   "",
-  "Workspace setup: use `collections action=update` to shape existing collections with the user.",
-  "Creating a brand-new collection is not self-serve \u2014 ask a platform admin to provision it, or",
-  "enable the module ontology pack that owns the drawer.",
+  DATA_HANDLING_SECTION,
   "",
-  "Personalization: if you have context about the user from memory (prior work, recent",
-  "conversations, team context), use it to personalize recommendations. For example,",
-  "'Based on your recent pitch reviews, the gap most likely to matter is X.'",
-  "The orient/start output gives you the workspace state; your memory fills in the human context."
+  "Every tool and action: `productbrain://agent-cheatsheet`."
 ].join("\n");
 function createProductBrainServer() {
   const server = new McpServer2(
@@ -14561,4 +14540,4 @@ export {
   createProductBrainServer,
   initFeatureFlags
 };
-//# sourceMappingURL=chunk-LDWP3UNV.js.map
+//# sourceMappingURL=chunk-OZXZLLHS.js.map